Rate Limits

Respect per-key limits and rate-limit response headers.

Rate limits apply per API key across all public endpoints.

Limits

EnvironmentLimitWindow
Test Sandbox60 requests60 seconds
Live Production120 requests60 seconds

A retry is still an HTTP request and counts against the limit.

Headers

Authenticated responses include:

HeaderMeaning
RateLimit-LimitMaximum requests in the current window
RateLimit-RemainingRequests remaining
RateLimit-ResetSeconds until the window resets
Retry-AfterSeconds to wait after a 429 response

Rate-limit response

{
  "success": false,
  "error": {
    "code": "RATE_LIMIT_EXCEEDED",
    "message": "Too many requests. Retry after the current rate limit window resets.",
    "requestId": "550e8400-e29b-41d4-a716-446655440005"
  },
  "billing": {
    "amount": 100,
    "currency": "NGN",
    "unit": "naira",
    "charged": false,
    "note": "No charges"
  }
}

Client behavior

  • Read Retry-After instead of guessing a delay.
  • Add jitter when many workers share one key.
  • Avoid retry loops for non-transient errors.
  • Use separate API keys for independent applications when operational isolation is required.

Did this page help you?