Troubleshooting
Understanding 401, 402, 422 and 429
The four errors worth handling explicitly, and which of them a retry can fix.
Every error response carries a machine-readable code alongside the HTTP status. Branch on the code, not on the message text.
401 unauthorized
Missing, malformed, revoked or unknown key. The usual cause is a bare key with no Bearer prefix. Retrying will not help until the header is fixed.
402 insufficient_credits
The key is valid but the balance is zero. Retry once credits are available; nothing was charged.
422 unsupported_platform
The input cannot work at all - an unsupported platform, a page rather than a video, or a podcast link with no public feed. This is the one that never succeeds on retry. A retry loop here burns requests for nothing.
429 rate_limited
Too many requests. Wait the number of seconds in Retry-After, then continue.
5xx
502 and 503 mean the upstream platform or our scraper was briefly unreachable. These are safe to retry with backoff.
Every one of these is documented with an example response. If you are still stuck, the support chat reaches a person.
More in Troubleshooting
Still stuck?
Open the chat launcher, bottom right, and include your request_id if you have one. Or email [email protected].