event field in the envelope, e.g. webinar.created) and an enum name used when creating subscriptions (e.g. WEBINAR_CREATED). Subscribe using the enum name; match on the wire name in your receiver.
Webinar, registrant and attendee events cover webinars only. Scheduled studio sessions do not emit them — to track those, use Get Events, which returns sessions and webinars alike. Recording and export events cover every recording and export in the account, from studio sessions and webinars alike.
The payloads below show the
data object of the envelope. Test events (fired via sendTestEvent) carry the same shape with an added "test": true marker and obviously synthetic values, so you can build and validate your parser without a real event.Webinar events
webinar.created, webinar.started, and webinar.ended share a common webinar shape. started adds actual_start_time; ended adds actual_end_time and attendee_count.
The webhook payload and Get Events describe the same webinar with different field names:
title → name, scheduled_start_time → start_time, scheduled_end_time → end_time. registration_url is the same link on both surfaces.data (webinar.ended)
Registrant & attendee events
registrant.created, attendee.joined, and registrant.did_not_attend share a common registrant shape. attendee.joined adds joined_at and sets participated: true; registrant.did_not_attend sets participated: false with a zeroed attendance.
data (attendee.joined)
Recording events
recording.ready fires once per recording, when its participant tracks have finished processing and their files can be downloaded. It also waits for the transcript, so the transcript files are usually included. It covers recordings made in the studio and in webinars. The payload is similar to Get Recording at the moment the event fires; the field table below is the contract.
status is always ready on this event, but the all_participants track may still be processing, with no files yet. No later event announces its files, so call Get Recording later to fetch them.data (recording.ready)
Export events
export.completed fires once per export, when it finishes rendering and can be downloaded. The payload is similar to Get Export; the field table below is the contract.
data (export.completed)
Known limitations of recording and export events
- Practice takes never fire
recording.ready. A small share of other recordings never reach the ready state and don’t fire either. - The
all_participantstrack may still beprocessingwhenrecording.readyfires. Fetch it later with Get Recording. - Timeline exports (the
.zipfrom Create Timeline Export) don’t fireexport.completed. Failed exports don’t fire any event. - Events lost inside Riverside (for example, during an internal outage) are never sent and can’t be replayed. Replay only re-sends deliveries Riverside recorded and that were already delivered, failed, or suspended.