> For the complete documentation index, see [llms.txt](https://docs.truecaller.com/truecaller-for-business/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truecaller.com/truecaller-for-business/truecaller-for-business/verified-campaigns/api-webhook-documentation/webhook-connectors/webhook-setup.md).

# Webhook Setup

{% hint style="info" %}
**Note:** Your external system's configuration will vary depending on the platform. Refer to your system's documentation for specific instructions on how to set up webhook integration.
{% endhint %}

Copy the following within Truecaller for Business console's webhook setup page.

1.  **Webhook Endpoint URL:**
   * This is the address (URL) where you will push your segment and template parameters to. 
     * [`https://enterprise-webhooks-noneu.truecaller.com/v2/campaigns`](https://enterprise-webhooks-noneu.truecaller.com/v2/campaigns)
   * **Action:** Copy this URL and paste it into the webhook configuration section of your external CX system.
2. **Organization ID:**
   * This is a unique identifier assigned to your organization within the Truecaller for Business system. It's a 16 digit UUID.
   * **Action:** Copy this ID. You'll need to include it in the authentication headers of your webhook requests to verify that you're authorized to receive the notifications.
   * **Key-Value Pair Format** : `X-Org-ID: [Your Organization ID]`
3. **Webhook Token:**
   * This token is used for authenticating your webhook requests to ensure secure communication between your system and Truecaller's backend service.
   * **Action:** Copy the webhook token and include it in the headers of your requests as an additional security measure.
   * **Key-Value Pair Format**: `X-Org-Token: [Your Webhook Token]`

<figure><img src="https://524139107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnvD14ounFJ30uTgr4F8f%2Fuploads%2FZznB7DyMKLxwg1l1B1MJ%2FScreenshot%202024-08-12%20at%204.43.48%E2%80%AFPM.png?alt=media&amp;token=0ecdc151-4fd2-447b-8cc8-5ca2a730068a" alt=""><figcaption></figcaption></figure>

{% embed url="<https://youtu.be/7w7eyywi_aQ?si=tjtO75ZCcHIeTAm4>" %}


---

# 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.truecaller.com/truecaller-for-business/truecaller-for-business/verified-campaigns/api-webhook-documentation/webhook-connectors/webhook-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.