Request Successful

The request is malformed or fails path, query, body, or lifecycle validation. Standard errors include response_code, message and api_version. Use the x-request-id response header when reporting a failed request.

Authentication failed, or the user/client doesn't have permission to access the requested resource.

The user doesn't have permission to access the requested resource.

The requested resource couldn't be found.

A request precondition failed. Some operations also return 412 when a related resource is not found, such as an assigned member when updating an inspection. Missing required fields normally return 400. Check the operation and message for the failed precondition.

An unexpected error occurred.