troubleshooting · 2026-09-28
Troubleshoot API 401, 403 and 429 responses
Use the response code to separate authentication, model authorization and rate-limit problems before retrying.
RelayAI · 中文
Capture a safe diagnostic record
Keep the request time, endpoint, model ID, HTTP status and request_id from the response. Do not paste an API key, prompt or personal data into a public ticket or log.
Separate 401 from 403
For 401, check the Authorization: Bearer header and whether the key is correct and active. For 403, check account verification, model authorization and enterprise key ownership. Repeated retries will not grant missing access.
Handle 429 deliberately
A 429 response means a rate limit was reached. Honor Retry-After when present. Otherwise use bounded exponential backoff with jitter and a maximum retry count. Limit client-side concurrency so retries do not create a new burst. Confirm current limits in the console, response headers or your contract.