Skip to content

Errors Reference ​

Control errors use this shape:

json
{
  "type": "response",
  "id": "request-id",
  "ok": false,
  "error": {
    "code": "BAD_REQUEST",
    "message": "sessionId is required"
  }
}

Common Codes ​

CodeMeaning
BAD_MESSAGEWebSocket message envelope was invalid.
BAD_REQUESTCommand or HTTP body failed validation.
NOT_FOUNDCall, session, endpoint, route, or recording was not found.
CONFLICTThe requested state transition is invalid.
SERVICE_UNAVAILABLERequired backend such as rtpbridge is not configured or unavailable.
SHUTTING_DOWNGateway is draining and cannot admit new work. HTTP command responses use 503 with Retry-After: 1.
INTERNAL_ERRORUnexpected server error.

HTTP routes return JSON error bodies for command failures:

json
{ "error": "sessionId is required" }

Streaming recording routes may return backend status codes when proxied rtpbridge requests fail.

Released by Zyno Consulting.