Ninjavan Rate Limits
Ninja Van does not publish fixed numeric rate limits for the ninjaAPI in its public documentation. Practical throughput is governed by the OAuth2 token lifecycle (tokens are short-lived and should be cached and reused rather than re-minted per request; regenerate only within about five minutes of expiry or on an HTTP 401) and by the integration audit that gates production access. Access to some endpoints is explicitly gated: waybill generation requires prior approval, and the sandbox is restricted to the Singapore (sg) country code.
Ninjavan Rate Limits is the machine-readable rate-limit profile for Ninja Van on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests and tokens.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, unauthorized, and forbidden.
Tagged areas include Logistics, Last-Mile Delivery, Shipping, Southeast Asia, and Rate Limiting.
generated, dated 2026-07-12.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.