Rate limit

Starting with the 2024-07 version, the rate limit for the AfterShip Tracking API will be updated from 10 requests/sec per organization to different rate limits for each endpoint. The specific rate limit for each endpoint is outlined in the table below.

EndpointRate Limit(req/s)
POST /2025-04/trackings20
GET /2025-04/trackings6
GET /2025-04/trackings/:id5
PUT /2025-04/trackings/:id5
DELETE /2025-04/trackings/:id5
POST /2025-04/trackings/:id/retrack5
POST /2025-04/trackings/:id/mark-as-completed5
POST /2025-04/couriers/detect3
GET /2025-04/couriers5
POST /2025-04/estimated-delivery-date/predict5
POST /2025-04/estimated-delivery-date/predict-batch20
POST /2025-04/courier-connections5
GET /2025-04/courier-connections5
GET /2025-04/courier-connections/:id5
PATCH /2025-04/courier-connections/:id5
DELETE /2025-04/courier-connections/:id5

Please give us time to process your requests. If you're sending too many requests too quickly, we'll respond with a 429 error code (TooManyRequests).

The API response headers also give you the following rate limit detailed information:

HeaderExampleDescription
X-RateLimit-Reset1406096275The Unix timestamp when the rate limit will be reset.
X-RateLimit-Limit20The rate limit ceiling for the current endpoint per sec.
X-RateLimit-Remaining19The number of requests left for the 1-second window.