Error Handling and HTTP Status Codes

Updated May 15, 2026 20:47

Runtime API families share common error behavior and HTTP status patterns.

Shared Status Code Guidance

HTTP Code	Shared Meaning in API Docs	Typical Handling Guidance
`200`	Request accepted or success payload. Some endpoint families may also return payload-level errors at `200`.	Inspect response body fields such as `success` and `error_message` where applicable.
`204`	Accepted with no content (common for tracking ingestion).	Treat as success.
`400`	Request reached parser but is invalid.	Correct payload and field usage.
`401`	Missing or invalid auth, or insufficient auth scope.	Verify credential type and header format.
`403`	Auth format accepted by transport but invalid for endpoint contract.	Use endpoint-specific auth format.
`413`	Payload too large.	Reduce payload size.
`414`	URL or request line too large.	Reduce query length and URL size.
`422`	Validation failure on required inputs.	Provide required parameters and fields.
`429`	Rate or plan limit condition.	Retry with backoff.
`500`	Service-side failure.	Check limits and usage, then escalate if persistent.

For some endpoint families, failures can appear in a successful HTTP response (200) with payload flags such as:

When this pattern is used, endpoint docs explicitly call it out.