Skip to main content

Subscribing to server events

At Dyte, we run a webhook service for you to be able to subscribe to server events. These webhook events enable you to take certain server actions based on Dyte meeting events and state changes.

Setting a webhook#

There are 2 ways to manage Dyte webhooks for your organization - using APIs and using our dev portal.

Using webhook APIs#

You can make simple REST API calls to add, remove or edit a webhook for your organization. Please refer to webhooks section under API reference to get more details on these APIs.

Using Dyte dev portal#

On the dev portal, you can navigate to the webhook section and click on the "Create a new webhook" card.

On clicking this, you will get to the interface that helps you add a webhook for your organization. You can fill in the details and click the "Create" button to save and create the webhook.

Once created, you can view the webhook details by clicking on the relevant card. You can also click the "Edit" button on the details screen to edit an existing webhook.


Each webhook request is an HTTPS POST request to the URL provided by you, where the details about the event are sent in the message body in JSON format and we expect an HTTP status of 200 OK in response.

Supported events#

We currently support notifications for the following event via webhooks.

  • meeting.started
  • meeting.ended
  • meeting.participantJoined
  • meeting.participantLeft
  • recording.statusUpdate


In order to simplify the webhook structure, we start by defining some types / interfaces / entities which are typically used in the webhook requests. These will later be used as references to explain the webhook request bodies.

Meeting Interface#

interface Meeting {  organizedBy: {    id: string;    name: string;  };  id: string;  title: string;  roomName: string;  status: string;  createdAt: string;}

Participant Interface#

interface Participant {  userDisplayName: string;  peerId: string;  clientSpecificId: string;}

Recording Interface#

interface Recording {  recordingId: string;  status: "INVOKED" | "RECORDING" | "UPLOADING" | "UPLOADED" | "ERRORED";  startedTime: string;  stoppedTime: string;  downloadUrl?: string;  downloadUrlExpiry?: string;  errMessage?: string;  invokedTime: string;  filesize?: double;}

Verifying a webhook call using signature#

Each webhook request is signed using Dyte's private key, and the same can be verified at your end by following the below steps.

  1. Get Dyte's public key: This can be done by making a GET request to this URL -

    curl -X GET ""
  2. Check for the signature header: Each incoming request should have a custom dyte-signature header. This is the signature value that you would be verifying in the next step.

  3. Verify the signature: The signature value is based on RSA-SHA256 digest of the payload. You can calculate the same at your end, and if the value matches the one supplied in the header as described by previous step, you should consider the webhook to be originating from the correct server. For example, you can do the following:

    const signature = req.headers["dyte-signature"];const payload = req.body;
    const isVerified = crypto.verify(  "RSA-SHA256",  Buffer.from(JSON.stringify(payload)),  dytePublicKey,  Buffer.from(signature, "base64"));
JSON Stringification

Few languages like Python, and maybe if you are using a specific library for JSON processing, your JSON.stringify results may not be consistent. Please make sure that there are no such quirks as spaces in between the stringified JSON before trying to verify the webhook signature.

Event details and descriptions#

In the following sections, we describe each event and the kind of data that is sent along with the webhook.


This event is fired when the first participant joins a meeting.

Structure of webhook body#

interface MeetingCreated {  event: "meeting.started";  meeting: Meeting;}

Sample webhook body#

{  "event": "meeting.started",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  }}


This event is fired 1 minute after all the participants leave the meeting or host end the meeting. We add a minute delay to make sure we don't end a meeting due to disconnects.

Structure of webhook body#

interface MeetingEnded {  event: "meeting.ended";  meeting: Meeting;  reason: "ALL_PARTICIPANTS_LEFT" |  "HOST_ENDED_MEETING"}

Sample webhook body#

{  "event": "meeting.ended",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  },  "reason": "HOST_ENDED_MEETING"}


This event is fired whenever a participant joins a meeting.

Structure of webhook body#

interface MeetingParticipantJoined {  event: "meeting.participantJoined";  meeting: Meeting;  participant: Participant;}

