Error Codes Overview
THEITBULLS API uses standard HTTP status codes to indicate the success or failure of API requests. Error responses include a code and message to help with troubleshooting.
Important: Always handle errors gracefully in your applications. Implement proper error handling and logging.
HTTP Status Codes
Success (2xx)
200 OK Success
The request was successful and the server returned the requested data.
201 Created Created
The request was successful and a new resource was created.
204 No Content No Content
The request was successful but there is no content to return.
Client Errors (4xx)
400 Bad Request Bad Request
The request was invalid or malformed. Check your request payload.
401 Unauthorized Unauthorized
Missing or invalid API key. Check your authentication credentials.
403 Forbidden Forbidden
You don't have permission to access this resource. Check your API key permissions.
404 Not Found Not Found
The requested resource was not found. Check your endpoint URL.
429 Too Many Requests Rate Limit Exceeded
You have exceeded your rate limit. Implement exponential backoff and retry.
Server Errors (5xx)
500 Internal Server Error Server Error
An unexpected error occurred on the server. Please try again or contact support.
502 Bad Gateway Bad Gateway
The server received an invalid response from an upstream server. Try again later.
503 Service Unavailable Service Unavailable
The service is temporarily unavailable. Please try again later.
Error Response Format
# Example error response { "error": { "code": "rate_limit_exceeded", "message": "Rate limit exceeded. Please try again after 3600 seconds.", "details": { "limit": 100, "remaining": 0, "reset": 1614556800 }, "timestamp": "2025-06-20T14:30:00Z" } }
Common Error Codes
| Error Code | Description | Solution |
|---|---|---|
invalid_api_key |
API key is invalid or expired | Regenerate your API key |
insufficient_permissions |
API key lacks required permissions | Update API key permissions |
rate_limit_exceeded |
Rate limit exceeded | Wait and retry with backoff |
invalid_request |
Request payload is invalid | Check request body format |
resource_not_found |
Resource not found | Check resource ID or endpoint |
webhook_verification_failed |
Webhook signature invalid | Check webhook secret configuration |
Troubleshooting Tips
- Check API key: Ensure you're using the correct key (test vs live)
- Validate payload: Use JSON validators to check request structure
- Check rate limits: Monitor rate limit headers in responses
- Review logs: Check your application logs for error details
- Test in sandbox: Use sandbox environment before production
- Contact support: Reach out if issues persist
Need help with errors? Our team is here to assist.
Get Support