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

# Preview Campaign Add

> See what adding recipients to a campaign would do. Nothing is stored

Check a CSV or a JSON list against an existing campaign before you [add it](https://docs.60db.ai/api-reference/agents/add-campaign-recipients.md). Nothing is stored and no call is placed.

## Request

The same headers (without `Idempotency-Key`), path and body as [Add campaign recipients](https://docs.60db.ai/api-reference/agents/add-campaign-recipients.md): exactly one of `csv_text` or `recipients`.

## Response

**200 OK**

```json theme={null}
{
  "success": true,
  "data": {
    "added": 2,
    "already_in_campaign": 1,
    "dnc": 1,
    "invalid_count": 1,
    "invalid": [{ "row": 5, "value": "n/a", "reason": "invalid_number" }],
    "duplicates": 0,
    "reopens": false
  }
}
```

The fields mean the same as in [Add campaign recipients](https://docs.60db.ai/api-reference/agents/add-campaign-recipients.md), plus:

| Field | Meaning |
| - | - |
| `reopens` | `true` when the campaign is completed and adding these people would restart it, because at least one number is new |

## Errors

The same as [Add campaign recipients](https://docs.60db.ai/api-reference/agents/add-campaign-recipients.md), except `IDEMPOTENCY_CONFLICT`. The limit is 30 checks a minute.

## Example

```bash cURL theme={null}
curl -X POST https://api.60db.ai/agents/campaigns/CAMPAIGN_ID/recipients/preview \
  -H "Authorization: Bearer your-api-key" \
  -H "Content-Type: application/json" \
  -d '{ "recipients": [{ "phone": "+919876543210" }, { "phone": "n/a" }] }'
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.