> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fynapse.app/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fynapse.app/_mcp/server.

# Setup Webhook Subscription via UI

> Learn how to configure webhook subscriptions on the Webhooks screen.

Webhooks screen allows you to create real-time event notifications, i.e. subscriptions, and browse the list of existing ones .

## List of Webhook Subscriptions

The grid comprises a list of all webhook subscriptions configured in Fynapse. It consists of the following columns:

* **URL Endpoint** - name of the subscription and URL of the endpoint called by the webhook
* **Event** - the event type triggering the delivery
* **Status** - information whether the subscription is active or inactive
  * **Active** - when an event occurs it is sent to the receiving system
  * **Inactive** - calls which occur when a subscription is inactive do not cumulate, i.e. there is no backlog that is sent once a subscription becomes active again
* **Timestamp** - date and time when the webhook subscription was created
* **Actions**
  * **Pause/Resume** - allows you to pause an active subscription or resume an inactive one
  * **Send test** - will send a test delivery for your subscription
  * **Delete** - allows you to delete a subscription

## Details Section

You can drill-down to the details section by clicking on a subscription in the grid.

The details section comprises of:

* Overview tab
* Event Deliveries tab

as well as

* **Pause deliveries/Resume deliveries** button - allows you to pause an active subscription or resume an inactive one
* **Send test** button - will send a test delivery for your subscription

### Overview Tab

Overview tab comprises of a dashboard with metrics about:

**Event deliveries**

* Total number of event deliveries - blue line
* Number of failed event deliveries - red line

**Response time**

* Maximum response time - purple line
* Average response time - blue line
* Minimum response time - green line

which can be filtered in the range from Last 5 min to Last 7 days, or you can setup a custom date range. This is shared between both tabs.

The Overview tab also has a right-hand section which contains:

* Details
  * Name - name of the subscription
  * URL Endpoint - URL of the called endpoint
  * Description - description of the subscription
* Secret - secret assigned to the subscription
  * Rotate secret - allows you to rotate a secret, i.e. create a new secret; please remember that this will require you to update the configuration
* Resources - link do relevant help article

### Event deliveries Tab

Comprises of a grid with a list of event deliveries:

* **Status** -  status of the delivery
  * PENDING - the delivery has been created and is awaiting its first attempt or is scheduled for a retry
  * DELIVERED - the webhook was accepted by the external system (HTTP 2xx). Terminal status.
  * DEAD-LETTER - the delivery failed permanently — a non-retryable HTTP status was returned or all retries were exhausted. Terminal status.
  * CANCELLED - the subscription was deleted or inactive when the delivery was picked up, so no HTTP attempt is made. Terminal status.
* **Event** - the event type triggering the delivery
* **Timestamp** - date and time when the message for the subscription was created

You can drill-down to details of an event delivery by clicking on a delivery in the grid. A panel will open on the right-hand side of the screen with the following information:

Delivery attempt details

* **Status** -  information whether the subscription is active or inactive
  * PENDING - the delivery has been created and is awaiting its first attempt or is scheduled for a retry
  * DELIVERED - the webhook was accepted by the external system (HTTP 2xx). Terminal status.
  * DEAD-LETTER - the delivery failed permanently — a non-retryable HTTP status was returned or all retries were exhausted. Terminal status.
  * CANCELLED - the subscription was deleted or inactive when the delivery was picked up, so no HTTP attempt is made. Terminal status.

* **Attempt date** - date of the last delivery attempt

* **ID** - unique ID of the delivery

* **Origin Date** - date and time when the message for the subscription was created

* **Request** - request body

* **Response** - response code, if failed the 4xx body response will be displayed

Resend option - a delivery is re-sent even if it already was sent, it will not appear separately in the Deliveries grid.

**Attempt History**
When more than one delivery attempt is made **Attempt history** will appear below the response listing all delivery attempts.Multiple delivery attempts can occur e.g. when the first attempt failed and the system attempted retires as per the [retry policy](/api-reference/getting-started/webhooks/delivery-retries), or when you click the **Resend** button.
The delivery status in the Deliveries grid will be the status of the last delivery attempt.

## Tutorials

#### How to Add a Webhook Subscription?

1. Go to **Developers > Webhooks.**
2. Click the **+ Add webhook** button.
3. Type a **Name** for the subscription.
4. Paste or type the **URL Endpoint** you want to use.
5. You can add an optional **Description**.
6. Choose the event types you want to trigger a delivery. When you click on the textbox a list of available event types will appear.
7. Click the **Create** button to save your subscription or **Cancel** to discard your changes.
8. A secret for the subscription will appear in the next dialog. Copy it and record in a safe location. Then acknowledge you have safely recorded the secret by checking the box.
9. Click the **Done** button.
   The secret will be later available in the subscription details.
10. The subscription is by default saved as active.

## Watch a Video about the Capabilities of the Webhooks Screen