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

# Testing webhooks

> Test your webhook endpoints before going live

## Send a test event

You can test your webhook directly from the Allo dashboard:

<Steps>
  <Step title="Open your webhook settings">
    Go to [Settings > Webhooks](https://web.withallo.com/settings/webhooks) in your Allo dashboard.
  </Step>

  <Step title="Select an event to test">
    Pick any event type from the catalog (e.g., `call.completed`, `sms.received`) and click **Test**.
  </Step>

  <Step title="Check the result">
    Allo sends a synthetic event to your endpoint and shows whether it succeeded, the HTTP status code returned, and the response time.
  </Step>
</Steps>

## Local development

During development, your webhook endpoint is typically not publicly accessible. Use a tunnel service to expose your local server:

<Steps>
  <Step title="Start your local server">
    Run your webhook handler locally (e.g., `http://localhost:3000/webhooks/allo`).
  </Step>

  <Step title="Create a tunnel">
    Use a tool like [ngrok](https://ngrok.com) to expose your local server:

    ```bash theme={null}
    ngrok http 3000
    ```

    This gives you a public HTTPS URL (e.g., `https://abc123.ngrok.io`).
  </Step>

  <Step title="Configure your webhook">
    Go to [Settings > Webhooks](https://web.withallo.com/settings/webhooks) and set your tunnel URL as the endpoint.
  </Step>

  <Step title="Send a test event">
    Use the test feature above to trigger a delivery and verify your handler processes it correctly.
  </Step>
</Steps>

## Monitoring

Check your webhook health from [Settings > Webhooks](https://web.withallo.com/settings/webhooks). You can see delivery statistics including successful, pending, and failed deliveries.

A healthy webhook should have a low failure count relative to successes. If failures are increasing, check [Troubleshooting](/en/v2/api-reference/webhooks/troubleshooting).