Documentation Index
Fetch the complete documentation index at: https://developers.explorium.ai/llms.txt
Use this file to discover all available pages before exploring further.
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
| Status Code | Type | Description |
|---|---|---|
| :--- | :--- | :--- |
| 200 | Success | Request completed successfully |
| 201 | Success | Resource created successfully |
| 400 | Client Error | Bad request - Invalid request format or parameters |
| 401 | Client Error | Unauthorized - Authentication failed |
| 403 | Client Error | Forbidden - Valid request but insufficient permissions |
| 422 | Client Error | Unprocessable Entity - Request validation failed |
| 429 | Client Error | Too Many Requests - Rate limit exceeded |
| 500 | Server Error | Internal Server Error - Unexpected server issue |
| 503 | Server Error | Service Unavailable - Temporary server issue |
Error Types
Authentication Errors (401)
| Error Message | Description | Resolution |
|---|---|---|
Partner ID is missing. Please set it in one of these headers: X-Context-Partner-ID, partner-id, partner_id. | Request missing required Partner ID header | Add Partner ID to request headers |
Partner ID is invalid. Please set the Partner ID in one of these headers: X-Context-Partner-ID, partner-id, partner_id. | Provided Partner ID is not recognized | Verify your Partner ID is correct |
Credit Errors (403)
| Error Message | Description | Resolution |
|---|---|---|
You have insufficient credits to perform this operation. Please purchase additional credits. | Credit balance too low for requested operation | Purchase additional credits or contact your account manager |
Validation Errors (422)
Validation errors return a detailed structure indicating which fields failed validation:JSON
| Field | Error Type | Message | Resolution |
|---|---|---|---|
size | value_error.number.not_le | ensure this value is less than or equal to 100 | Reduce the size parameter to ≤ 100 |
page | value_error.number.not_ge | ensure this value is greater than or equal to 1 | Page numbers start at 1 |
filters | value_error.missing | field required | Include the required filters object |
Client Errors (400)
| Error Message | Description | Resolution |
|---|---|---|
Client webhook failed on: [details] | Your webhook endpoint failed to process the event | Check webhook endpoint availability and response |
Server Errors (500)
| Error Message | Description | Resolution |
|---|---|---|
An internal server error occurred | Unexpected server error | Retry with exponential backoff; contact support if persists |
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
| Version | Date | Changes |
|---|---|---|
| v1.5 | June 2025 | Enhanced error handling with specific error codes and improved messages |
| v1.4 | - | Added 10K enrichments |
| v1.3 | - | Added prospects match |
| v1.2 | - | Added Social media posts and workforce trends |
| v1.1 | - | Added events pipelines |
| v1.0 | - | Initial release |
Need Help?Contact our support team through your dedicated Slack channel with Explorium.