> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get2dial.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Realtime events
> Why the WebSocket feeds that power the Get2Dial workspace aren't a supported integration surface, and what to use instead.
Get2Dial's own agent, supervisor, and chat panels update live over WebSocket connections. This
isn't a supported integration surface for your own application today — here's why, and what
to use instead.
## 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](/developers/webhooks/overview) 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](/developers/webhooks/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.
## Limits and constraints
None of the three feeds are documented in the public API reference, and their message formats
aren't a published contract — they can change without the notice a public API would get.
## Next steps