# Webhooks

**Summary:** Webhooks let your integration react to activity in Subrite. When a subscribed event happens, Subrite sends an HTTP request to the URL you configured.

- Role: [Developers](https://www.subrite.no/developers)
- Source: https://www.subrite.no/developers/webhooks
- Updated: 2026-09-23
- Markdown index: https://www.subrite.no/developers/llms.txt

Webhooks allow you to create integrations that react to specific activities in Subrite. When such an activity occurs, Subrite sends an HTTP request to the webhook's configured URL.

For example, you can set up a webhook to send a request when a user is deleted in Subrite.

## Pages in this section

- [Create a webhook](https://www.subrite.no/developers/create-webhook?md=true): Create, edit and delete webhooks yourself in the Subrite admin, under Account settings → Webhooks. Choose the endpoint URL, authentication, request method and the events to subscribe to.
- [Edit a webhook](https://www.subrite.no/developers/edit-a-webhook?md=true): Open a webhook to change its settings, events and status, view its delivery logs, regenerate the signing secret or delete it.
- [Sample webhook request](https://www.subrite.no/developers/sample-webhook-request?md=true): Sample request headers and payloads for every Subrite webhook event, and how Subrite retries requests that do not get a 2xx response.
- [Webhook signature verification](https://www.subrite.no/developers/webhook-signature-verification?md=true): Verify that a webhook request comes from Subrite by computing an HMAC SHA256 of the timestamp and payload with your webhook secret. Includes a NestJS example.