Session Errors

Session-level errors are sent through the session.error event.

AUTH_INVALID

Sent when the ticket, token, or authentication information is invalid.

{
  "type": "event",
  "topic": "session.error",
  "data": {
    "code": "AUTH_INVALID",
    "message": "Authentication credentials are invalid."
  }
}

AUTH_EXPIRED

The WebSocket session is closed when the access token expires.

If the service sends an error event before closing, it may use:

{
  "type": "event",
  "topic": "session.error",
  "data": {
    "code": "AUTH_EXPIRED",
    "message": "Authentication token has expired."
  }
}

RATE_LIMITED

Sent when heartbeat, reconnection, or request frequency is too high.

{
  "type": "event",
  "topic": "session.error",
  "data": {
    "code": "RATE_LIMITED",
    "message": "Rate limit was exceeded."
  }
}

Client Handling

• For authentication errors: obtain a new access token or wsTicket, then reconnect
• For rate limit errors: reduce request frequency and retry later
• For network failures: reconnect with exponential backoff
• After repeated reconnect failures: record logs and raise an alert