Manifest for Python
An API rejects your request. Manifest fixes it and retries. You do nothing.
pip install mnfst
from mnfst import manifest
manifest() # once, at startup
# Keep making your API calls as usual.
Works with httpx (sync and async) and requests, for JSON and form-urlencoded bodies. Python 3.10+. The import name is mnfst.
Setup
- Create a project in your Manifest dashboard and copy its project key.
- Turn on Autofix in Project Settings.
- Set the key:
export MNFST_KEY='your-project-key'
Call manifest() once at startup, before your first request.
See it work
import httpx
from mnfst import manifest, flush
manifest(on_heal=lambda e: print("[manifest]", e.heal_status, e.replay_status_code))
res = httpx.post(
"https://api.example.com/orders",
json={"limit": 500}, # rejected? Manifest retries with a valid limit
)
flush(timeout=5) # short scripts only: wait for reports before exiting
Good to know
- Retries repeat side effects. Use idempotency keys on non-idempotent calls.
- A heal adds up to 60 s to a failed request. Successful requests are untouched and never contact Manifest.
- Not intercepted: custom
httpxtransports andaiohttp. - Privacy. Failed URLs, headers, JSON or form-urlencoded bodies, and error responses are sent to Manifest. Known credentials are masked, but nested secrets and business data are not. Enable it only for traffic you allow Manifest to process.
More
Configuration, limits & development · API contract · Node.js SDK
Release files for mnfst 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mnfst-0.2.0.tar.gz | 50.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mnfst-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.0 kB
Release files / mnfst-0.2.0.tar.gz
| Download URL | mnfst-0.2.0.tar.gz |
|---|---|
| Size | 50.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e95f37d0ca1f3f0bb2d523d548d09341e09641b5f7b477f7472691ce2f896ea7
|
|
BLAKE2b-256 checksum How to use checksums |
c1caaae277c4d315a2b05358731820703b4948dbd499b4b12676b0f2f2617952
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 10, 2026.
Transparency logRelease files / mnfst-0.2.0-py3-none-any.whl
| Download URL | mnfst-0.2.0-py3-none-any.whl |
|---|---|
| Size | 20.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec40709b146c337b131a5063367c540286c3f795016991f015fa8fd7341bc629
|
|
BLAKE2b-256 checksum How to use checksums |
ba69a0163501d59e4f110945f0402082149179125942554ad9a3178f958e649e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 10, 2026.
Transparency log