Webhook payloads are read at any depth
Realtime webhook handling walks the whole payload instead of the top level only, so nested event fields are no longer missed.
What's new across WAVE, at the platform, workstream, and product level. Shipping in the open.
Filtered by tag realtime · clear
Realtime webhook handling walks the whole payload instead of the top level only, so nested event fields are no longer missed.
Recordings from Asia-Pacific and South America now route to in-region storage automatically, based on where the session happens.
Clients now receive real-time state updates instead of polling, and can exchange data directly through the room. This completes the live client layer for rooms.
Publish from the browser over WHIP and play back low-latency streams over WHEP, no plugins required.
Browser publish requests were being blocked by the realtime edge and rejected for a malformed offer. Both issues are fixed and publishing now succeeds end to end.
Run a live voice agent in a room that listens, responds, and stops speaking the moment a caller interrupts.
A join request sent without a media offer was returning an error from the realtime service. The client now omits the request body when there is no offer, and joins succeed.
Joining, publishing, subscribing, renegotiating, and leaving a real-time room now works through one authenticated path from app to media edge.
The realtime service now answers on its own domain, with health checks public and the join endpoint gated behind authentication.
Callers can now join a real-time session and fetch connection credentials through one authenticated or pay-per-use endpoint. Nothing reaches the media edge directly.
A single request creates or opens a meeting and returns a join token and app ID. Client SDKs use the token to join instantly.
Dated, versioned changes to the API and SDKs live at changelog.wave.online.