429

API problem detail

Too Many Requests

Description

This problem happens when the request exceeded its rate limit. Authenticated integrations default to 600 requests per minute per integration; unauthenticated requests share a much tighter anonymous allowance (60 per minute), so always authenticate before probing. The response carries a Retry-After header with the number of seconds to wait.

Experience API error bodies also carry errorCode, resolution, and traceId. Branch on errorCode, not on title or detail; see fields on every error.

How to resolve

Honor Retry-After, then retry. When retrying an idempotent write, keep the original X-Idempotency-Key and body. Reduce polling frequency by using the events cursor (/DisbursementRequests/{id}/Events?after=...) instead of re-reading full resources in a tight loop.
Back to all problem details