---
title: "Add contacts to broadcast"
method: POST
path: "/v1/broadcasts/{broadcastId}/contacts"
---

# Add contacts to broadcast

`POST /v1/broadcasts/{broadcastId}/contacts`

Add contacts to a broadcast in batch. Maximum 1000 contacts per request.

## Path parameters

- `broadcastId` string, required

## Request body

- BroadcastContactsAddRequest
  - `contacts` BroadcastContactInput[], required — List of contacts to add (max 1000 per request).
    - `recipient` string, required — Phone number (E.164) or email address.
    - `templateVariables` object — Per-contact body variables. Key them to match the template body: by position (`1`, `2`, ...) for positional templates, or by name (e.g. `customer_name`) for named templates. Zavu detects the template's format and sends the correct payload to Meta. Do not mix positional and named keys.
    - `templateButtonVariables` object — Per-contact button variables for dynamic URL/OTP buttons. Keys are the button index (0, 1, 2).
    - `templateHeaderVariables` object — Per-contact value for a text-header variable, keyed by `1`. If omitted, Zavu resolves the header from `templateVariables` by the header placeholder's name.

## Response `201`

Contacts added.

- BroadcastContactsAddResponse
  - `added` integer, required — Number of contacts successfully added.
  - `duplicates` integer, required — Number of duplicate contacts skipped.
  - `invalid` integer, required — Number of invalid contacts rejected.
  - `errors` object[] — Details about invalid contacts.
    - `recipient` string
    - `reason` string

## Other responses

- `400` — Invalid request or broadcast not in draft status.
- `401` — Unauthorized.
- `404` — Broadcast not found.

---

[API](https://skmtc.net/zavudev/apis/zavu-unified-messaging-layer-api.md) · [All operations](https://skmtc.net/zavudev/apis/zavu-unified-messaging-layer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zavudev/zavu-unified-messaging-layer-api/revisions/eb3dc75cc05b/schema)