> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/onboarding/webhook-events-and-setup.md).

# Webhook Events & Setup

360dialog sends webhooks to two different URLs. Partners need both.

| Webhook                                                                                                                                                                                                                   | What it receives                                                                                                                                                                                                                                                                                                                                                                                        | Where to set it                                                                                                                                                                                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><strong>Partner webhook</strong><br>One per partner account</p>                                                                                                                                                        | Events about your partner account, your clients and their channels: channel lifecycle (created, submitted, ready, live, running), client created, partner change requests, template status changes, account updates such as restrictions and violations, BSP removed or restored. See the [full list of partner webhook events](https://docs.360dialog.com/partner/partner-api/api-reference/webhooks). | Partner Hub > Integration > Partner Webhook URL, or the [Set webhook URL](https://docs.360dialog.com/partner/partner-api/api-reference/webhook-management) endpoint of the Partner API                                                         |
| <p><strong>Number webhook</strong><br>Per phone number, up to 3 with <a href="https://docs.360dialog.com/partner/onboarding/webhook-events-and-setup/set-multiple-webhooks-for-phone-number.md">multiple webhooks</a></p> | Messaging events for that number: incoming messages and message statuses (sent, delivered, read, failed). See the [messaging webhook payloads](https://docs.360dialog.com/partner/onboarding/webhook-events-and-setup/webhook-events-partner-and-messaging-api.md).                                                                                                                                     | The [Set webhook URL for a phone number](https://docs.360dialog.com/partner/messaging/sending-and-receiving-messages/receiving-messages-via-webhook#set-webhook-url-for-phone-number) endpoint of the Messaging API, with the number's API key |

A WABA webhook can act as a fallback. Set without `override_all`, it applies only to the numbers of that WABA that have no number webhook.

{% hint style="warning" %}
Use production URLs for both. Free test services like webhook.site are fine while you build, but replace them before your clients go live. Events delivered to a test URL never reach your system.
{% endhint %}

## Set the number webhook for new client numbers

There is no partner-wide default number webhook. Set it for each new number your clients onboard:

1. Wait for the `channel_running` event on your partner webhook. The number is then ready to send messages.
2. Generate an API key for the channel with the [Partner API](https://docs.360dialog.com/partner/partner-api/api-reference/channel-management). If it returns `409`, the channel is still provisioning. Retry after the `Retry-After` delay.
3. Set the number webhook with that API key.

Direct-Paid partners need the client's permission before they can generate an API key. See [API Keys](https://docs.360dialog.com/partner/partner-hub/api-keys).

## Verify that a webhook comes from 360dialog

Every partner webhook carries an x-360dialog-signature header: the HMAC-SHA256 of the raw request body, keyed with your platform secret (Partner Hub, Integration), in lowercase hex. It is the same signature and the same secret as on messaging webhooks, so the function on the signature validation page verifies both.

The header comes on top of the headers you set for your Partner webhook URL; those still arrive unchanged. Verifying it is optional, but we recommend it, together with HTTPS, so nobody can post fake events to your URL.

Use "Send test webhook event" in the Partner Hub to check your verification before you enforce it. See [Signature Validation](https://docs.360dialog.com/partner/onboarding/webhook-events-and-setup/signature-validation.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://docs.360dialog.com/partner/onboarding/webhook-events-and-setup.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.
