AxleHire (Jitsu) · Rate Limits

Axlehire Rate Limits

Jitsu (formerly AxleHire) publishes one account-wide rate limit for the v3 REST API — 10 requests per second with a short burst allowance — enforced identically in staging and production. Exceeding it returns HTTP 429. No rate-limit response headers are published, so a client cannot see its remaining budget; the documented remedy is client-side exponential backoff.

Axlehire Rate Limits is the machine-readable rate-limit profile for AxleHire (Jitsu) on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 1 rate-limit definition, measuring requests_per_second.

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

Tagged areas include Rate Limiting, Logistics, and Last Mile Delivery.

1 Limits Throttle: 429
Rate LimitingLogisticsLast Mile Delivery

Limits

All API requests account
requests_per_second · second
10

Policies

Exponential backoff
On 429, retry with exponential backoff — 1s, 2s, 4s, 8s, capped at 60s — with ±10–20% random jitter to avoid thundering-herd retries.
Retry classes
Retry 429, 500, 502 and 503 with backoff. Do not retry 400, 401, 403, 404, 405, 406, 412 or 422 — fix the request instead.
Load testing
Staging enforces the same 10 QPS as production. Higher limits for load testing must be arranged with the Jitsu team in advance.

Sources