Skip to main content

Errors and Response Handling

Error responses are not fully standardized across the current Web API, so clients should be prepared to handle both structured JSON and plain-text error responses.

Status Codes Seen In Existing Docs​

These are the response codes already mentioned in the existing documentation and endpoint descriptions:

  • 200: Success
  • 400: Invalid request body or invalid input
  • 401: Unauthorized
  • 419: Session expired
  • 500: Internal server error

Client Recommendations​

  • Treat non-2xx responses as failures even if the body is a plain string.
  • Log the request path, HTTP method, status code, and response body for supportability.
  • Store the string-to-sign and headers used for failed requests while you are validating auth.
  • Wrap long-poll, upload, and media workflows with retries and timeout handling.