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.
| Endpoint | Rate Limit(req/s) |
|---|---|
| POST /2025-01/trackings | 20 |
| GET /2025-01/trackings | 6 |
| GET /2025-01/trackings/:id | 5 |
| PUT /2025-01/trackings/:id | 5 |
| DELETE /2025-01/trackings/:id | 5 |
| POST /2025-01/trackings/:id/retrack | 5 |
| POST /2025-01/trackings/:id/mark-as-completed | 5 |
| POST /2025-01/couriers/detect | 3 |
| GET /2025-01/couriers | 5 |
| GET /2025-01/couriers/all | 5 |
| POST /2025-01/estimated-delivery-date/predict | 5 |
| POST /2025-01/estimated-delivery-date/predict-batch | 20 |
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:
| Header | Example | Description |
|---|---|---|
| X-RateLimit-Reset | 1406096275 | The Unix timestamp when the rate limit will be reset. |
| X-RateLimit-Limit | 20 | The rate limit ceiling for the current endpoint per sec. |
| X-RateLimit-Remaining | 19 | The number of requests left for the 1-second window. |