Overview
The Explorium API uses standard HTTP response codes to indicate the success or failure of requests. Responses include detailed error information to help you identify and resolve issues quickly.Error Response Format
All error responses follow a consistent structure:JSON
ImportantThe
correlation_id is crucial for troubleshooting. Always include it when contacting support.HTTP Status Codes
Error Types
Authentication Errors (401)
Credit Errors (403)
Validation Errors (422)
Validation errors return a detailed structure indicating which fields failed validation:JSON
Client Errors (400)
Server Errors (500)
Rate Limiting
When you exceed API rate limits, you’ll receive a429 response:
JSON
X-RateLimit-Limit: Maximum requests per windowX-RateLimit-Remaining: Requests remaining in current windowX-RateLimit-Reset: Unix timestamp when limit resets
Best Practices
DO
- Log correlation IDs for all errors to facilitate debugging
- Implement retry logic with exponential backoff for 5xx errors
- Monitor credit usage to avoid unexpected 403 errors
- Validate requests client-side to minimize 422 errors
- Handle rate limits gracefully using the retry_after value
DON’T
- Don’t retry 4xx errors without fixing the root cause
- Don’t ignore correlation IDs when reporting issues
- Don’t make parallel requests that might exceed rate limits
- Don’t cache error responses
Error Handling Examples
Troubleshooting
Quick Troubleshooting Tips
- 401 Errors: Double-check your Partner ID and API key
- 403 Errors: Verify your credit balance in the dashboard
- 422 Errors: Review the validation error details and adjust your request
- 429 Errors: Implement rate limiting in your application
- 500 Errors: These are usually temporary - retry with exponential backoff
Change Log
Need Help?Contact our support team through your dedicated Slack channel with Explorium.