Error Response Format
All errors return JSON with anerror field:
HTTP Status Codes
| Code | Status | Meaning |
|---|---|---|
| 200 | OK | Request successful |
| 201 | Created | Resource created successfully |
| 400 | Bad Request | Invalid request parameters |
| 401 | Unauthorized | Missing or invalid API key |
| 402 | Payment Required | Insufficient balance |
| 403 | Forbidden | Access denied to resource |
| 404 | Not Found | Resource not found |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Server error (contact support) |
Common Errors
401 Unauthorized
- Missing
X-API-Keyheader - Invalid API key format
- Deleted or expired key
402 Payment Required
- Not enough credit for operation
- Balance below estimated cost
400 Bad Request
- Invalid video URL
- Missing required fields
- Invalid parameter values
404 Not Found
- Invalid video ID
- Video deleted
- Access to different organization’s resource
429 Rate Limit Exceeded
- Too many requests in short time
- Exceeded plan rate limit
Error Handling Best Practices
Implement Retry Logic
Implement Retry Logic
Handle All Status Codes
Handle All Status Codes
Log Errors for Debugging
Log Errors for Debugging
Video-Specific Errors
Video Not Found or Private
- Video is private or deleted
- Invalid video URL
- Age-restricted content
Platform Error
- Platform temporarily unavailable
- Video removed by platform
- Platform blocking requests
