> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usequotable.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage endpoints

> Add webhook endpoints, choose events and brands, rotate signing secrets, pause, resume and redeliver from Settings → Webhooks.

You manage webhook endpoints in **Settings → Webhooks**.

| Role | View endpoints and delivery logs | Add, rotate, pause, resume, remove, redeliver |
| - | - | - |
| Owner | Yes | Yes |
| Integration admin | Yes | Yes, for the brands they can access |
| Other members | Yes | No |

Changing an endpoint is a sensitive action. If your sign-in isn't recent, Quotable asks you to sign in again, or for a fresh code from your authenticator app. Every change is recorded in the workspace audit log. See [Team and roles](https://docs.usequotable.com/workspace/team-and-roles.md).

## Add an endpoint

**1. Open the form**

Go to **Settings → Webhooks** and select **Add endpoint**.

**2. Enter the URL**

The URL must start with `https://`, be reachable from the public internet, and contain no username or password. For example: `https://example.com/hooks/quotable`.

**3. Describe it (optional)**

A short description, up to 120 characters, such as `Slack bridge`. It helps teammates know what the endpoint is for.

**4. Pick events**

**Tracking run finalized** is the event you can subscribe to, and it's checked by default. See [Events](https://docs.usequotable.com/webhooks/events.md).

**5. Pick brands**

Leave **All brands, including ones added later** checked, or choose specific brands. The endpoint receives events only for the brands you choose.

**6. Copy the signing secret**

Select **Add endpoint**. Quotable shows the signing secret, which starts with `whsec_`, **once**. Copy it into your receiver's configuration, for example as `QUOTABLE_WEBHOOK_SECRET`. After you close the dialog, only its first characters are shown.

> [!NOTE]
>
> Integration admins can only choose brands they have access to. For them the box reads **Every brand you can access now**: the endpoint covers the brands that admin can access when it's created; brands added later aren't included. Only the owner can create an endpoint that covers future brands.

A workspace can have up to **10 endpoints**. To change an endpoint's URL, events or brands, add a new endpoint with the new settings, then remove the old one.

## Read the delivery log

Select **Show deliveries** under an endpoint to see its 50 most recent deliveries, newest first. Each row shows:

| Column | Meaning |
| - | - |
| Event type | For example `tracking.run.finalized` |
| Status | `pending` (waiting for its first attempt or a retry), `delivered` or `dead` (all 7 attempts failed) |
| Attempts | How many attempts were made |
| Status code | The HTTP status your endpoint returned on the last attempt |
| Next attempt | For pending deliveries, when the next attempt is due |
| Delivered at | When your endpoint accepted it |
| Last error | The last failure: a status code with the start of your response, `redirect not followed`, a timeout or a connection error |

The endpoint itself shows when it last received a delivery, its secret prefix, and, if it was disabled, why.

## Redeliver an event

Select **Redeliver** on any delivery that isn't pending, whether it's dead or was already delivered. It goes back on the queue with a fresh retry schedule, and its earlier attempts stay in the log. The event `id` and `X-Quotable-Delivery-Id` don't change, so your deduplication still recognizes it.

> [!TIP]
>
> After an outage on your side, first fix and **Resume** the endpoint if it was disabled, then redeliver the dead deliveries.

## Rotate the signing secret

Rotate the secret on a schedule, or immediately if it may have leaked.

**1. Rotate**

Select **Rotate secret** on the endpoint. Quotable shows the new secret once. Copy it.

**2. Deploy the new secret**

For the next **24 hours**, every delivery is signed with both the new and the previous secret, and the endpoint shows a **Rotating** badge. Deploy the new secret to your receiver at any point in that window. A verifier that accepts any matching `v1=` signature works with either secret.

**3. Done**

After 24 hours, only the new secret signs deliveries.

> [!WARNING]
>
> If the secret leaked, rotate and deploy the new secret to your receiver right away, without waiting for the 24-hour window to end. Once your receiver verifies only with the new secret, requests forged with the old one fail, while genuine deliveries keep passing because they also carry a signature made with the new secret.

## Pause and resume

Select **Pause** to stop sending without losing events. New events keep queuing for a paused endpoint. Select **Resume** to send everything that queued up.

**Resume** also re-enables an endpoint that Quotable disabled after 50 failed attempts in a row, and resets its failure count. See [Delivery and retries](https://docs.usequotable.com/webhooks/delivery-and-retries.md#automatic-disabling).

## Remove an endpoint

Select **Remove** to delete the endpoint. It stops receiving events immediately, and its delivery log is deleted with it. This can't be undone.

## Status badges

| Badge | Meaning |
| - | - |
| **Paused** | Someone paused it. Events queue until it's resumed. |
| **Disabled** | Quotable disabled it after 50 failed attempts in a row. New events aren't queued. |
| **Rotating** | A secret rotation is in its 24-hour window: deliveries carry two signatures. |
| **Creator left** | The person who created it is no longer in the workspace. Its deliveries stop. Add a replacement endpoint and remove this one. |

## Next steps

> [card] [Verify signatures](https://docs.usequotable.com/webhooks/verify-signatures.md)
>
> Accept both signatures during a rotation.

> [card] [Delivery and retries](https://docs.usequotable.com/webhooks/delivery-and-retries.md)
>
> Retry schedule, guarantees and auto-disable.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.