Errors

Handle errors by HTTP status first, then inspect the operation's documented response body. Common classes are authentication failures, authorization failures, validation failures, missing resources, conflicts, throttling, and server failures.

Do not assume an error code, details object, or retry behavior unless the current operation schema documents it. For a retryable request, use bounded backoff and avoid repeating non-idempotent work without confirming the result.

When reporting a failure, include environment, route family, status, request correlation information if returned, and a redacted response body. See Support.