Webhooks

Webhooks are a way to integrate your existing backend with different room events. When the event happens, then an HTTP POST request will be made to the URL which you preconfigured. That way you can execute custom logic on your backend side.

Read about the payload structure which you will receive at the preconfigured URL.

Currently the available events are:

• participant_joined

• participant_left

• recording_started

• recording_stopped

• recording_ready

• session_started

• session_ended

• file_added_to_library

• file_renamed

• file_deleted_from_library

• file_processing_failed

• folder_added_to_library

• folder_renamed

• folder_deleted_from_library

• phone_participant_muted

• phone_participant_unmuted

• participant_invited

• question_asked

• question_answered

• room_locked

• room_unlocked

• phone_participant_asked_to_unmute

• participant_avatar_uploaded

• participant_avatar_deleted

• session_summary_ready

• room_deleted

• role_deleted

• recording_deleted

• participant_hand_raised

• participant_hand_lowered

• session_transcript_ready

• question_updated

• question_dismissed

• question_reopened

• question_deleted

• answer_updated

• answer_deleted

• participant_waiting_joined

• participant_waiting_left

In the future support for more events will be added.

An authorization_header secret property can be configured to improve the security of the webhook. The property is a secret known only to you and to DigitalSamba, and it will be included in every webhook POST request as a bearer token. That way you can be sure the webhook request comes from DigitalSamba and not from an unauthorized external entity.

CreateEditListDelete