Stream live events
What’s happening on a call, as it happens, over Server-Sent Events. Every call has it: phone calls (outbound, campaign and inbound), browser calls and realtime sessions.
This response doesn’t finish on its own. It stays open and sends each event as it occurs: agent.state (listening, processing, speaking), transcript.turn for every completed turn, turn.metrics with how fast each agent reply came (latency_ms from the caller stopping to the reply’s audio, and each stage’s first-byte time), tool.started and tool.completed for each tool the agent runs during the call (names and timings, never arguments or results), flow.node.entered and flow.variables.extracted for a node-based agent, language.changed when the call switches language because the caller asked for another one or spoke it (and language.not_enabled when they asked for one the agent does not have), and finally call.ended, after which the stream closes.
Every event has an id. To resume after a drop, send it back as after (or as the Last-Event-ID header) and the stream carries on after that event. Events are kept for an hour after the call ends, so opening a finished call replays it and closes. A reader already past call.ended gets 204.
A phone call’s stream opens when it is placed and stays quiet while it rings; the first event arrives when the call is answered. A call that is never answered (busy, no answer) sends only call.ended, with the call’s status.
Your API key works here, from your backend, for any call in your workspace. A browser should open the events_url that creating the call returned, which carries its own token, so your key never reaches the page. A campaign or inbound call has no create response, so read its stream with your key.
Authorizations
Response
The stream, through to call.ended