Skip to main content
The API uses standard HTTP status codes. Common responses include:
  • 401 Unauthorized (invalid or missing token)
  • 403 Forbidden (invalid credentials or insufficient access)
  • 404 Not Found
  • 409 Conflict (data not ready yet or duplicate state)
  • 422 Unprocessable Content (the request failed its schema; see Request validation errors)
  • 500 Server error
Other errors are returned as JSON with an error message.

Request validation errors

A request whose query, path parameters, headers or body don’t match the endpoint’s schema answers 422. The body lists every problem, then echoes what you sent:
  • on names the part of the request that failed: query, params, headers or body.
  • Each entry in errors has a path, with nested fields joined by dots (emails.0.value), and a message.
  • found is the input as received.
Dates in a request must be ISO 8601 date-times with Z or a UTC offset, such as 2026-11-04T15:30:00Z or 2026-11-04T10:30:00-05:00. Date-only strings (2026-11-04) and epoch numbers answer 422 with Invalid ISO datetime. Responses return dates as ISO 8601 strings in UTC. If a response fails its own schema, the API answers 500 with "on": "response" and the errors list, and no record data. That is a Rollout bug, not a problem with your request; retrying won’t help, so contact us with the request.