> 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-events/webhook-configuration.md). # Webhook Configuration {% hint style="danger" %} A total of 5 webhooks can be configured under a customer account at a given point in time. {% endhint %} To configure your webhooks, simply follow these steps: 1. **Access Webhook :** Click on Manage Webhooks under Verified Campaigns 2. **Create a New Webhook**: Click on the "Create webhook" button to begin adding a new webhook. 3. **Enter Webhook Details**: * **Webhook Name**: Provide a descriptive name for your webhook in the designated field. This name will be used to identify the webhook within the Truecaller for Business console. Please ensure the name is unique at any given time and does not exceed 50 characters. * **Webhook URL**: Enter the endpoint to which Truecaller should send the webhook notifications. For enhanced security, you might consider including a self-generated key as part of your URL (e.g., `https://server.yourcompany.com/tcbiz-webhook?key=`). 4. **Select Event Type**: Choose the specific type of webhook event you wish to receive notifications for. Currently, webhooks are available for Verified Campaigns-Detailed Whenever a response occurs for these enabled features, we will capture it as an event and send it to your configured URL. *You can review event logs for your webhooks on both the "Manage Webhooks" page and the dedicated "Webhook events" page. Detailed information for each event is available on its respective event details page, with logs retained for the last 30 days.* 5. **Finalize Creation**: Once all the required details are filled, click "Create." Your webhook will now be successfully set up. 6. **Test Your Webhook** : After creation, you can test your webhook to ensure it's functioning correctly. * Click on "Test Webhook" next to an existing webhook. * Select the event you wish to test (Detailed Events or Click Events). * Click "Test URL" to send a test notification.
{% hint style="info" %} Webhook should respond with status code **2XX** and content type should be **application/json** along with **json body** {% endhint %} --- # 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-events/webhook-configuration.md?ask=&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.