WhatsApp Template Message API Guide: Create, Approve & Send (2026)

WhatsApp template messages are pre-approved message formats required whenever your business initiates a conversation outside the 24-hour customer service window. Order confirmations, marketing broadcasts, OTP codes — they all flow through the WhatsApp template message API on Meta's Cloud API. Get templates wrong and nothing sends. Get them right and you have a scalable, compliant messaging layer.

This guide covers the four template categories, creation and approval workflow, REST API send syntax, variable rules, rejection fixes, broadcast strategy, troubleshooting error codes, and how Ominiflow simplifies template management for Indian teams.

Too long? Start here

• Templates must be approved by Meta before sending — typically minutes to 48 hours
• Four categories: marketing, utility, authentication, service — pricing differs per country
• Variables use {{1}}, {{2}} placeholders mapped in API components array
• Business-initiated = template required. Inside 24-hour window after customer messages = free-form allowed
• Error #132000 = variable count mismatch — most common production failure
• India tip: create separate Hindi and English templates per use case

What are WhatsApp message templates?

Templates are standardized message shells with fixed body text and optional header (text, image, video, document), footer, and interactive buttons (quick reply, URL, phone). Meta reviews each template for policy compliance before approval.

That's the core constraint of WhatsApp API integration: your ERP can't fire a free-form "your package left the warehouse" string unless the customer is inside the 24-hour window.

"Template approval isn't a day-before-launch task. Build template creation into your project timeline from week one — rejections delay every downstream integration."

The 24-hour rule

• Session messages: Customer messages you first → 24 hours to reply freely without templates
• Business-initiated: You reach out first → approved template required in correct category

Map every outbound trigger to a template name before writing connector code.

Template categories explained

Full pricing: API pricing guide. Never submit promotional copy as utility — Meta rejects and may flag your account.

How to create and submit templates

1. Draft in Ominiflow — Template manager: category, language, body text
2. Add variables — {{1}}, {{2}} for dynamic fields. Provide sample values for Meta review
3. Choose components — Optional header image, footer disclaimer, CTA buttons
4. Submit to Meta — Ominiflow syncs to Cloud API; status: pending → approved or rejected
5. Test send — Your own number before broadcasting to customers

Create marketing, utility, or authentication templates in Ominiflow — category, language, variables, and Meta-style preview in one screen. Template Builder V2 — Meta-style workflow with category picker, sync to Cloud API, and live WhatsApp preview.

Variable rules Meta enforces

• No variable at the very start or end of body text — add static words around placeholders
• Variable count in send payload must match template exactly (error #132000 if mismatch)
• Sample values must be realistic during submission
• URLs should use your domain — avoid opaque shorteners
• Maximum variables per template varies by category — check Meta docs for current limits

Sending templates via API

POST https://graph.facebook.com/v21.0/{PHONE_NUMBER_ID}/messages
Authorization: Bearer {ACCESS_TOKEN}
Content-Type: application/json

{
  "messaging_product": "whatsapp",
  "to": "919876543210",
  "type": "template",
  "template": {
    "name": "order_shipped",
    "language": { "code": "en" },
    "components": [{
      "type": "body",
      "parameters": [
        { "type": "text", "text": "Priya" },
        { "type": "text", "text": "ORD-88421" },
        { "type": "text", "text": "https://track.example/88421" }
      ]
    }]
  }
}

Header image example — add components block with type header and image link parameter.

Walkthrough: send messages programmatically · webhook guide

Template best practices

• Match category to content — utility for transactional only
• One template per trigger — not one mega-template with 8 variables
• Include opt-out language — marketing templates should mention how to unsubscribe
• Localize — Hindi + English templates for India campaigns
• Monitor quality rating — high block/report rates reduce messaging tier
• Version control — log template name + version in outbound audit logs
• Pre-warm before festivals — submit Diwali templates 48h before peak send

Common rejection reasons and fixes

Production error codes

More pitfalls: 5 common API mistakes

Templates in broadcast campaigns

Marketing broadcasts send an approved template to a segmented contact list. On Ominiflow: segment audiences, schedule sends, track delivery/read/click rates.

Pair approved templates with contact segments before scheduling a marketing broadcast.

Pair with bulk messaging best practices for opt-in compliance.

Benchmark: automated journeys average 11.1% CTR vs 2.6% for unsegmented broadcasts — 2026 marketing benchmark.

FAQ