Open Source Python API Gateways

ThetaGang is an IBKR trading bot for collecting premiums by selling options using "The Wheel" strategy. The Wheel is a strategy that surfaced on Reddit but has been used by many in the past. This bot implements a slightly modified version of The Wheel, with my own personal tweaks. The strategy, as implemented here, does a few things differently from the one described in the post above. For one, it's intended to be used to augment a typical index-fund-based portfolio with specific asset allocations. For example, you might want to use a 60/40 portfolio with SPY (S&P500 fund) and TLT (20-year treasury fund). This strategy reduces risk, but may also limit gains from big market swings. By reducing risk, one can increase leverage. ThetaGang will try to acquire your desired allocation of each stock or ETF according to the weights you specify in the config. To acquire the positions, the script will write puts when conditions are met.

Zappa makes it super easy to build and deploy server-less, event-driven Python applications (including, but not limited to, WSGI web apps) on AWS Lambda + API Gateway. Think of it as "serverless" web hosting for your Python apps. That means infinite scaling, zero downtime, zero maintenance - and at a fraction of the cost of your current deployments! With a traditional HTTP server, the server is online 24/7, processing requests one by one as they come in. If the queue of incoming requests grows too large, some requests will time out. With Zappa, each request is given its own virtual HTTP "server" by Amazon API Gateway. AWS handles the horizontal scaling automatically, so no requests ever time out. Each request then calls your application from a memory cache in AWS Lambda and returns the response via Python's WSGI interface. After your app returns, the "server" dies.

Posting is an open-source, terminal-based API client designed for developers who prefer a fast, keyboard-driven workflow. It allows users to create, test, and manage HTTP requests directly from the command line without relying on graphical tools. The interface is highly interactive, offering features like command palettes, jump navigation, and real-time editing for efficient API exploration. Posting supports saving requests in a readable, version-control-friendly format, making it ideal for collaboration and reproducibility. It also includes scripting capabilities, enabling users to run Python code before and after requests to automate workflows. Overall, Posting brings a modern, customizable, and developer-centric API testing experience to the terminal.

The AWS Serverless Application Model (SAM) CLI is an open-source CLI tool that helps you develop serverless applications containing Lambda functions, Step Functions, API Gateway, EventBridge, SQS, SNS and more. The AWS Serverless Application Model (SAM) is an open-source framework for building serverless applications. It provides shorthand syntax to express functions, APIs, databases, and event source mappings. With just a few lines per resource, you can define the application you want and model it using YAML. During deployment, SAM transforms and expands the SAM syntax into AWS CloudFormation syntax, enabling you to build serverless applications faster. To get started with building SAM-based applications, use the SAM CLI. SAM CLI provides a Lambda-like execution environment that lets you locally build, test, debug, and deploy AWS serverless applications.

Flask-Limiter provides rate-limiting features to flask applications. It allows configuring various backends to persist the rate limits, which is provided by the limits library. Sponsored by Zuplo - fully-managed API Gateway with rate limiting, authentication, and more. Add rate limiting to your API in minutes, try it at zuplo.com Test it out. The fast endpoint respects the default rate limit while the slow endpoint uses the decorated one. ping has no rate limit associated with it. By adding the extension to your flask application, you can configure various rate limits at different levels (e.g. application wide, per Blueprint, routes, resource etc). To include extra dependencies for a specific storage backend you can add the specific backend name via the extras notation.

LocalStack is a fully functional local AWS cloud stack that enables you to develop and test your cloud and serverless apps offline. It spins up an easy-to-use testing environment on your local machine that has the same APIs and works the same way as the real AWS cloud environment. It can spin up a number of different core Cloud APIs on your local machine, including API Gateway, Kinesis, DynamoDB, Firehose, Lambda and many others. LocalStack was built on some of today’s best-of-breed mocking/testing tools, combining them and making them interoperable, and adding important functionality such as error injection and pluggable services. All this happening locally, without ever talking to the cloud.

Mangum is an adapter for running ASGI applications in AWS Lambda to handle Function URL, API Gateway, ALB, and Lambda@Edge events. Event handlers for API Gateway HTTP and REST APIs, Application Load Balancer, Function URLs, and CloudFront Lambda@Edge. Compatibility with ASGI application frameworks, such as Starlette, FastAPI, Quart and Django. Support for binary media types and payload compression in API Gateway using GZip or Brotli. Works with existing deployment and configuration tools, including Serverless Framework and AWS SAM. The heart of Mangum is the adapter class. It is a configurable wrapper that allows any ASGI application (or framework) to run in an AWS Lambda deployment. The adapter accepts a number of keyword arguments to configure settings related to logging, HTTP responses, ASGI lifespan, and API Gateway configuration.

doccano-client is a simple client wrapper for the doccano API. We're introducing a newly revamped Doccano API Client that features more Pythonic interaction as well as more testing and documentation. It also adds more regulated compatibility with specific Doccano release versions.

Python script to get the last 5 minutes of accepted traffic logs via the trendmicro email security API and send them to a syslog server Script Python para obtener los ultimos 5 minutos de logs de trafico aceptado por medio de la API de trendmicro email security y enviarlos a un servidor de syslog Crontab */5 * * * * /usr/local/bin/python3.9 /home/user/tmes-syslog_0.02.py 2>&1 > /home/user/errores.txt ------------ # API documentation # Getting Started with Trend Micro Email Security APIs # https://docs.trendmicro.com/en-us/enterprise/trend-micro-email-security-rest-api-online-help/getting-started-with.aspx # Obtaining the API Key # https://docs.trendmicro.com/en-us/enterprise/trend-micro-email-security-rest-api-online-help/getting-started-with/obtaining-the-api-ke.aspx # List Mail Tracking Logs # https://docs.trendmicro.com/en-us/enterprise/trend-micro-email-security-rest-api-online-help/supported-apis/logs/list-mail-tracking-l.aspx

This library helps you easily create a Python application with WhatsApp API. https://green-api.com/en/

Db Api client is a simple Python DB Api v2.0 client. It shows some information about database, tables, table\'s description. Db Api Client provides sql queries executing, shows results, and exports to some formats (html, csv).

Zappa makes it super easy to build and deploy serverless, event-driven Python applications (including, but not limited to, WSGI web apps) on AWS Lambda + API Gateway. Think of it as "serverless" web hosting for your Python apps. That means infinite scaling, zero downtime, zero maintenance - and at a fraction of the cost of your current deployments! With a traditional HTTP server, the server is online 24/7, processing requests one by one as they come in. If the queue of incoming requests grows too large, some requests will time out. With Zappa, each request is given its own virtual HTTP "server" by Amazon API Gateway. AWS handles the horizontal scaling automatically, so no requests ever time out. Each request then calls your application from a memory cache in AWS Lambda and returns the response via Python's WSGI interface. After your app returns, the "server" dies.

hug aims to make developing Python-driven APIs as simple as possible, but no simpler. As a result, it drastically simplifies Python API development. Make developing a Python-driven API as succinct as a written definition. The framework should encourage code that self-documents. It should be fast. A developer should never feel the need to look somewhere else for performance reasons. Writing tests for APIs written on-top of hug should be easy and intuitive. Magic done once, in an API framework, is better than pushing the problem set to the user of the API framework. Be the basis for next-generation Python APIs, embracing the latest technology.