Anis Partners for Python 2.1.0
The Python client for the Anis Partner API. It signs every request, verifies every answer Anis signs, and gives each operation a typed result. The details that can cause duplicate purchases or expose unverified credentials are handled explicitly: caller-owned order ids, recovery outcomes, and response verification have no silent shortcuts.
Disclaimer. This SDK is an optional helper provided free of charge under the MIT License, "as is", without warranty of any kind. Anis (Aniscom for Technical Services) accepts no responsibility or liability for its use or for any loss arising from it. You remain responsible for your own integration — recording orders before you send them, recovery, key custody and testing. The source code is public: read it to understand exactly what it does before you rely on it. You do not need an SDK — you can integrate directly with the Anis Partner API using the documentation at https://developers.anis.ly.
pip install anis-partners==2.1.0
# or
uv add anis-partners==2.1.0
- Getting started — enrollment, configuration, first call, sync and async use
- Orders and recovery — read before placing an order
- Routes and permissions — routes, permissions, bodies, and limits
- Errors — stable error codes and typed exceptions
- Security and key custody
- Observability
- Signing key cache — shared cache for multi-process applications
- Runnable sample
Quick start
from anis_partners import AnisPartnersClient, ClientOptions, PemP256Signer
options = ClientOptions("https://<authority Anis gave you>")
signer = PemP256Signer.from_pem_file("/secure/partner-key.pem").for_key("<active key id>")
with AnisPartnersClient(options, signer) as anis:
profile = anis.profile.get()
wallets = list(anis.wallets.list()) # follows every cursor page
print(profile.application.id if profile.application else "No application")
print(f"Found {len(wallets)} wallets")
if wallets:
print(wallets[0].balance.currency)
The async client returns the same results. Run the whole flow inside an event loop:
import asyncio
from anis_partners import AsyncAnisPartnersClient, ClientOptions, PemP256Signer
async def main() -> None:
options = ClientOptions("https://<authority Anis gave you>")
signer = PemP256Signer.from_pem_file("/secure/partner-key.pem").for_key("<active key id>")
async with AsyncAnisPartnersClient(options, signer) as anis:
profile = await anis.profile.get()
wallets = [wallet async for wallet in anis.wallets.list()]
print(profile.application.id if profile.application else "No application")
print(f"Found {len(wallets)} wallets")
if __name__ == "__main__":
asyncio.run(main())
For order creation and recovery, persist the operation id and exact request before calling the SDK. See Orders and recovery for the complete outcome rules.
Refusals built into the design
The caller supplies the order id. A dropped answer followed by a new id could buy twice, so the SDK never invents this identity. The five order result types distinguish a completed sale, processing, a replay, a definitive refusal, and an unknown outcome. Only the first completion returns credentials; a replay never repeats them.
An unknown result means the original sale may have completed. Resume with the same id and body. A new purchase uses a new id only after a definitive OrderNotPlaced result and a changed intent.
Anis signs the answers that move money, deliver card codes, or establish a key: order creation and order reads, both reveals, application suspension, key revocation, the four enrollment routes, and the signature self-test. On those routes every answer, success or refusal, is verified, and verification cannot be disabled. If such an answer cannot be verified — including one that arrives with no signature — its body is discarded and UnverifiableResponseError is raised. An unverifiable order answer is OrderOutcomeUnknown, because the sale may already have completed.
The information reads — profile, wallets, the catalogue, and the owned-card list and read — are answered unsigned and read without verification. Which routes are signed is fixed per route in the SDK (PartnerRoute.signs_response in PARTNER_ROUTES); it is never decided by whether an answer happens to carry a signature. See Routes and permissions.
What is covered
The SDK covers all 22 published routes across access, profile, wallets, catalogue, orders, owned_cards, and diagnostics, plus the enrollment client. Public errors are generated from the error catalogue. Request, response, safety-code, and enrollment vectors are tested along with signed in-memory client flows and contract drift checks.
This package follows the published Partner SDK contract. Supported Python versions are 3.11–3.14.
Signing-key documents are cached for five minutes by default and at most five minutes, including their original age in a shared cache. Unknown response key ids trigger at most one refresh per 30 seconds per key source, including failures. Anis publishes retired response keys for 90 days after retirement and compromised key ids in revoked[] for 90 days; see Security and key custody.
Live verification
Version 1.x was verified end to end against a live Anis environment in October 2026. Version 2.x has not had a live run yet.
Regenerating error types
src/anis_partners/errors/_codes.py is generated from contracts/error-catalogue.json. Regenerate it with:
uv run python tools/generate_errors.py
Do not edit the generated file by hand; the contract drift test checks it.
License
MIT © 2026 Aniscom for Technical Services (Anis).
2.0.0 API shapes
Use anis.catalogue.get_card(wallet_id, card_id) for one wallet-priced catalogue card. Owned cards use anis.owned_cards and /owned-cards paths. A MaskedCard exposes sold_card_id, operation_id, and a shared CardSummary at card; face value, logo, subcategory and category belong to that summary. Reveals and order sold_cards carry the full RevealedCredential with the same summary. Wallet currency is wallet.balance.currency.
Self-service stops return signed state: anis.access.suspend_application(reason) and anis.access.revoke_key(key_id, reason). Reasons are required and trimmed to 1–500 characters. Resume is staff-only; a revoked key never works again. Both stop calls use a fresh nonce and a body digest without an idempotency key.
1.x is deprecated — upgrade to 2.1.0.
Metadata
Release files for anis-partners 2.1.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 | Provenance | Actions |
|---|---|---|---|---|
| anis_partners-2.1.0.tar.gz | 177.9 kB | With provenance | Details for anis_partners-2.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anis_partners-2.1.0-py3-none-any.whl | Python 3 | none | any | Details for anis_partners-2.1.0-py3-none-any.whl |
Total release size: 269.9 kB
Release files / anis_partners-2.1.0.tar.gz
| Download URL | anis_partners-2.1.0.tar.gz |
|---|---|
| Size | 177.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af0fe6f62fa03b51982e3886982c5bb73e8d18cba179599e96f2b7c008118932
|
|
BLAKE2b-256 checksum How to use checksums |
5d22e5c9f113f3e0eeeee047a5733eac585bb5f6491734a5d69c7227a8fbfbc9
|
| 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 Oct 18, 2026.
Transparency logRelease files / anis_partners-2.1.0-py3-none-any.whl
| Download URL | anis_partners-2.1.0-py3-none-any.whl |
|---|---|
| Size | 92.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a0cf93ed2f8a1a9643d5181925a43ebca53f728df60d7e7397be042be5604e7b
|
|
BLAKE2b-256 checksum How to use checksums |
9fd6bdce33e29ac98bffe7eccd01bcc60cb09d5e3a4377d389f132e1a808aef6
|
| 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 Oct 18, 2026.
Transparency logSecurity for anis-partners 2.1.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for anis_partners-2.1.0.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 Oct 18, 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.