WhatsApp Business API

All WhatsApp messages go through one endpoint, POST /whatsapp/message/sendbulk, where messageType selects the payload. This page shows how to send approved templates and session messages, manage templates, and track delivery per recipient.

Before you send#

• Connect a WhatsApp Business Account. Onboarding uses Meta Embedded Signup. POST /whatsapp/generate-link returns an encrypted signup link (HTTP 201) for your account; the business admin opens it and completes Meta's flow (business account, phone number verification and display name). Our team supports you through Meta's review.
• Have an approved template for any message that starts a conversation or is sent outside the customer service window.
• Hold opt-in from each recipient, as Meta's policies require.

The customer service window#

When a customer messages you, a 24-hour customer service window opens. Inside it you can reply with any message type (text, media, interactive). Outside it, you can only send an approved template. Meta sets these rules and its pricing; check Meta's current documentation and rate card for the categories and markets you send to.

Send a template#

Set messageType=TEMPLATE, name the template and its language, and pass the body variable.

curl -X POST https://api.broadnet.me/whatsapp/message/sendbulk \
  -H "Authorization: Bearer $BROADNET_TOKEN" \
  -F batchId=0 \
  -F campaignName=order-updates \
  -F destinationNo=971500000000 \
  -F messageType=TEMPLATE \
  -F templateName=order_update \
  -F templateLanguage=en_US \
  -F bodyTemplateVariables=INV-400

const form = new FormData();
form.append("batchId", "0");
form.append("campaignName", "order-updates");
form.append("destinationNo", "971500000000");
form.append("messageType", "TEMPLATE");
form.append("templateName", "order_update");
form.append("templateLanguage", "en_US");
form.append("bodyTemplateVariables", "INV-400");

const res = await fetch("https://api.broadnet.me/whatsapp/message/sendbulk", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.BROADNET_TOKEN}` }, // fetch sets the multipart boundary
  body: form,
});
console.log(await res.json());

import os
import requests

fields = {
    "batchId": "0",
    "campaignName": "order-updates",
    "destinationNo": "971500000000",
    "messageType": "TEMPLATE",
    "templateName": "order_update",
    "templateLanguage": "en_US",
    "bodyTemplateVariables": "INV-400",
}
# Send every field as a multipart part (files=) rather than url-encoded (data=).
r = requests.post(
    "https://api.broadnet.me/whatsapp/message/sendbulk",
    headers={"Authorization": f"Bearer {os.environ['BROADNET_TOKEN']}"},
    files={k: (None, v) for k, v in fields.items()},
    timeout=30,
)
print(r.json())

<?php
$ch = curl_init("https://api.broadnet.me/whatsapp/message/sendbulk");
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => ["Authorization: Bearer " . getenv("BROADNET_TOKEN")],
    // An array (not a string) makes cURL send multipart/form-data.
    CURLOPT_POSTFIELDS => [
        "batchId" => "0",
        "campaignName" => "order-updates",
        "destinationNo" => "971500000000",
        "messageType" => "TEMPLATE",
        "templateName" => "order_update",
        "templateLanguage" => "en_US",
        "bodyTemplateVariables" => "INV-400",
    ],
]);
echo curl_exec($ch);
curl_close($ch);

The call queues the messages and returns at once with a batch summary:

{
  "totalFiles": 1,
  "totalSuccess": 1,
  "totalFailed": 0,
  "totalDuplicates": 0,
  "batchId": "2609091405000000001",
  "fileResults": [
    {
      "fileName": "direct",
      "totalRecords": 1,
      "successCount": 1,
      "failedRecipients": [],
      "duplicateRecipients": []
    }
  ],
  "message": "Messages queued for delivery"
}

Store batchId. Per-recipient statuses arrive on your webhook and can be read from the bulk insights endpoint.

Request fields#

Which fields are required depends on messageType. These are the common ones:

For templates with several variables per recipient, upload a personalised destinationFiles file with one row per recipient. Confirm the column layout with our team for your first campaign.

Template variations#

Send session messages#

Inside the service window you can send free-form messages. Two examples:

curl -X POST https://api.broadnet.me/whatsapp/message/sendbulk \
  -H "Authorization: Bearer $BROADNET_TOKEN" \
  -F batchId=0 \
  -F destinationNo=971500000000 \
  -F messageType=TEXT \
  -F campaignName=support \
  -F "content=Your order has shipped. Reply here if you need anything."

curl -X POST https://api.broadnet.me/whatsapp/message/sendbulk \
  -H "Authorization: Bearer $BROADNET_TOKEN" \
  -F batchId=0 \
  -F destinationNo=971500000000 \
  -F messageType=INTERACTIVE \
  -F campaignName=support \
  -F 'interactivePayload={"type":"button","body":{"text":"Confirm your delivery slot?"},"action":{"buttons":[{"type":"reply","reply":{"id":"slot_ok","title":"Confirm"}},{"type":"reply","reply":{"id":"slot_change","title":"Change"}}]}}'

Interactive payloads follow Meta's interactive message format, which also covers lists, CTA URL buttons, location requests, product and catalog messages, and Flows.

Mark a message as read#

POST /whatsapp/message/read marks an inbound message as read. Add "typing": true to show a typing indicator while you prepare the reply.

curl -X POST https://api.broadnet.me/whatsapp/message/read \
  -H "Authorization: Bearer $BROADNET_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "messageId": "wamid.HBgMOTcxNTAwMDAwMDAwFQIAEhgg", "typing": true }'

Track delivery#

Each recipient moves through SUBMITTED, SENT, DELIVERED and READ, or ends as FAILED or REJECTED with a reason. Statuses are pushed to your account's webhook. You can also read them per batch:

curl "https://api.broadnet.me/whatsapp/message/bulk-insights?batch_Id=2609091405000000001&status=FAILED&page=0&size=50" \
  -H "Authorization: Bearer $BROADNET_TOKEN"

Manage batches#

Manage templates#

Templates are created through the API (or the console), reviewed by Meta, and then sent by name.

Main fields for POST /whatsapp/template:

New templates start as PENDING until Meta approves them. If you suspect a missed status update, call the refresh endpoint.

Other WhatsApp features in the API#

The WhatsApp section of the API also covers:

• WhatsApp Flows: create, upload, publish and measure Flows (for example POST /whatsapp/flow/create, POST /whatsapp/flow/{WA_FLOW_ID}/publish, GET /whatsapp/flow/{WA_FLOW_ID}/metrics).
• Catalogs: manage products and product sets on a connected catalog (for example POST /whatsapp/catalog/{WA_CATALOG_ID}/product, POST /whatsapp/catalog/connect) and read GET /whatsapp/message/catalog-insights.
• QR links: create and manage QR codes that open a chat (/whatsapp/qr-links).
• Business profile: read and update the profile (/whatsapp/business-profile) and upload a profile photo (POST /whatsapp/profile-photo).
• Blocked users: list, block and unblock users (/whatsapp/block-users).

The full field reference for each is in the OpenAPI spec, available to customers on request. See SDKs and OpenAPI.

Next steps#

• Webhooks: handle DELIVERED, READ and FAILED events.
• RCS: reach Android users with rich cards, with SMS fallback.
• Errors and limits: handle 502 errors that carry Meta's error code.
• SDKs and OpenAPI: send WhatsApp messages with the TypeScript SDK.