# 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](https://docs.digitalsamba.com/reference/rest-api/webhooks/payload-structure) which you will receive at the preconfigured URL.

#### Currently the available events are:

* participant\_joined
* participant\_left
* participant\_invited
* session\_started
* session\_ended
* recording\_started
* recording\_stopped
* recording\_ready
* 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
* phone\_participant\_asked\_to\_unmute
* question\_asked
* question\_answered
* room\_locked
* room\_unlocked

In the future support for more events will be added.

{% hint style="info" %}
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.
{% endhint %}

{% content-ref url="webhooks/create" %}
[create](https://docs.digitalsamba.com/reference/rest-api/webhooks/create)
{% endcontent-ref %}

{% content-ref url="webhooks/edit" %}
[edit](https://docs.digitalsamba.com/reference/rest-api/webhooks/edit)
{% endcontent-ref %}

{% content-ref url="webhooks/list" %}
[list](https://docs.digitalsamba.com/reference/rest-api/webhooks/list)
{% endcontent-ref %}

{% content-ref url="webhooks/delete" %}
[delete](https://docs.digitalsamba.com/reference/rest-api/webhooks/delete)
{% endcontent-ref %}