WhatsApp Business API

Send WhatsApp template messages and bulk campaigns, manage your templates, reply free-form inside the 24-hour customer-service window, and read your number’s health — all over plain HTTPS with your server credentials. It’s the same engine that powers the QuickAuth dashboard, exposed as a clean REST API for your backend.

Base URL

https://api.quickauth.in/v1/whatsapp

All endpoints accept and return application/json.

Authentication

Every request is authenticated server-to-server with your client credentials — the same pair you use for the Auth and Marketing APIs. Never expose these in a browser or mobile app.

Find both keys in Dashboard → Settings → API keys. A missing or wrong pair returns 401.

How WhatsApp sending works

WhatsApp doesn’t let you send arbitrary text to a customer out of the blue — business-initiated messages must use a pre-approved template. The lifecycle is always the same:

1. Create a template once (POST /templates) and wait for it to reach APPROVED.
2. Send it to one recipient (POST /messages) or many (POST /campaigns), filling its variables per recipient.
3. Once a customer replies, a 24-hour window opens in which you can send free-form text with no template (POST /messages/session).

Template categories

Variables

Put numbered placeholders {{1}}, {{2}} … in your template body. At send time you pass a variables map of name → value per recipient — QuickAuth substitutes them before delivery. Declare each variable’s name and an example when you create the template so Meta can review it.

Billing & limits

• Template sends are billed per your plan — prepaid credits are debited on send; postpaid WhatsApp marketing accrues to your monthly invoice.
• A session (free-form) message costs one WhatsApp credit.
• A single /campaigns call takes up to 100 recipients. For larger lists, page your audience and call it repeatedly.

Quickstart — send your first message

Assuming you already have an APPROVED template named order_shipped with two variables:

curl https://api.quickauth.in/v1/whatsapp/messages \
  -H "Content-Type: application/json" \
  -H "X-Client-Id: qa_client_***" \
  -H "X-Client-Secret: qa_secret_***" \
  -d '{
    "templateId": "order_shipped",
    "to": "919876543210",
    "variables": { "name": "Asha", "tracking": "BLX-4471" }
  }'

Templates

POST /v1/whatsapp/templates
X-Client-Id: qa_client_***
X-Client-Secret: qa_secret_***
Content-Type: application/json

{
  "name": "order_shipped",
  "language": "en",
  "category": "UTILITY",
  "body": "Hi {{1}}, your order is on the way! Track it here: {{2}}",
  "footer": "Reply STOP to opt out",
  "variables": [
    { "name": "name",     "example": "Asha" },
    { "name": "tracking", "example": "BLX-4471" }
  ],
  "buttons": [
    { "type": "URL", "text": "Track order", "url": "https://shop.example/t/{{1}}", "urlParam": "BLX-4471" }
  ]
}

curl https://api.quickauth.in/v1/whatsapp/templates \
  -H "X-Client-Id: qa_client_***" \
  -H "X-Client-Secret: qa_secret_***"

Template status reference

Sending messages

POST /v1/whatsapp/messages

{
  "templateId": "order_shipped",   // an APPROVED template
  "to": "919876543210",            // international format, digits only
  "variables": {                   // optional — keyed by your variable names
    "name": "Asha",
    "tracking": "BLX-4471"
  }
}

POST /v1/whatsapp/campaigns

{
  "templateId": "diwali_offer",
  "campaignName": "Diwali 2026 — VIP segment",
  "recipients": [
    { "phoneNumber": "919876543210", "variables": { "name": "Asha",  "code": "VIP20" } },
    { "phoneNumber": "919812345678", "variables": { "name": "Rahul", "code": "VIP20" } }
  ]
}

POST /v1/whatsapp/messages/session

{
  "to": "919876543210",
  "text": "Thanks for reaching out! Your refund is processed ✅"
}

Account health

curl https://api.quickauth.in/v1/whatsapp/health \
  -H "X-Client-Id: qa_client_***" \
  -H "X-Client-Secret: qa_secret_***"

Errors

Errors use standard HTTP status codes with a JSON body of shape { error: { code, message } }.