Errors
HTTP errors, processing failures, and temporary service states.
The API uses standard HTTP status codes for request-time failures.
| Status | Meaning | Action |
|---|---|---|
400 | Invalid request or unsupported file input. | Correct the request before retrying. |
401 | Missing or invalid credential. | Check the bearer credential. |
402 | Insufficient account balance. | Add credit before resubmitting paid work. |
403 | The credential is valid but not allowed for the operation. | Use a dashboard session for account routes. |
404 | Resource not found or not owned by the account. | Verify the ID and credential. |
413 | The request body or uploaded file is too large. | Reduce the input or use a supported asynchronous operation. |
422 | A field or language option is invalid. | Use the discovery endpoints to validate input. |
502 | Processing returned unusable output. | Retry if appropriate and retain the original input. |
503 | A worker or queue is temporarily unavailable. | Retry with backoff and respect Retry-After when present. |
An asynchronous job can be accepted successfully and later enter failed. Read its error field and do not confuse a terminal job failure with a transient network failure during polling.