> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/workspace-settings/webhooks/delete-a-webhook.md).

# Delete a webhook

This article describes how to permanently delete a webhook endpoint in Cerby and stop all event delivery.

As a workspace **Owner**, **Super Admin**, or **Admin**, you can permanently delete a webhook and stop all event delivery to its endpoint.

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super Admins**, and **Admins**
* Supported using the Cerby web app
  {% endhint %}

{% hint style="danger" %}
**WARNING:** Deleting a webhook stops all deliveries immediately and cannot be undone. To pause delivery temporarily, disable the webhook instead.
{% endhint %}

To delete a webhook, you must complete the following steps:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Select **Settings** from the left navigation. The **Workspace Configuration** page is displayed.
3. Select the **Webhooks** left tab.
4. Select the actions menu for the webhook you want to delete. The available actions are displayed.
5. Select **Delete webhook**. A confirmation dialog box is displayed.
6. Click the **Delete webhook** button. The webhook is removed from the list and Cerby stops all deliveries to its endpoint.

Now you are done.

## Related articles

**Feature guides:**

* [Create a webhook](https://help.cerby.com/setup-and-admin/workspace-settings/webhooks/create-a-webhook.md)
* [Disable a webhook](https://help.cerby.com/setup-and-admin/workspace-settings/webhooks/disable-a-webhook.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.cerby.com/setup-and-admin/workspace-settings/webhooks/delete-a-webhook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
