Reference

Rate Limits

Handle rate limit responses and retryable failures.

Modified at Apr 28, 2026, 05:38 AM UTC

When a route is rate limited, the API returns 429 RATELIMIT_EXCEDED_ERROR.

{  "error": true,  "code": "RATELIMIT_EXCEDED_ERROR",  "message": "Upps, terlalu banyak permintaan, coba lagi nanti.",  "traceId": "01234567-89ab-cdef-0123-456789abcdef"}

Possible headers:

HeaderMeaning
X-RateLimit-LimitMaximum requests in the active window.
X-RateLimit-RemainingRequests left in the active window.
X-RateLimit-ResetUnix timestamp when the window resets.
Retry-AfterSeconds to wait before retrying.
X-RateLimit-PolicyHuman-readable policy label when configured.

Use backoff for 429 and 503 responses. Avoid retrying write requests unless the endpoint has an idempotency mechanism, such as transfer idempotency keys.