Events and subscriptions
Relay is event-driven. Once your connection is open, SignalWire pushes events to it as things happen — your call changes state, a member joins or leaves the room, the active speaker changes, the layout updates — so you react to them instead of polling. This page covers the events a client receives and how to subscribe to a room’s feed.
The events you receive
Every event reaches you the same way — pushed over the open socket. As a client, they fall into a few groups:
- Call state —
call.statetracks each call leg as it progresses and carries thecall_idandnode_idthat identify the leg.call.joinedandcall.leftmark when you join and leave the call, and also carry yourmember_id. - Member events —
member.joined,member.left,member.updated, andmember.talkingreport who is in the room and what changed for them, including the active speaker. - Room events —
room.updatedandlayout.changedreport changes to the room itself, such as a new video layout. - Verto signaling — if you drive calling through the lower-level WebRTC/Verto path, inbound Verto frames (an incoming call, the far end hanging up, media updates) arrive on the receive-only
webrtc.messagechannel, passed through as-is. Room and member events don’t travel on this channel; they arrive as their own events.
Every event is documented on its own receive-only channel in the API reference under this tab — call.state, member.joined, room.updated, webrtc.message, and the rest.
How you receive events
Call Fabric events are receive-only: SignalWire pushes them to you as your call and room change state, with no separate request to turn them on. Once you place or join a call you receive its call.state changes, and when you join a room, a room.subscribed event delivers the room’s current state and your member and call identifiers.
When your webrtc.verto invite joins a Video Room resource, that room’s events are opt-in instead. Apart from room.subscribed, they reach you only if their event types are named in the subscribe list of that invite; an event you leave out of the list never arrives. The Browser SDK sends this list for you.
What an event looks like
Every event arrives as a JSON-RPC request with the method signalwire.event. Its params is an envelope: event_type names the event, and the inner params holds the payload, whose fields depend on the event. This call.state event is shortened to a few payload fields:
Events are notifications, so you don’t reply to them. The exact envelope and payload for each event live on that event’s page in the API reference. If you use the Browser SDK, you don’t parse this shape by hand — the SDK delivers each event as a typed object or a callback.
Correlate events to your call
Client events carry the identifiers that address your call, so you can tie each one back to the call or member it belongs to:
call_id— the call the event is for.member_id— the specific member (participant) the event is about, on member events and oncall.joinedandcall.left.