WhatsApp Business API

Meta Business Verification

We create or configure your Meta Business Manager, submit your GST certificate / business registration, and push through Meta's verification queue. Verified status unlocks higher messaging limits and green tick eligibility.

WABA & Phone Number Setup

We create your WhatsApp Business Account (WABA) under the verified Business Manager and register a dedicated phone number. The number must not be active on the WhatsApp consumer or WhatsApp Business app — we'll guide you on acquiring a clean SIM or VoIP number if needed.

Display Name & Profile

We submit your business display name, description, and category for Meta review. A well-written profile speeds up approval and is required before you can send messages. The green verified badge is applied for separately once your volume qualifies.

Message Template Creation & Approval

We write, format, and submit your HSM templates for each use case. Templates fall into three Meta-defined categories:

Most templates are approved within 24 hours. We re-submit if rejected and adjust copy to meet Meta's guidelines.

Template name:  otp_login
Category:       AUTHENTICATION
Language:       en

Body:
  "Your {{1}} login code is *{{2}}*. Valid for 10 minutes."

Footer:
  "Do not share this code with anyone."

Buttons:
  Copy Code  →  {{2}}

API Integration into Your App

We wire the Meta Cloud API into your codebase. The core call to send a template message looks like this:

# Send an OTP message via Meta Cloud API
POST https://graph.facebook.com/v20.0/{PHONE_NUMBER_ID}/messages
Authorization: Bearer {ACCESS_TOKEN}
Content-Type: application/json

{
  "messaging_product": "whatsapp",
  "to": "+919876543210",
  "type": "template",
  "template": {
    "name": "otp_login",
    "language": { "code": "en" },
    "components": [{
      "type": "body",
      "parameters": [
        { "type": "text", "text": "Bansal Solutions" },
        { "type": "text", "text": "847291" }
      ]
    }]
  }
}

We set up environment variables, handle token refresh, and implement a BullMQ queue so high-volume sends don't block your main process.

# .env additions
WA_PHONE_NUMBER_ID=1234567890
WA_ACCESS_TOKEN=EAABwzLixnjYB...
WA_WEBHOOK_VERIFY_TOKEN=my_secure_random_token
WA_BUSINESS_ACCOUNT_ID=9876543210

Webhook & Go-Live

We register a webhook URL on your server (or a Cloudflare Worker) to receive incoming messages, delivery receipts, and read confirmations. After a test run on Meta's sandbox numbers, we flip to production and hand over monitoring access.

# Minimal webhook handler (Node / Express)
app.get('/webhook', (req, res) => {
  // Verify token challenge from Meta
  if (req.query['hub.verify_token'] === process.env.WA_WEBHOOK_VERIFY_TOKEN)
    res.send(req.query['hub.challenge']);
  else res.sendStatus(403);
});

app.post('/webhook', (req, res) => {
  // Handle incoming messages and status updates
  const { entry } = req.body;
  entry?.[0]?.changes?.[0]?.value?.messages?.forEach(handleMessage);
  res.sendStatus(200);
});