The short version: the WhatsApp Business API is Meta’s programmatic interface for sending and receiving WhatsApp messages at scale. In 2026 it bills per message, not per 24-hour conversation: business-initiated marketing and authentication templates are charged per message, utility templates are free inside an open customer window, and customer-initiated service messages are free. This guide covers the architecture, the 2026 pricing, template rules, messaging tiers, GDPR, and Shopify setup.
What the WhatsApp Business API is
The WhatsApp Business API is Meta’s programmatic interface for WhatsApp at scale. It enables:
Outbound messaging at scale: broadcasts, cart recovery, order confirmations, shipping updates, and post-purchase campaigns to opted-in lists of any size.
Inbound AI handling: automated responses using AI that understands natural language, reads Shopify order data, and resolves issues.
System integration: connects WhatsApp to Shopify, CRMs, and analytics via webhooks and API events.
The free WhatsApp Business App supports none of this. It is a single-device mobile app with a 256-contact broadcast limit. The API is the infrastructure that makes WhatsApp commerce viable at scale. For marketing campaigns see the WhatsApp marketing guide; for automation flows see WhatsApp automation for Shopify; for the cluster overview see the WhatsApp commerce hub.
WhatsApp API architecture: how it works
Outbound (you to customer): your system (Zipchat, Shopify, your CRM) triggers an API call, Meta validates the template and opt-in, Meta delivers the message, and a delivery receipt returns to your system.
Inbound (customer to you): the customer sends a message, Meta routes it to your webhook, the AI processes it and generates a response, and the API sends the reply.
Webhooks: you register webhook URLs with Meta, which sends events (message received, delivered, read, failed, template status changed).
The API is stateless: Meta does not store conversation history; your platform (Zipchat) stores conversation data and the context the AI uses to personalize responses.
Conversation types and 2026 pricing (per message)
Meta changed the billing model. As of July 1, 2025, and standard through 2026, WhatsApp bills per message for business-initiated templates, not per 24-hour conversation. The category determines cost.
| Type | Initiator | Template | 2026 billing |
|---|
| Marketing | Business | Required | Charged per message |
| Utility | Business | Required | Free inside an open customer window; otherwise charged per message |
| Authentication | Business | Required | Charged per message |
| Service | Customer | Not required | Free |
Two rules matter most. First, customer-initiated service messages (anything the customer starts) are free, and so are your replies within the 24-hour customer window. Second, within that 24-hour window you can send multiple messages, including automated follow-ups, at no Meta message fee; you pay Meta per message only for business-initiated marketing and authentication templates, and for utility templates sent outside an open window. Meta fees are paid to Meta directly and vary by country.
Sample per-message rates (Q2 2026, delivered message, source: Meta for Developers):
| Country | Marketing | Utility | Authentication | Service |
|---|
| United States | ~$0.025 | ~$0.004 to 0.005 | ~$0.0135 to 0.015 | Free |
| Brazil | ~$0.0625 | ~$0.007 to 0.008 | ~$0.007 to 0.0225 | Free |
| India | ~$0.0094 to 0.0118 | ~$0.0014 | ~$0.0014 | Free |
| Germany | ~$0.11 to 0.14 | ~$0.033 to 0.055 | ~$0.046 to 0.077 | Free |
| Mexico | ~$0.031 to 0.044 | ~$0.008 | ~$0.0085 to 0.021 | Free |
Rates update quarterly (next change around July 1, 2026); verify the current rate card on Meta for Developers before modeling spend.
BSP vs direct API: which path is right for you
A Business Solution Provider (BSP) is a Meta-certified partner (Zipchat, Twilio, 360dialog) that manages API access. You configure your agent in the BSP dashboard; the BSP handles infrastructure, webhooks, delivery, and template submission. No engineering, faster deployment, ongoing maintenance included; the trade is a platform fee on top of Meta’s per-message costs.
The direct Meta Cloud API gives full control and lower per-message cost, but you manage webhooks, servers, routing, and error handling, which takes 2 to 8 weeks and ongoing engineering.
| Scenario | Recommended path |
|---|
| Shopify store, no engineering team | BSP (Zipchat) |
| Shopify store with engineering team | Evaluate BSP vs direct by volume |
| Very high volume (10M+ messages/month) | Direct API often cheaper |
| Multi-platform (Shopify + CRM + custom) | BSP with API connectors |
| Fastest time to live | BSP always |
Template approval: the rules
Every business-initiated message outside the customer window uses a pre-approved template. Components: header (optional), body (variables like {{1}} or {{product_name}}, max 1,024 characters), footer (optional, max 60 characters), and up to 3 buttons (CTA or quick reply).
Approval criteria: the template must match its category, the CTA must be specific and actionable, content must comply for the registered market, and variables must be present where personalization is claimed. Common rejections: vague CTA (“check out our deals”), wrong category (a promo submitted as Utility), prohibited content, excessive capitalization, and misleading urgency. Marketing templates take 3 to 7 business days to review; authentication is often same-day. Edit and resubmit to recover from a rejection.
Messaging tiers and scaling
New accounts start at 1,000 unique contacts per 24 hours, then progress to 10,000, 100,000, and unlimited. Two changes matter in 2026: limits now apply at the Business Portfolio level (not per phone number, since October 2025), and Meta is moving verified businesses toward a 100,000/day baseline, removing the lower 2K and 10K steps. You advance by maintaining a Green quality rating and sending at the tier’s volume without quality degradation. Quality rating (Green, Yellow, Red) reflects opt-out and block rates; a Red rating lowers your limit temporarily, recovered by pausing marketing for 7 days and resuming with segmented, relevant sends.
GDPR compliance for the WhatsApp API
For EU/EEA customers: explicit, channel-specific WhatsApp marketing consent before sending marketing templates (a pre-ticked checkbox is invalid); a stored consent record (timestamp, exact consent text, phone number); an opt-out instruction in every marketing message, processed immediately; data minimization to the stated purpose; a DPA with your BSP; and support for access and erasure requests. A 2026 change: WhatsApp-native opt-in is required for marketing since May 2026, so a website checkbox alone is no longer sufficient for marketing consent in the EU (DSA and updated guidance). Zipchat records consent and stores data in EU-region infrastructure.
Connecting the WhatsApp API to Shopify
The integration connects three systems: the WhatsApp API, Shopify data, and Zipchat’s AI.
From Shopify to WhatsApp: abandoned cart events (recovery sequences), order created (confirmations), fulfillment events (shipping updates), customer records (match phone to profile), product catalog (AI knowledge), and order history (support context).
From WhatsApp to Shopify: opt-in records (to customer metafields), returns initiated via WhatsApp, discount codes applied in chat, and revenue attribution for orders after WhatsApp touchpoints.
Setup via Zipchat needs no Shopify development; the app uses standard Shopify APIs with the permissions granted at install.
API errors and common integration issues
Message not delivered (failed): the number is not on WhatsApp or the format is wrong. Validate international format (country code, no spaces or dashes) and remove invalid numbers.
Template rejected post-approval: Meta re-reviews; a policy violation deactivates it. Review the change, edit, resubmit.
Quality rating drop: opt-out rate above 2% or spam reports. Pause marketing 7 days, audit relevance, resume with tighter segmentation.
Webhook not receiving events: unreachable URL, expired SSL, or failed verification. Confirm the URL is public, the certificate is valid, and re-register the webhook.
Integropet connected the WhatsApp API via Zipchat and runs order support and product recommendations on WhatsApp at scale. Read the Integropet story.
FAQ
How does WhatsApp Business API pricing work in 2026?
It bills per message, not per 24-hour conversation. Business-initiated marketing and authentication templates are charged per delivered message; utility templates are free inside an open customer window; customer-initiated service messages and your replies within the 24-hour window are free. Rates vary by country and are paid to Meta.
Are messages inside the 24-hour window free?
Yes. Within the 24-hour customer window you can send multiple messages, including automated follow-ups, with no Meta message fee. You pay only for business-initiated marketing and authentication templates and for utility templates sent outside an open window.
What is the difference between the WhatsApp Business App and the API?
The free app is single-device manual messaging with a 256-contact broadcast cap. The API supports automation, AI handling, unlimited opted-in sends, and integration with Shopify and CRMs, at scale.
How do I connect the WhatsApp API to Shopify?
Through a BSP like Zipchat: a verified Meta Business Account and a dedicated phone number, then the BSP handles the API, webhooks, and templates, and the Zipchat app reads Shopify order and catalog data with no custom development.
Is WhatsApp Business API GDPR compliant?
It can be, with explicit channel-specific opt-in, stored consent records, an opt-out in every marketing message, a DPA with your BSP, and support for erasure. Since May 2026, WhatsApp-native opt-in is required for marketing in the EU; a website checkbox alone is not sufficient.
Get WhatsApp API access through Zipchat
Zipchat provides WhatsApp Business API access as part of the platform, with no separate Meta setup and no engineering for standard Shopify integrations. See WhatsApp features or book a demo.
