POST /api/v1/broadcasts

Request contract

• Required scope is broadcasts:create. name, source_type, and object source_definition are required.
• Optional fields include template, message, sender_phone_number_id, scheduled_at, live or dry_run delivery_mode, lead_tracking, and client_reference.
• Manual sources require at least one recipient containing cc and whatsapp_no.
• Creation enforces the monthly max_broadcast_campaigns_monthly plan limit and can return PLAN_LIMIT_EXCEEDED with resource, limit, current, and requested.

Queue example

{
  "name": "Reviewed campaign",
  "source_type": "manual",
  "source_definition": { "type": "manual", "recipients": [{ "name": "Amit", "cc": "91", "whatsapp_no": "9999999999" }] },
  "template": { "name": "approved_template", "language": "en_US" },
  "client_reference": "campaign-001"
}

Queue response

{
  "request_id": "broadcastreq_example",
  "account_id": "account_uuid",
  "client_reference": "campaign-001",
  "broadcast_id": "broadcast_uuid",
  "run_id": "run_uuid",
  "status": "queued",
  "total_recipients": 1
}

Queued means internal preparation work exists; it does not mean Meta accepted any recipient message. Retain broadcast_id and poll its status rather than recreating the campaign.

Recover creation failures

• Correct required source, sender, template, scheduling, and lead-tracking data.
• Review plan quota fields before reducing the audience or upgrading.
• Do not assume every broad source_type or scheduling string was fully validated at the route schema boundary; inspect the returned error.
• After an uncertain create outcome, inspect account campaign state before retrying because v1 has no idempotency key.