API Reference
Errors
Error codes and handling
Error Handling
All error responses follow a consistent JSON format:
{
"error": "Human-readable error message"
}Some errors include additional fields depending on the error type.
HTTP Status Codes
| Status | Meaning |
|---|---|
| 400 | Bad Request -- invalid or missing parameters |
| 401 | Unauthorized -- authentication failed |
| 402 | Payment Required -- insufficient balance |
| 403 | Forbidden -- access denied |
| 404 | Not Found -- resource not found |
| 500 | Server Error -- something went wrong on our end |
Handling Errors by Status
400 -- Bad Request
Check that all required parameters are present and valid. The error message will indicate what needs to be corrected.
401 -- Unauthorized
Your API key is missing, invalid, or has been revoked. Verify your key in the dashboard.
402 -- Payment Required
Your balance is too low to run this job. Add credits or a payment method via the dashboard.
403 -- Forbidden
Your account may be suspended or the key may not have access to the requested resource.
404 -- Not Found
The requested resource doesn't exist or isn't accessible with your current key.
Retry Strategy
- 401, 402, 403 -- Do not retry. Fix the underlying issue first.
- 500 -- Safe to retry with exponential backoff (max 3 attempts).
- Timeouts -- Research jobs can take minutes. Increase your polling timeout, not your request timeout.