Error Response Format
All errors follow a consistent JSON format:Fields
| Field | Description |
|---|---|
error | Always true for error responses |
code | Machine-readable error code |
message | Human-readable error description |
version | API version |
timestamp | ISO 8601 timestamp of the error |
details | Additional context (optional) |
HTTP Status Codes
2xx Success
200OK - Request succeeded -201Created - Resource created -204No Content - Request succeeded, no content
4xx Client Errors
400Bad Request - Invalid request -401Unauthorized - Invalid API key403Forbidden - Insufficient permissions -404Not Found - Resource not found -429Too Many Requests - Rate limited
5xx Server Errors
500Internal Server Error - Server issue -502Bad Gateway - Upstream error -503Service Unavailable - Temporary unavailability
Common Error Codes
Authentication Errors
UNAUTHORIZED (401)
- Missing
x-api-keyheader - Invalid API key format
- Expired API key
- Deactivated API key
PERMISSION_DENIED (403)
- API key lacks required permission
- Attempting to access restricted resource
Validation Errors
VALIDATION_ERROR (400)
- Missing required fields
- Invalid field formats
- Invalid field values
INVALID_LINKEDIN_URL (400)
Rate Limiting Errors
RATE_LIMIT_EXCEEDED (429)
Resource Errors
NOT_FOUND (404)
DUPLICATE_RESOURCE (409)
Integration Errors
LINKEDIN_NOT_CONNECTED (400)
ENRICHMENT_CREDITS_EXHAUSTED (402)
Error Handling Best Practices
Check Status Codes First
Check Status Codes First
Always check the HTTP status code before parsing the response:
Handle Specific Error Codes
Handle Specific Error Codes
Different errors require different handling strategies:
Implement Retry Logic
Implement Retry Logic
Retry transient errors with exponential backoff:
Log Errors Appropriately
Log Errors Appropriately
Log errors with appropriate detail levels:
Language-Specific Examples
JavaScript/TypeScript
Python
Error Monitoring
Setting Up Alerts
Need Help?
If you’re experiencing persistent errors or need assistance:Check Status Page
See if there are any known issues
Contact Support
Email our support team with error details
Discord Community
Get help from other developers
Documentation
Review the full API reference
- API key prefix (first 8 characters)
- Error response with timestamp
- Request details (endpoint, method, payload)
- Expected vs actual behavior

