Rate Limiting

Exceeding the limitCopy Anchor Link

Once the limit is exceeded, the API returns 429 Too Many Requests with a Retry-After header giving the number of seconds to wait before the window resets:

HTTP/1.1 429 Too Many Requests
Retry-After: 42
X-Request-Id: 8fae367bba5424e543023918ce4c5c98

{
  "error": {
    "status": "Too Many Requests",
    "requestId": "8fae367bba5424e543023918ce4c5c98",
    "details": {
      "message": "Rate limit exceeded"
    }
  }
}

See Errors for the full response envelope and header reference.

Handling 429sCopy Anchor Link

Wait at least Retry-After seconds before retrying. Clients that poll the API should space out requests rather than retrying in a tight loop.