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

# Call Attached Data

Call Attached Data (CAD) allows you to configure key-value pairs that are attached to calls and passed to downstream integrations and APIs.

CAD fields can be configured in two places:

* **Platform settings** — CAD fields applied across the tenant.
* **Bot configuration** — CAD fields applied only to interactions for the current bot.

<Info>
  All interactions in this tenant will use the CAD fields configured in Platform settings.
</Info>

## Platform-level CAD configuration

`Platform Settings → System & Access → Call Attached Data`

<Frame>
  <img className="block" src="https://mintcdn.com/monobot-0e0ffe36/HyNf3IDpimcyfMha/images/telephony/platform_call_attached_data.png?fit=max&auto=format&n=HyNf3IDpimcyfMha&q=85&s=0a54ee3e3a083162f0a83607c48b33a8" alt="CAD Config" width="2842" height="1346" data-path="images/telephony/platform_call_attached_data.png" />
</Frame>

## Configure CAD for a bot

`Agent Configuration → Integrations → SIP Integration → Call Attached Data`

<Frame>
  <img className="block" src="https://mintcdn.com/monobot-0e0ffe36/HyNf3IDpimcyfMha/images/telephony/cad_bot_integration.png?fit=max&auto=format&n=HyNf3IDpimcyfMha&q=85&s=8d21674d857f437df144accf9e0a9ea8" alt="CAD Config Bot" width="1602" height="1122" data-path="images/telephony/cad_bot_integration.png" />
</Frame>

To configure CAD fields for a specific bot:

1. Open **Bot configuration**.
2. Go to **Integrations**.
3. Open **SIP Integration**.
4. Select the **Call Attached Data** tab.
5. Click **New Field**.
6. Add the **Field Name**.
7. Select or enter the **Value**.
8. Click **Save**.

<Info>
  Only interactions in the current bot will use the CAD fields configured in the bot's SIP Integration settings, together with CAD fields from Platform settings.
</Info>

## Field Name

The **Field Name** is the key that will be sent with the call.

Use clear and consistent names so downstream systems can recognize the data correctly.

Examples:

* `status`
* `summary`
* `csat`
* `int_bot_name`
* `int_bot_voice`
* `int_dynamic_value1`

## Value

The **Value** is the data attached to the field.

You can use available variables from the selector, such as:

* **Interaction** variables
* **Bot** variables
* **Dynamic Value** variables

Examples:

* `Interaction.status`
* `Interaction.Summary`
* `Interaction.CSAT`
* `Bot.name`
* `Bot.voice`
* `Dynamic Value`

## Example

| Field Name      | Value                 |
| --------------- | --------------------- |
| `status`        | `Interaction.status`  |
| `summary`       | `Interaction.Summary` |
| `csat`          | `Interaction.CSAT`    |
| `int_bot_name`  | `Bot.name`            |
| `int_bot_voice` | `Bot.voice`           |

## Read CAD Fields

Call Attached Data (CAD) fields attached to interactions can be retrieved using API endpoints.

Supported response formats:

* JSON
* XML

***

## Read CAD in JSON Format

```http theme={null}
GET https://platform.monobot.ai/api/chatbot/interactions/{interactionId}/cad
```

<Frame>
  <img className="block" src="https://mintcdn.com/monobot-0e0ffe36/HyNf3IDpimcyfMha/images/telephony/json_cad.png?fit=max&auto=format&n=HyNf3IDpimcyfMha&q=85&s=3c80fa6edf2ccebd63a283ac3bf04622" alt="XML Json" width="3052" height="1044" data-path="images/telephony/json_cad.png" />
</Frame>

### Path Parameters

| Parameter     | Type   | Description                    |
| ------------- | ------ | ------------------------------ |
| interactionId | string | Unique interaction identifier. |

### Response Example

```json theme={null}
{
  "status": "finished",
  "summary": "The customer requested to be redirected to an agent.",
  "csat": 5,
  "int_bot_name": "Support Bot",
  "int_latency": 0.96
}
```

***

## Read CAD in XML Format

```http theme={null}
POST https://platform.monobot.ai/api/chatbot/interactions/read-cad-by-interaction-id
```

<Frame>
  <img className="block" src="https://mintcdn.com/monobot-0e0ffe36/HyNf3IDpimcyfMha/images/telephony/xml_cad.png?fit=max&auto=format&n=HyNf3IDpimcyfMha&q=85&s=19010d9776c0d7a5987c551cda029bf4" alt="XML Json" width="3060" height="1134" data-path="images/telephony/xml_cad.png" />
</Frame>

### Body Parameters

| Parameter | Type   | Description                     |
| --------- | ------ | ------------------------------- |
| call\_id  | string | Interaction or call identifier. |
| token     | string | Authentication token.           |

### Request Format

`x-www-form-urlencoded`

### Response Example

```xml theme={null}
<?xml version="1.0"?>
<vxml version="2.0">
    <var name="status" expr="finished" />
    <var name="summary" expr="The customer requested to be redirected to an agent." />
    <var name="csat" expr="5" />
    <var name="int_bot_name" expr="Support Bot" />
</vxml>
```

***

## Notes

* CAD fields are returned based on interaction-level and bot-level CAD configuration.
* Returned fields may vary between interactions depending on configured dynamic variables.
* JSON format is recommended for API integrations and external systems.
* XML format is primarily used for SIP and telephony workflows.
* Empty or undefined CAD fields may be omitted from the response.