Skip to main content
The Kua API applies fair-use rate limits to keep the platform responsive for everyone. Limits are generous for normal integration traffic; you’ll only meet them if you loop tightly or fan out heavily.

​
When you’re limited

A throttled request returns HTTP 429 Too Many Requests with the standard error body. Back off and retry — the limit is a short rolling window, so a brief pause clears it.

​
Handling it gracefully

  • Back off exponentially. On a 429, wait a moment and retry, increasing the delay each attempt (e.g. 1s, 2s, 4s) with a little random jitter.
  • Prefer webhooks over polling. If you’re calling /v1/events in a tight loop to react to changes, register a webhook instead — Kua pushes events to you, so you make far fewer requests.
  • Batch where you can. Page with a larger limit rather than many small requests.
Retrying a write after a 429? Send the same Idempotency-Key you used on the first attempt, so the retry can’t create a duplicate.

​
Need a higher limit?

If your integration has a legitimate need for more headroom, reach out at [email protected] and we’ll work with you.