Skip to main content
ReachOwl uses conventional HTTP status codes to indicate the success or failure of every API request. Understanding these codes helps you build reliable integrations and respond correctly when something goes wrong. All API responses require the Accept: application/json header.

​
Status code reference

​
Common error scenarios

Missing or invalid token If you receive a 401 response, verify that your request includes the header:
Validation errors A 422 response means one or more fields failed validation. Check the response body for details about which fields are required or have incorrect values. For example, creating a campaign without a required action_type will return 422. Rate limiting If you receive 429, back off and retry with exponential delay. ReachOwl may temporarily throttle high-volume callers to protect platform stability.

​
Retrying failed requests

For 500 errors and occasional 429 responses, implement an exponential backoff retry strategy. Do not retry 400, 401, 403, 404, or 422 responses because the request itself is unlikely to succeed without changes.