> 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/test-a-webhook-endpoint.md).

# Test a webhook endpoint

This article describes how to send a verification challenge to a webhook endpoint in Cerby to confirm it is reachable and responding correctly.

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

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

As a workspace **Owner**, **Super Admin**, **Admin**, or **Guest Admin**, you can send a verification challenge to a webhook endpoint to confirm it is reachable and responding correctly. The challenge uses the same signing algorithm and key as live deliveries and works even while the webhook is disabled.

The test sends the `webhook.test` event type, which is not subscribable and never fires from real account or automation activity. Cerby signs and renders it exactly as it does a live delivery, so what the test sends matches what production sends.

To test a webhook endpoint, 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. Click the name of the webhook you want to test. The webhook detail page is displayed.
5. Click the **Test endpoint** button. A panel opens showing the endpoint URL and a description of the verification challenge.
6. Click the **Send test event** button. Cerby sends the verification challenge to the configured endpoint URL, and the panel displays the HTTP status along with the request and response details.

{% hint style="info" %}
**NOTE:** If the panel reports the endpoint as blocked or unreachable, Cerby could not complete a request to it at all. For how to diagnose that result, refer to [Troubleshooting: Webhook deliveries failing](https://help.cerby.com/tips-and-troubleshooting/troubleshooting/webhooks/troubleshooting-webhook-deliveries-failing).
{% endhint %}

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)
* [Rotate a webhook signing key](https://help.cerby.com/setup-and-admin/workspace-settings/webhooks/rotate-a-webhook-signing-key.md)

**Troubleshooting:**

* [Troubleshooting: Webhook deliveries failing](https://help.cerby.com/tips-and-troubleshooting/troubleshooting/webhooks/troubleshooting-webhook-deliveries-failing)


---

# 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/test-a-webhook-endpoint.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.
