Skip to main content

​
HTTP

StatusTypical meaning
400Invalid or missing parameters
401 / 403Authentication or authorization failed
404Unknown resource or route
422Semantically invalid body or state
429Rate limited
500Unexpected server error
Response bodies should follow the schema your OpenAPI components.schemas define (for example a { "error": { "code", "message" } } envelope). Align client parsing with that contract.

​
WebSocket

Application-level errors may arrive as dedicated ServerMessage error frames. Treat disconnects as recoverable: reconnect, resubscribe, and use sequence numbers if your integration logic requires ordering guarantees.