Serverless event-driven queues, background jobs, and scheduled jobs for Python.
Add durable functions and workflows to any framework and platform.
Inngest Python SDK
Inngest's SDK adds durable functions to Python in a few lines of code. Using this SDK, you can write background jobs as step functions without new queueing infrastructure such as celery.
We currently support the following frameworks (but adding a new framework is easy!):
- DigitalOcean Functions
- Django (
>=5.0) - FastAPI (
>=0.110.0) - Flask (
>=3.0.0) - Tornado (
>=6.4)
Python 3.10 is the minimum version we support.
Getting started
Examples
💡 You can mix
asyncand non-asyncfunctions in the same app!
Basic (no steps)
This is a minimal example of an Inngest function:
import flask
import inngest.flask
import requests
inngest_client = inngest.Inngest(
app_id="flask_example",
is_production=False,
)
@inngest_client.create_function(
fn_id="find_person",
trigger=inngest.TriggerEvent(event="app/person.find"),
)
def fetch_person(ctx: inngest.ContextSync) -> dict:
person_id = ctx.event.data["person_id"]
res = requests.get(f"https://swapi.dev/api/people/{person_id}", verify=False)
return res.json()
app = flask.Flask(__name__)
# Register functions with the Inngest server
inngest.flask.serve(
app,
inngest_client,
[fetch_person],
)
app.run(port=8000)
Each function is automatically backed by its own queue. Functions can contain steps, which act as code level transactions. Each step retries on failure, and runs once on success. Function state is automatically managed.
Let's run the function. Send the following event in the local development server (Dev Server UI) and the fetch_person function will run:
{
"name": "app/person.find",
"data": {
"person_id": 1
}
}
Step run
The following example registers a function that will:
- Get the person ID from the event
- Fetch the person with that ID
- Fetch the person's ships
- Return a summary dict
@inngest_client.create_function(
fn_id="find_ships",
trigger=inngest.TriggerEvent(event="app/ships.find"),
)
def fetch_ships(ctx: inngest.ContextSync) -> dict:
"""
Find all the ships a person has.
"""
person_id = ctx.event.data["person_id"]
def _fetch_person() -> dict:
res = requests.get(f"https://swapi.dev/api/people/{person_id}", verify=False)
return res.json()
# Wrap the function with step.run to enable retries
person = step.run("fetch_person", _fetch_person)
def _fetch_ship(url: str) -> dict:
res = requests.get(url)
return res.json()
ship_names = []
for ship_url in person["starships"]:
# step.run works in loops!
ship = step.run("fetch_ship", _fetch_ship, ship_url)
ship_names.append(ship["name"])
return {
"person_name": person["name"],
"ship_names": ship_names,
}
Send the following event in the Dev Server UI and the fetch_person function will run:
{
"name": "app/ships.find",
"data": {
"person_id": 1
}
}
Async function
@inngest_client.create_function(
fn_id="find_person",
trigger=inngest.TriggerEvent(event="app/person.find"),
)
async def fetch_person(ctx: inngest.Context) -> dict:
person_id = ctx.event.data["person_id"]
async with httpx.AsyncClient(verify=False) as client:
res = await client.get(f"https://swapi.dev/api/people/{person_id}")
return res.json()
Sending an event outside a function
Sometimes you want to send an event from a normal, non-Inngest function. You can do that using the client:
inngest_client.send_sync(inngest.Event(name="app/test", data={"person_id": 1}))
If you prefer async then use the send method instead:
await inngest_client.send(inngest.Event(name="app/test", data={"person_id": 1}))
Using in production
The Dev Server is not used in production. Inngest Cloud is used instead.
The INNGEST_EVENT_KEY and INNGEST_SIGNING_KEY environment variables must be set. These secrets establish trust between Inngest Cloud and your app. We also use request signature verification to mitigate man-in-the-middle attacks. You can read more about environment variables in our docs.
Your Inngest client must be in production mode. This is typically done with an environment variable:
inngest_client = inngest.Inngest(
app_id="my_app",
is_production=os.getenv("INNGEST_DEV") is None,
)
2 maintainers
Metadata
2 maintainers
Release files for inngest 0.5.19
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| inngest-0.5.19.tar.gz | 109.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inngest-0.5.19-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 261.0 kB
Release files / inngest-0.5.19.tar.gz
| Download URL | inngest-0.5.19.tar.gz |
|---|---|
| Size | 109.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7be69f9dc4b4bd2d4ceab06e2a4e8cdbf48bb705904faccb926ba23224637e0
|
|
BLAKE2b-256 checksum How to use checksums |
27c830524cd80447ba6abff85f4c2a3a536da9a55a6bb6d997cddfe2576076a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logRelease files / inngest-0.5.19-py3-none-any.whl
| Download URL | inngest-0.5.19-py3-none-any.whl |
|---|---|
| Size | 151.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d4804c49c0a4e3e4bb8adf603f19a2daf2d433ba743bd8958116f6c76a9b028
|
|
BLAKE2b-256 checksum How to use checksums |
ebfbe395348a44fe2332973db228c90c1f2ca9be921bdc8aa3d06dfaa50e63c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logSecurity for inngest 0.5.19
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for inngest-0.5.19.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
