Skip to main content

Error Response Format

When an API request fails, the response body contains a detail field describing what went wrong:
Rate limit errors use a different format with additional context:

HTTP Status Codes

Success Codes

Client Error Codes

Server Error Codes

Error Handling Examples

Common Error Scenarios

Make sure you’re sending the X-API-Key header with a valid key. Keys use the otr_ prefix.
Each workspace enforces unique lead emails. If you get a 409, the lead already exists. Use the List Leads endpoint with search to find the existing lead, then update it instead.
Check that required fields are present and values match expected formats. For example, email must be a valid email address, and status must be one of the allowed values.
You’ve exceeded 100 requests per minute. Check the Retry-After header and wait before retrying. See Rate Limiting for strategies to avoid hitting limits.