Error Handling

All API endpoints use a consistent error response model.
When a request fails, use the HTTP status code and error message to identify the cause.

Common Status Codes

Status	Meaning	Typical Cause
400 Bad Request	Invalid request payload	Missing required fields, invalid format, invalid asset input
401 Unauthorized	Authentication failed	Missing, expired, or invalid Bearer token / API key
403 Forbidden	Permission denied	Credential does not have the required scope
413 Payload Too Large	Input too large	File or remote asset exceeds configured size limits
422 Unprocessable Entity	Validation failed	Body/query/path parameters fail schema validation
429 Too Many Requests	Rate or quota limit hit	Request frequency or usage exceeded current quota
500 Internal Server Error	Internal failure	Unexpected service-side error
502 Bad Gateway	Upstream service error	Model/storage upstream returned invalid response
503 Service Unavailable	Temporary unavailable	Backend dependency is down or overloaded

Troubleshooting Tips

• Verify request payload type and required fields first.
• Confirm Authorization header is valid and not expired.
• For 429, retry with backoff and review your quota plan.
• For 5xx, retry later; if persistent, include request details when contacting support.