> 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/campaign-payload/caller-id.md).

# Caller ID

Display your campaign when users receive calls from your verified number, ensuring high visibility and engagement. This touchpoint allows you to present important messages directly during incoming calls, enhancing user awareness of your brand&#x20;

{% hint style="info" %}
To create the JSON payload structure needed for your webhook connectors, use the DIY Template Generator tool within the Verified Campaigns tab on the Truecaller for Business console. The tool helps you to create the appropriate template in two simple steps.&#x20;
{% endhint %}

**Below are the required payload parameters for each Template Style on the Caller ID screen :**

**profile** section parameters are **Mandatory** for all webhook payloads :

* **campaign\_id** : External campaign reference ID
* **receiver\_number** : Phone numbers of the end user to whom the communication should be delivered.

**content** section parameters can vary based on display\_unit and template\_style selected as follows : *\* means mandatory*

| Template 1 - Text only | Template 2 - Image Banner only | Template 3 - Personalised content with image banner on left | Template 4 - Personalised content with image banner on right |
| ---------------------- | ------------------------------ | ----------------------------------------------------------- | ------------------------------------------------------------ |
| “display\_unit”\*      | “display\_unit”\*              | “display\_unit”\*                                           | “display\_unit”\*                                            |
| "title"\*              | "ttl"                          | "title"\*                                                   | "title"\*                                                    |
| "sub\_title"\*         |                                | "sub\_title"\*                                              | "sub\_title"\*                                               |
| "ttl"                  |                                | "ttl"                                                       | "ttl"                                                        |


---

# 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/campaign-payload/caller-id.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.
