401Unauthorized (invalid or missing token)403Forbidden (invalid credentials or insufficient access)404Not Found409Conflict (data not ready yet or duplicate state)422Unprocessable Content (the request failed its schema; see Request validation errors)500Server error
Request validation errors
A request whose query, path parameters, headers or body don’t match the endpoint’s schema answers422. The body lists every problem, then echoes what you sent:
onnames the part of the request that failed:query,params,headersorbody.- Each entry in
errorshas apath, with nested fields joined by dots (emails.0.value), and amessage. foundis the input as received.
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.