Skip to content
PuraPura Developers
Developers/Errors and troubleshooting

Errors and troubleshooting

Stable codes, correct actions and uncertain outcomes.

Authentication and consent

401: missing, expired or revoked access token. The SDK attempts refresh when applicable. invalid_grant from the token endpoint indicates an invalid refresh/code or revoked family: restart Connect. 403 insufficient_scope requires consent with the appropriate scopes.

Limits and models

402 weekly_limit_exceeded: wait for weekly_reset_at. 402 monthly_limit_exceeded: wait for period_end and a paid renewal. 402 subscription_inactive: check account status and payment in the console. 403 subscription_model_not_allowed indicates a server configuration inconsistent with the plan: contact Pura instead of choosing a client model.

429 subscription_requests_pending: two account requests are still running or awaiting accounting. Do not bypass the limit through another app. If a request had an uncertain outcome, wait for recovery or contact support.

Uploads and audio

413 invalid_transcription_file_size: empty or oversized file. 400/422: invalid fields, format or body; model is not accepted. 503 integration_chat_not_configured or subscription_transcription_not_configured: the service is not configured on the server yet.

Unavailability

503 subscription_exchange_rate_unavailable: no valid ECB reference; wait for restoration. 503 subscription_key_provisioning_unavailable: the gateway did not finish internal key management. 502 indicates an unusable response or compliance proof. Do not replace these conditions with an unverified provider.

Support information

Collect client_id, UTC timestamp, endpoint, HTTP status and error code. For webhooks include event_id and sequence. Do not include access/refresh tokens, client secrets, signing secrets, audio or prompts in logs and tickets. Delayed usage updates can be normal callback completion.