Skip to content

Too Many Requests

URI: https://docs.ankatech.co/errors/too-many-requests
HTTP Status: 429 Too Many Requests

When you see this

You have sent more requests than the endpoint's rate limit allows within the current window. Further requests are rejected until the limit resets.

Common Causes

  • Exceeding the per-client or per-tenant request quota for the endpoint.
  • A burst of requests (for example a tight retry loop) overrunning the configured rate.
  • Multiple clients sharing the same credentials and collectively exceeding the limit.

Response Example

{
  "type": "https://docs.ankatech.co/errors/too-many-requests",
  "title": "Too Many Requests",
  "status": 429,
  "detail": "Rate limit exceeded. Retry after the period indicated by the Retry-After header.",
  "instance": "/api/v3/audit/tenant/crypto",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

Content-Type: application/problem+json — the response follows RFC 7807 Problem Details.

How to Resolve

  1. Inspect the Retry-After header and wait the indicated number of seconds before retrying.
  2. Apply client-side throttling and exponential backoff to smooth out request bursts.
  3. Reduce request frequency, batch where possible, or distribute load across time.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.