---
title: "Send broadcast"
method: POST
path: "/v1/broadcasts/{broadcastId}/send"
---

# Send broadcast

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

Start sending the broadcast immediately or schedule for later.

**Verification is required to send, except on WhatsApp.** On every channel other than `whatsapp`, the team must have completed both identity verification (KYC) and business verification (KYB); passing one is not enough. A `whatsapp` broadcast requires neither: it can only be built on a template, and Meta vets the business and the content when it approves that template, so an unapproved template is refused instead. `smart` is not exempt — it can route a contact to SMS or email. Drafts can be created, edited and kept without any check. Every send path — dashboard, API and CLI alike — enforces the same rule, returning `403` with code `kyc_required` or `kyb_required` for whichever is outstanding.

**Review depends on the channel, and cannot be bypassed.** A draft is submitted to automated content review here; it does not go straight out. A WhatsApp broadcast built on a Meta-approved template skips review (Meta already vetted the content) and begins sending. An email broadcast sends as soon as the automated review passes. Every other channel moves to `pending_admin_review` and waits for a person. If the review rejects it, use PATCH to edit the content then call POST /retry-review.

Calling this on a broadcast that is already `approved` or `scheduled` sends or reschedules it directly, since it has already been reviewed. Reserves the estimated cost from your balance.

## Path parameters

- `broadcastId` string, required

## Request body

- BroadcastSendRequest
  - `scheduledAt` string, date-time — Schedule for future delivery. Omit to send immediately.

## Response `202`

Broadcast started or scheduled.

- BroadcastResponse
  - `broadcast` Broadcast, required
    - `id` string, required
    - `name` string, required
    - `status` 'draft' | 'pending_review' | 'approved' | 'rejected' | 'escalated' | 'rejected_final' | 'scheduled' | 'sending' | 'paused' | 'completed' | 'cancelled' | 'failed', required — Current status of the broadcast.
    - `channel` 'smart' | 'sms' | 'sms_oneway' | 'whatsapp' | 'telegram' | 'email', required — Broadcast delivery channel. Use 'smart' for per-contact intelligent routing.
    - `messageType` 'text' | 'image' | 'video' | 'audio' | 'document' | 'template', required — Type of message for broadcast.
    - `text` string
    - `content` BroadcastContent — Content for non-text broadcast message types.
      - `mediaUrl` string — URL of the media file.
      - `mediaId` string — Media ID if already uploaded.
      - `mimeType` string — MIME type of the media.
      - `filename` string — Filename for documents.
      - `templateId` string — Template ID for template messages.
      - `templateVariables` object — Default body variables (can be overridden per contact). 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 — Default button variables for dynamic URL/OTP buttons. Keys are the button index (0, 1, 2). Per-contact values override these.
      - `templateHeaderVariables` object — Default value for a text-header variable, keyed by `1` (can be overridden per contact). If omitted, Zavu resolves the header from `templateVariables` by the header placeholder's name.
    - `senderId` string
    - `emailSubject` string
    - `totalContacts` integer, required — Total number of contacts in the broadcast.
    - `pendingCount` integer
    - `sendingCount` integer
    - `deliveredCount` integer
    - `failedCount` integer
    - `estimatedCost` number, nullable — Estimated total cost in USD.
    - `reservedAmount` number, nullable — Amount reserved from balance in USD.
    - `actualCost` number, nullable — Actual cost so far in USD.
    - `scheduledAt` string, date-time
    - `startedAt` string, date-time
    - `completedAt` string, date-time
    - `metadata` object
    - `createdAt` string, date-time, required
    - `updatedAt` string, date-time
    - `reviewResult` object, nullable — AI content review result.
      - `score` number — Content safety score from 0.0 to 1.0, where 1.0 is completely safe.
      - `categories` string[] — Policy categories violated, if any.
      - `reasoning` string — Explanation of the review decision.
      - `reviewedAt` string, date-time
      - `flaggedContent` string[], nullable — Problematic text fragments, if any.
    - `reviewAttempts` integer, nullable — Number of review attempts (max 3).

## Other responses

- `400` — Invalid request, no contacts, or broadcast not in valid status. A WhatsApp broadcast whose template Meta has not approved yet is refused here with code `template_not_approved`. Because a WhatsApp broadcast needs no KYC/KYB, this is the only review it passes through — retry once the template is approved.
- `401` — Unauthorized.
- `402` — Insufficient balance.
- `403` — Verification required; the code says which one is missing. Both identity (KYC) and business (KYB) verification are needed on every channel except `whatsapp`, which requires neither — so neither code is ever returned for a WhatsApp broadcast. Drafts are unaffected.
- `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/4dacdff2adf8/schema)