Go to developer

rate_limited

Too many requests for this rate-limit bucket.

On this page
HTTP 429rate-limitpartner-2faoauthsharedapi

Code: rate_limited · Shape: partner

Meaning

Too many requests for this rate-limit bucket.

Likely causes

  1. Overly aggressive polling
  2. Retry storms
  3. Shared IP / key exceeding window

How to diagnose

  • Confirm HTTP 429 and error === rate_limited
  • Partner responses use { error, message }; OAuth rate limit uses { error, error_description }
  • No Retry-After / X-RateLimit-* headers are returned today

How to fix

  • Honor pollAfterMs from KEYRA responses
  • Use SDK wait helpers instead of tight manual loops
  • Back off and retry later

Retry behavior

Retry with backoff after the window. Do not tight-loop.

API: GET /v1/auth/challenge/{challengeId}, GET /v1/identities/enroll/{enrollmentId}/status, POST /oauth/authorize/init, POST /verify/validate

SDK: waitForChallengeApproval(), waitForEnrollment(), pollChallenge()

Troubleshooting: network, partner-2fa

Guides: Authentication