Rate limits - KetaPay Docs

Each secret key can make 100 requests per 10 seconds. Requests without a valid key share a limit per IP address. Every response tells you where you stand:

Header	Meaning
`X-RateLimit-Limit`	Requests allowed in the window
`X-RateLimit-Remaining`	Requests left in the current window
`X-RateLimit-Reset`	When the window resets, as a Unix timestamp in seconds

Over the limit

You get 429 with this error:

{
  "error": {
    "type": "rate_limit_error",
    "code": "rate_limited",
    "message": "Too many requests. Retry after the time in X-RateLimit-Reset.",
    "param": null,
    "request_id": "req_01J9ZK7M2Q4V8XW3B6N5T0R1YH"
  }
}

Wait until X-RateLimit-Reset, then retry with the same Idempotency-Key. The libraries do this for you with backoff.

Staying under it

Use webhooks instead of polling for changes.
Fetch lists with limit=100 rather than many small pages.
Give each system its own key: limits are per key.
Spread batch jobs out instead of sending them all at once.

Need more for a launch or a migration? Email developers@ketapay.com with your expected volume.