Rate Limits

All API endpoints are rate limited per API key to ensure fair usage and platform stability.

Current Limits

The sustained limit of 300 req/min supports a full catalog sync (~40,000 items at ?limit=200) in under 45 seconds. The order creation limit is lower because each order triggers downstream processing.

Rate Limit Headers

Every response includes headers indicating your current usage:

Exceeding the Limit

When you exceed the rate limit, the API returns a 429 Too Many Requests response:

Code
 
{
  "error": {
    "code": "RATE_LIMITED",
    "message": "Rate limit exceeded. Retry after the reset window.",
    "request_id": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Best Practices

• Monitor the x-ratelimit-remaining header to proactively throttle requests
• Use modified_after filters for incremental syncing instead of full re-fetches
• Set ?limit=200 when syncing large datasets to minimize the number of requests
• Implement exponential backoff when you receive a 429 response
• Cache responses where possible to reduce unnecessary calls