Create a webhook

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.

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

Webhook name: An identifiable name for your webhook.
Description (optional): A brief description of the webhook's purpose.
Endpoint URL: The URL where the webhook payload will be sent.
Authentication method (optional): The method used for authentication. Currently, only "bearer" is supported.
Bearer token (conditionally required): The token used for authentication if the "bearer" method is selected.
Request method: The HTTP method to be used. Options are:
- POST
- GET
- DELETE
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

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]

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 — The Webhook tab shows the endpoint, request method, authentication and secret.

Events tab for the same webhook, with the Member Deleted event selected — The Events tab shows the events the webhook subscribes to.

Create a webhook

Required information

Sample information

Webhook in the Subrite UI