Sample webhook body#

{  "event": "meeting.participantJoined",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  },  "participant": {    "userDisplayName": "Rohan",    "peerId": "7eef23c6-1985-492b-9b95-99bac37b60d7",    "clientSpecificId": "a6b2ac87-6f45-46d9-b48a-7e9ccdfd7517"  }}


This event is fired whenever a participant leaves a meeting. This event is also fired when a participant gets disconnected.

Structure of webhook body#

interface MeetingParticipantLeft {  event: "meeting.participantLeft";  meeting: Meeting;  participant: Participant;}

Sample webhook body#

{  "event": "meeting.participantLeft",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  },  "participant": {    "userDisplayName": "Rohan",    "peerId": "7eef23c6-1985-492b-9b95-99bac37b60d7",    "clientSpecificId": "a6b2ac87-6f45-46d9-b48a-7e9ccdfd7517"  }}


This event is fired whenever there is a status update for a meeting recording. There are five such statuses for now:

  • INVOKED: The recording function has been invoked and will start recording the meeting very shortly.
  • RECORDING: The meeting is currently being recorded.
  • UPLOADING: The recording has been stopped and the file is being uploaded to cloud storage. The storage would be Dyte's if no storage parameters are passed in the recording API call.
  • UPLOADED: The recording file upload is complete.
  • ERRORED: There was an error while recording the meeting and the file wouldn't be available.

Structure of webhook body#

interface RecordingStatusUpdate {  event: "recording.statusUpdate";  meeting: Meeting;  recording: Recording;}

Sample webhook body#

Recording status = INVOKED#
{  "event": "recording.statusUpdate",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  },  "recording": {    "recordingId": "7a789a2d-1142-4be3-a208-4d25a75663e7",    "status": "INVOKED",    "invokedTime": "2021-02-01T10:08:21.917Z"  }}
Recording status = RECORDING#
{  "event": "recording.statusUpdate",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  },  "recording": {    "recordingId": "7a789a2d-1142-4be3-a208-4d25a75663e7",    "status": "RECORDING",    "invokedTime": "2021-02-01T10:08:21.917Z",    "startedTime": "2021-02-01T10:08:22.917Z"  }}
Recording status = UPLOADING#
{  "event": "recording.statusUpdate",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  },  "recording": {    "recordingId": "7a789a2e-1141-4bd3-a908-4d30a75773e7",    "status": "UPLOADING",    "invokedTime": "2021-02-01T10:08:21.917Z",    "startedTime": "2021-02-01T10:08:21.917Z",    "stoppedTime": "2021-02-01T10:08:21.917Z",    "filesize": 123.45  }}
Recording status = UPLOADED#
{  "event": "recording.statusUpdate",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  },  "recording": {    "recordingId": "7a789a2e-1141-4bd3-a908-4d30a75773e7",    "status": "UPLOADED",    "invokedTime": "2021-02-01T10:08:21.917Z",    "startedTime": "2021-02-01T10:08:21.917Z",    "stoppedTime": "2021-02-01T10:08:21.917Z",    "downloadUrl": "",    "downloadUrlExpiry": "2021-02-14T10:08:21.917Z",    "filesize": 123.45  }}
Recording status = ERRORED#
{  "event": "recording.statusUpdate",  "meeting": {    "id": "cae39473-ef23-4ca2-a9e9-98f1509354f2",    "title": null,    "roomName": "testing-room",    "status": "LIVE",    "createdAt": "2021-02-09T10:07:11.675Z",    "organizedBy": {      "id": "4fd15a19-80e2-4305-bf13-49039f32963f",      "name": "myOrganization"    }  },  "recording": {    "recordingId": "7a789a2e-1141-4bd3-a908-4d30a75773e7",    "invokedTime": "2021-02-01T10:08:21.917Z",    "stoppedTime": "2021-02-01T10:08:21.917Z",    "status": "ERRORED",    "errMessage": "Description of the error."  }}