Skip to main content

Rate Limiting

The Business API enforces per-merchant rate limits to ensure fair usage and platform stability.

Response Headers

Every response includes rate limit headers that tell you your current quota: Check these headers on every response to know your limit and how many requests you have left.

Handling 429 Too Many Requests

When you exceed the limit, the API responds with status 429 and adds a Retry-After header:

Retry Strategy

Use exponential backoff when you receive a 429 response:

Best Practices

  • Monitor the X-RateLimit-Remaining header to proactively slow down before hitting the limit.
  • Cache responses when the data doesn’t change frequently — especially product catalogs.
  • Batch your work — fetch larger pages (up to limit=100) to reduce the number of requests.
  • Respect Retry-After — always wait the indicated time before retrying, rather than using a fixed delay.