Programmatic access to supply chain intelligence, landed cost calculation, HS code lookup, and order data over a REST API with JSON responses.
All API requests require a valid API key. Generate one in Settings → API Keys. Pass it via either header:
X-API-Key header
X-API-Key: zf_live_your_key_hereAuthorization: Bearer
Authorization: Bearer zf_live_your_key_herehttps://api.zentriaflow.com/api/v1/Machine-readable description: OpenAPI spec (OpenAPI 3.1, JSON). It covers the tariff and landed-cost endpoints and the free tariff endpoints that need no key, with request and response schemas, plan quotas and error codes. Import it into an API client or a code generator.
All endpoints return JSON. Errors follow { detail: string } format.
/api/v1/meReturns account info, plan, and scopes for the authenticated API key.
Response
{
"user_id": "usr_abc123",
"email": "[email protected]",
"plan": "professional",
"api_key_name": "My Claude Agent",
"scopes": ["read", "write"]
}Example
curl https://api.zentriaflow.com/api/v1/me \ -H "X-API-Key: zf_live_your_key"
Two events exist today, both about your Watchlist. On the Scale API plan and Enterprise they are pushed to your own https URL, signed, when the Watchlist re-price finds a tariff change on a product you watch. Register the URL with POST /api/v1/hooks. On every plan with Watchlist access (Scale API and higher, Professional, Enterprise) you can also poll GET /api/v1/watchlist/changes, where every change has a stable id. Unsigned hooks to a hooks.zapier.com URL are for the Zapier integration, which is coming soon and not yet published.
watch.tariff_changedA tariff change moved the cost of a watched product
watch.createdA product was added to the Watchlist
Each delivery is a JSON POST with the keys of the matching list endpoint and the headers X-Zentria-Event, X-Zentria-Hook-Id, X-Zentria-Delivery (the same on every retry of one event, so you can ignore a repeat) and X-Zentria-Signature.
The header is t=<unix seconds>,v1=<hex>, where v1 is the HMAC-SHA256 of <t>.<raw request body> keyed with the signing secret you received when you created the hook. Compute it over the raw bytes, before parsing the JSON, compare in constant time, and refuse a timestamp older than five minutes.
import hashlib, hmac, time
def verify(secret: str, signature_header: str, raw_body: bytes, tolerance_s: int = 300) -> bool:
parts = dict(p.split("=", 1) for p in signature_header.split(","))
t, v1 = parts["t"], parts["v1"]
if abs(time.time() - int(t)) > tolerance_s:
return False # too old: possibly a replay
expected = hmac.new(secret.encode(), t.encode() + b"." + raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, v1)
# secret = the signing_secret from POST /api/v1/hooks
# signature_header = the X-Zentria-Signature request headerGET /api/v1/watchlist/changes always has the full list.disabled_at. A successful POST /api/v1/hooks/{id}/test switches it back on.API access is included in the Professional and Enterprise subscriptions. Keys are scoped to your own account data.
| Plan | API Access | Req / min | Req / day | Key prefix |
|---|---|---|---|---|
| Free | No access | — | — | — |
| Growth | No access | — | — | — |
| Professional | Enabled | 60 | 500 | zf_live_ |
| Enterprise | Enabled | 300 | 5,000 | zf_live_ |
Exceeded limits return 429 Too Many Requests with Retry-After and X-RateLimit-Reset headers.
Building a logistics platform, freight quoting tool, procurement system, or AI agent that needs duty rates and landed cost? The API plans below are sold separately from the web app subscriptions, with monthly call quotas instead of daily ones.
API-plan keys are created the same way, at Settings → API Keys.
Scale API
📦 50,000 calls / mo
⚡ 200 rpm
🔒 Priority email support
Production platforms
Start Scale APIEnterprise
📦 Unlimited
⚡ Unlimited
🔒 SLA agreed in contract
Dedicated support & contract
Contact usIf your product sends us customers (your users sign up for their own Zentria Flow accounts after using your integration), you earn 20% of their subscription payments for their first 12 months, on the same terms as the partner program.
See the partner program →What exists today, and what does not yet. Anything not listed here reaches Zentria Flow by calling the REST API.
Available
Landed cost, HS code lookup and US tariff layers over HTTPS with an API key. JSON in, JSON out.
API reference →Available
An OpenAPI 3.1 description of the tariff and landed-cost endpoints, for API clients and code generators.
openapi.json →Available, no key
US tariff layers by HTS code and origin, and HTSUS line search. Tariff checks: 60 an hour per IP address. HTS search: 600 an hour. They are in the OpenAPI spec under "Free tools".
Try the checker →Available on GitHub
A Model Context Protocol server for Claude, Cursor, VS Code and other MCP clients: US tariff layers by HTS code and origin, origin comparison, HTSUS search, and landed cost with an API key. Install with: npx -y github:orhansavash/zentria-flow-mcp. Not on npm or in the official MCP registry yet.
zentria-flow-mcp on GitHub →Listed on WordPress.org
Landed cost and duty estimates inside a WooCommerce store.
WooCommerce plugin →In development, not on Zapier yet
Landed cost, tariff lookups and Watchlist alerts in Zaps. It is not available on Zapier yet.
Not on the Shopify App Store yet
The Shopify app is not on the Shopify App Store yet.
Shopify page →Subscriber? Generate an API key from your dashboard in seconds.
Builder? Start with the free Sandbox (100 calls a month) or ask us about an API plan.