Zinc API Python Library
zinc is the official SDK for the Zinc API —
search, buy, track, and return products from major online retailers
(Amazon, Walmart, and more) through a single, type-safe API.
Keywords: e-commerce API, place an order, buy products programmatically, Amazon ordering API, checkout automation, order tracking, returns, product search, AI agent commerce, autonomous purchasing, MPP / HTTP 402.
Every method is fully typed. Instantiate ZincClient once and call resource
methods on it — placing an order, searching for a product, and tracking a
shipment are each a single call. (Method names follow each language's
convention: createOrder in TypeScript, create_order in Python.)
Table of Contents
- Installation
- Reference
- Authentication
- Test Mode
- Faq
- Usage
- Environments
- Async Client
- Exception Handling
- Advanced
- Contributing
Installation
pip install zinc
Reference
A full reference for this library is available here.
Authentication
Most endpoints require a Zinc API key (prefixed zn_), sent as the
Authorization header. The value is forwarded verbatim, so pass the
Bearer prefix yourself:
import os
from zinc import ZincClient
client = ZincClient(
api_key=f"Bearer {os.environ['ZINC_API_KEY']}", # "zn_..."
# base_url defaults to https://api.zinc.com
)
The client.agent.* endpoints need no Zinc account — they are paid
per-call via MPP (HTTP 402), so an agent can order without one. They raise
PaymentRequiredError until payment is attached.
Test mode
Use a test API key (zn_test_...) to hit the sandbox — same client,
same base URL; the key prefix routes you to test data:
client = ZincClient(api_key=f"Bearer {os.environ['ZINC_TEST_KEY']}")
client.orders.list_test_products() returns product URLs that trigger
specific sandbox scenarios.
FAQ
Which version should I use? The package version mirrors the Zinc
API version (CalVer, e.g. 2026.7.17 = API 2026-07-17). Pin an exact
version or take the latest.
Do I need an account to place orders as an agent? No.
client.agent.create_mpp_order(...) settles payment via MPP (HTTP 402) —
no API key required.
How is max_price interpreted? In cents. It's a ceiling; the order
is not finalized above it.
Where are the full API docs? https://www.zinc.com/docs
Usage
Instantiate and use the client with the following:
from zinc import ZincClient, OrderProduct, Address
client = ZincClient(
api_key="<value>",
)
client.orders.create_order(
products=[
OrderProduct(
url="https://www.amazon.com/dp/B07JGBW826",
)
],
shipping_address=Address(
first_name="first_name",
last_name="last_name",
address_line1="address_line1",
city="city",
postal_code="postal_code",
phone_number="phone_number",
),
max_price=1,
)
Environments
This SDK allows you to configure different environments for API requests.
from zinc import ZincClient
from zinc.environment import ZincClientEnvironment
client = ZincClient(
environment=ZincClientEnvironment.PRODUCTION,
)
Async Client
The SDK also exports an async client so that you can make non-blocking calls to our API. Note that if you are constructing an Async httpx client class to pass into this client, use httpx.AsyncClient() instead of httpx.Client() (e.g. for the httpx_client parameter of this client).
import asyncio
from zinc import AsyncZincClient
client = AsyncZincClient(
api_key="<value>",
)
async def main() -> None:
await client.orders.create_order(
products=[
OrderProduct(
url="https://www.amazon.com/dp/B07JGBW826",
)
],
shipping_address=Address(
first_name="first_name",
last_name="last_name",
address_line1="address_line1",
city="city",
postal_code="postal_code",
phone_number="phone_number",
),
max_price=1,
)
asyncio.run(main())
Exception Handling
When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.
from zinc.core.api_error import ApiError
try:
client.orders.create_order(...)
except ApiError as e:
print(e.status_code)
print(e.body)
Advanced
Access Raw Response Data
The SDK provides access to raw response data, including headers, through the .with_raw_response property.
The .with_raw_response property returns a "raw" client that can be used to access the .headers and .data attributes.
from zinc import ZincClient
client = ZincClient(...)
response = client.orders.with_raw_response.create_order(...)
print(response.headers) # access the response headers
print(response.status_code) # access the response status code
print(response.data) # access the underlying object
Retries
The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
Which status codes are retried depends on the retryStatusCodes generator configuration:
legacy (current default): retries on
recommended: retries on
- 408 (Timeout)
- 409 (Conflict)
- 429 (Too Many Requests)
- 502 (Bad Gateway)
- 503 (Service Unavailable)
- 504 (Gateway Timeout)
Use the max_retries request option to configure this behavior.
client.orders.create_order(..., request_options={
"max_retries": 1
})
Timeouts
The SDK defaults to a 60 second timeout. You can configure this with a timeout option at the client or request level.
from zinc import ZincClient
client = ZincClient(..., timeout=20.0)
# Override timeout for a specific method
client.orders.create_order(..., request_options={
"timeout": 1
})
Custom Client
You can override the httpx client to customize it for your use-case. Some common use-cases include support for proxies
and transports.
import httpx
from zinc import ZincClient
client = ZincClient(
...,
httpx_client=httpx.Client(
proxy="http://my.test.proxy.example.com",
transport=httpx.HTTPTransport(local_address="0.0.0.0"),
),
)
Contributing
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!
Release files for zinc 2026.9.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zinc-2026.9.11.tar.gz | 118.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zinc-2026.9.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 347.2 kB
Release files / zinc-2026.9.11.tar.gz
| Download URL | zinc-2026.9.11.tar.gz |
|---|---|
| Size | 118.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef44843b42673f3bf9753fe763977687c7511ab8dc9f5b0d1d52960fa1911111
|
|
BLAKE2b-256 checksum How to use checksums |
1450d7aed10d2c65980b05846f1285f950cbd7b7420ecc5383bf6dd3f9d8ca99
|
| 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 13, 2026.
Transparency logRelease files / zinc-2026.9.11-py3-none-any.whl
| Download URL | zinc-2026.9.11-py3-none-any.whl |
|---|---|
| Size | 229.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76cf5b2545d3c5e495f9068246bb3493f45790ee942efc88d58eeac4d554eeb9
|
|
BLAKE2b-256 checksum How to use checksums |
94184a84f6d3034db401b28245857fc84c735b3ba1505d9d498bc45f60ac7c6f
|
| 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 13, 2026.
Transparency log