Error Response Format
When an API request fails, the response body contains adetail field describing what went wrong:
HTTP Status Codes
Success Codes
Client Error Codes
Server Error Codes
Error Handling Examples
Common Error Scenarios
401 — Invalid or missing API key
401 — Invalid or missing API key
Make sure you’re sending the
X-API-Key header with a valid key. Keys use the otr_ prefix.409 — Duplicate lead email
409 — Duplicate lead email
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.422 — Validation error
422 — Validation error
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.429 — Rate limit exceeded
429 — Rate limit exceeded
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.