Zencargo · Rate Limits

Zencargo Rate Limits

Zencargo does not publish numeric rate limits for its GraphQL API in the public documentation. As a customer-provisioned enterprise API, throttling and fair-use limits are governed per account and coordinated with the customer's account manager rather than advertised as a public per-minute cap. For webhooks, Zencargo documents an operational reliability policy rather than a rate limit: each delivery has a five-second response timeout, failed deliveries are retried up to five times over the following five hours, and a subscription is automatically disabled after five consecutive failures (with a warning email to the registered contact).

Zencargo Rate Limits is the machine-readable rate-limit profile for Zencargo on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, seconds, retries, and consecutive_failures.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Freight Forwarding, Supply Chain, GraphQL, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Freight ForwardingSupply ChainGraphQLRate LimitingQuotas

Limits

GraphQL API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the GraphQL API; governed per enterprise account.
Webhook Delivery Timeout webhook
seconds
5
Zencargo waits five seconds for a 200 response from the customer's callback URL.
Webhook Retry Attempts webhook
retries
5
Failed deliveries are retried up to five times over the following five hours.
Webhook Auto-Disable Threshold webhook
consecutive_failures
5
After five consecutive failures the webhook subscription is automatically disabled.

Policies

Webhook Retry
Failed webhook deliveries are retried 5 times over 5 hours before the subscription is disabled.
No Redirect Following
Webhook callbacks must return a 2XX directly; 3XX redirects are treated as an error (Zencargo does not follow them).
Backoff Strategy
Clients of the GraphQL API should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/zencargo-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.