Post By
Published
Sep 15, 2025
Reading Time
8 min read
I built GTA.BD, a WhatsApp Business platform that lets organizations run campaigns, automate conversations, and track engagement from one dashboard. Integrating the WhatsApp Business Cloud API taught me lessons that the official docs only hint at. Here is the field guide I wish I had on day one.
Getting access: Cloud API, not on-premise
Meta's Cloud API is now the way — free hosting of the API itself, no Docker stack to babysit. You need a Meta Business account, a verified business, a phone number not registered to a personal WhatsApp, and a System User token. Budget real calendar time for business verification; it is the slowest step in the whole project.
Respect the 24-hour conversation window
You can send free-form messages only within 24 hours of the user's last message. Outside that window, only pre-approved template messages are allowed. Architect this as a state machine on the conversation: window open or closed drives which send paths are legal. Build template management and the approval workflow into your product early — clients change templates constantly.
Webhooks are your source of truth
- Verify the webhook with the hub.challenge handshake and validate X-Hub-Signature-256 on every event
- Acknowledge fast: enqueue the payload and return 200 immediately — process in a queue worker
- Handle statuses (sent, delivered, read, failed) idempotently; Meta retries and duplicates happen
- Store raw payloads for replay — you will need them when debugging delivery disputes
Bulk messaging without getting banned
Messaging limits tier up with quality ratings. Blast too fast to cold lists and your number's rating tanks. I queue campaign sends with per-number rate limits, spread delivery over time, and watch the quality dashboard like a hawk. Opt-in hygiene is not legal box-ticking — it is what keeps your sender alive.
WhatsApp is the highest-engagement channel I have ever integrated — open rates dwarf email. Built carefully, it transforms how businesses talk to customers; built carelessly, you lose the number. The difference is engineering discipline.
