Rate Limiting
The Partner API enforces rate limits to ensure fair usage and platform stability.
Default Limits
| Endpoint | Limit (Production) | Limit (Sandbox) |
|---|---|---|
| General endpoints | 100 requests/min | 500 requests/min |
Order creation (POST /orders) | 10 requests/min | 50 requests/min |
Response Headers
Every API response includes rate limit information in the following headers:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed in the current window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp (seconds) when the rate limit window resets |
Handling 429 Responses
When you exceed the rate limit, the API returns a 429 Too Many Requests response:
{
"statusCode": 429,
"message": "Rate limit exceeded. Try again in 45 seconds.",
"error": "Too Many Requests"
}
Recommended Strategy
- Read the
X-RateLimit-Remainingheader to monitor your usage proactively. - When you receive a
429, wait until the time indicated byX-RateLimit-Resetbefore retrying. - Implement exponential backoff for retries to avoid repeated throttling.
- Cache product catalog responses where possible to reduce unnecessary requests.