How it works
Three WebSocket endpoints exist (/ws/agent, /ws/supervisor, /ws/chat), and they’re what
Get2Dial’s own workspace app connects to for live agent state, wallboard, and chat updates.
Each one authenticates with a user session token — the same short-lived token issued when
someone signs in — not a workspace API key. A workspace API key has no signed-in user behind
it to scope the feed to, so it can’t open one of these connections.
When to use it
Use webhooks instead for any integration that needs to react to call, campaign, or lead events in your own system. Webhooks are the supported, API-key-independent way to receive events, and they cover call lifecycle events (call. originated, call.answered, call.bridged, call.hangup, and more) — see the event
catalog.
What it affects
There’s no supported way to stream these WebSocket feeds into your own application. Building
against them would mean depending on a user session token, which is short-lived and tied to
a specific signed-in person, not a stable integration credential.