# Create a webhook

**Summary:** Subrite sets up webhooks for you. Email dev@subrite.no with the webhook name, endpoint URL, authentication, request method and the events to subscribe to.

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

Currently, Subrite does not support creating or updating webhooks through the user interface. To create a webhook and subscribe to a webhook event, contact [dev@subrite.no](mailto:dev@subrite.no).

<a id="required-information"></a>
## Required information

When requesting Subrite to create a webhook, you need to provide the following details:

1. **Webhook name:** An identifiable name for your webhook.
2. **Description (optional):** A brief description of the webhook's purpose.
3. **Endpoint URL:** The URL where the webhook payload will be sent.
4. **Authentication method (optional):** The method used for authentication. Currently, only "bearer" is supported.
5. **Bearer token (conditionally required):** The token used for authentication if the "bearer" method is selected.
6. **Request method:** The HTTP method to be used. Options are:
   - `POST`
   - `GET`
   - `DELETE`
7. **Events:** The events the webhook will subscribe to. Currently, these events are available:
   - `member.deleted`
   - `member.updated`
   - `subscription.created`
   - `subscription.renewed`
   - `member.subscription.activated`
   - `member.subscription.deactivated`

<a id="sample-information"></a>
## Sample information

Here is an example of the information you might send to Subrite:

```text
Webhook Name: Member deletion
Description: Webhook to notify when a member is deleted in subrite
Endpoint URL: https://yourapp.com/webhooks/member-deleted
Authentication Method: Bearer
Bearer Token: your-secure-bearer-token
Request Method: POST
Events: [member.deleted]
```

<a id="webhook-in-the-subrite-ui"></a>
## Webhook in the Subrite UI

Here is an example of the UI after the webhook has been created:

![Webhook tab for a webhook named Subrite Webshop, showing the name, endpoint URL, POST request method, bearer token authentication, a masked token and a masked secret](https://cdn.sanity.io/images/1x2xswq6/production/cb932a4e44e8a651fd63ac56ab09ba9299c2d9cd-807x701.png?w=1600&fit=max&auto=format)

*The Webhook tab shows the endpoint, request method, authentication and secret.*

![Events tab for the same webhook, with the Member Deleted event selected](https://cdn.sanity.io/images/1x2xswq6/production/dac5cd004e151a3a6c320e4af4237c5a088a9c33-806x254.png?w=1600&fit=max&auto=format)

*The Events tab shows the events the webhook subscribes to.*

> [!NOTE]
> You need to collect the secret from Subrite to [verify the webhook signature](https://www.subrite.no/developers/webhook-signature-verification?md=true).