Back to all Posts
Blog Luca Borreani Luca Borreani Last updated: Apr 27, 2026

WhatsApp Business API: complete guide for ecommerce in 2026

Summarize with:
What you will learn

Zipchat AI

37.8% avg. conversion lift

Your AI Agent live in under 1 hour

No code. Trained on your catalog. Converts on every channel.

Create free Agent Book a demo
Free course

Learn Agentic Commerce

Earn certification and merch rewards. No credit card needed.

Start now →

WhatsApp Business API: complete guide for ecommerce in 2026

Summary: The WhatsApp Business API is the programmatic interface that powers WhatsApp marketing, automation, and support at scale. This guide covers every layer: the API architecture, conversation type pricing, template approval rules, BSP vs. direct API setup, messaging tiers, GDPR compliance, and how Zipchat connects the API to Shopify stores without developer involvement.


What the WhatsApp Business API is

Answer: The WhatsApp Business API is Meta’s programmatic interface for sending and receiving WhatsApp messages at scale. It enables:

  1. Outbound messaging at scale: broadcasts, cart recovery sequences, order confirmations, shipping updates, and post-purchase campaigns to opted-in lists of any size.

  2. Inbound AI handling: automated responses to customer messages using AI that understands natural language, queries Shopify order data, and resolves support issues.

  3. System integration: connects WhatsApp to Shopify, CRMs, analytics platforms, and third-party tools via webhooks and API events.

The free WhatsApp Business App supports none of this. It is a mobile app for manual messaging from one device with a 256-contact broadcast limit. The API is the infrastructure layer that makes WhatsApp commerce viable at scale.

For how to use the API for marketing campaigns, see the WhatsApp marketing guide. For automation flows on Shopify, see WhatsApp automation for Shopify. For the full cluster overview: WhatsApp commerce hub.


WhatsApp API architecture: how it works

The WhatsApp Business API sits between your business systems and WhatsApp’s infrastructure. Here is the data flow:

Outbound (you to customer): Your system (Zipchat / Shopify / your CRM) triggers an API call → Meta validates the template and the recipient opt-in → Meta delivers the message to the recipient’s WhatsApp → Delivery receipt returned to your system.

Inbound (customer to you): Customer sends a WhatsApp message → Meta routes it to your webhook endpoint (your BSP or your server) → AI processes the message and generates a response → API sends the response back to the customer’s WhatsApp.

Webhooks: Your system registers webhook URLs with Meta. Meta sends event notifications to those URLs when specific events occur: message received, message delivered, message read, message failed, template status changed.

The API is stateless: Meta does not store conversation history. Your platform (Zipchat) stores all conversation data and provides the context the AI needs to personalize responses.


Conversation types and pricing

Meta charges per conversation, not per message. A conversation is a 24-hour window opened by a message exchange. Multiple messages within the same 24 hours in the same conversation incur one conversation charge.

Five conversation types:

TypeInitiatorTemplate requiredPricing tier
MarketingYou (business)YesHighest
UtilityYou (business)YesMedium
AuthenticationYou (business)YesMedium
ServiceCustomerNoFree
ReferralCustomer (via Click-to-WhatsApp ad)NoFree (first 72 hours)

Marketing conversations: Cart recovery, win-back campaigns, product launches, promotional broadcasts. All require pre-approved templates.

Utility conversations: Order confirmations, shipping updates, return confirmations, appointment reminders. These are transactional. Templates required but approval rates are high.

Authentication: OTPs and verification codes. Lowest error rates; Meta prioritizes delivery.

Service conversations: A customer messages you first. The 24-hour window is free. No template required for your responses within the window. Service conversations represent the entirety of inbound customer support traffic.

Sample pricing (April 2026):

MarketMarketingUtilityService
United States$0.025$0.015Free
Brazil$0.065$0.025Free
India$0.011$0.004Free
Germany$0.036$0.014Free
Mexico$0.036$0.011Free

Prices change periodically. Verify current rates at Meta’s pricing page.


BSP vs. direct API: which path is right for you

Business Solution Provider (BSP): A BSP is a Meta-certified partner (Zipchat, Twilio, 360dialog, Vonage) that manages API access for you. You configure your chatbot in the BSP dashboard. The BSP handles infrastructure, webhook management, message delivery, and template submission.

Advantages: No engineering required. Faster deployment (hours vs. weeks). Ongoing maintenance handled. Support included. Disadvantage: Additional monthly fee on top of Meta’s per-message costs.

Direct Meta Cloud API: Integrate with Meta’s Cloud API directly. You manage webhooks, server infrastructure, message routing, and error handling.

Advantages: Lower per-message cost (no BSP markup). Full control over data flow. Disadvantage: Engineering resources required. 2 to 8 weeks to deploy. Ongoing maintenance falls on your team.

Decision framework:

ScenarioRecommended path
Shopify store, no engineering teamBSP (Zipchat)
Shopify store with engineering teamEvaluate BSP vs. direct based on volume
High message volume (10M+/month)Direct API often more cost-effective
Multi-platform (Shopify + CRM + custom systems)BSP with API connectors
Fastest time to liveBSP always

Template approval: complete rules

Templates are the governed layer of the WhatsApp API. Every outbound message to a contact outside a 24-hour service window requires a pre-approved template.

Template components:

  • Header: Text, image, document, or video. Optional.
  • Body: The message content. Variables formatted as {{1}}, {{2}} or named {{product_name}}. Max 1,024 characters.
  • Footer: Optional disclaimer or opt-out text. Max 60 characters.
  • Buttons: Call-to-Action (URL or phone number) or Quick Reply (pre-set response triggers). Max 3 buttons.

Approval criteria:

  • Template must match the category selected (Marketing, Utility, Authentication).
  • CTA must be specific and actionable.
  • No prohibited content for the account’s registered market.
  • Variables must be present where personalization is claimed.
  • No deceptive or misleading language.

Approval timeline: 24 to 48 hours for most templates. Complex or borderline templates may take longer or require clarification from Meta.

Common rejection reasons:

  1. Vague CTA: “Check out our deals” → rejected. “Shop the sale: [URL]” → approved.
  2. Wrong category: promotional message submitted as Utility → rejected.
  3. Prohibited content: alcohol, gambling, or financial content without required disclaimers.
  4. Excessive capitalization: “BEST PRICES EVER!” → rejected.
  5. Misleading urgency: “Last chance!” without a real deadline → rejected.

Template rejection recovery: Review the rejection reason in Meta Business Suite. Edit the template and resubmit. Most rejections are correctable with one resubmission.


Messaging tiers and scaling

New WhatsApp Business API accounts start at Tier 1: 1,000 unique contacts per 24-hour period.

Tier progression:

TierDaily unique contacts
Tier 11,000
Tier 210,000
Tier 3100,000
Tier 4Unlimited

You advance tiers automatically by:

  1. Maintaining a Green quality rating.
  2. Sending to the current tier’s daily maximum within a 7-day window.
  3. After 7 days at the volume threshold without quality degradation, Meta automatically upgrades your tier.

Quality rating: Meta assigns Green (high), Yellow (medium), or Red (low) based on opt-out rates, spam reports, and engagement metrics. A Red rating lowers your daily tier temporarily. Recover by pausing marketing sends for 7 days and then resuming with high-relevance, segmented campaigns.

For a new ecommerce store: start with Tier 1. Send consistent, segmented, relevant campaigns. Most stores reach Tier 2 within 30 days and Tier 3 within 90 days.


GDPR compliance for WhatsApp API

For stores serving EU/EEA customers, GDPR requirements apply to WhatsApp API usage:

1. Explicit consent. Before sending marketing messages, you must have explicit WhatsApp marketing consent from the customer. A pre-ticked checkbox is invalid. An unchecked checkbox at checkout with clear consent language is valid.

2. Consent records. Store a record of each consent: timestamp, the exact consent text shown, and the customer’s phone number. Zipchat records this automatically.

3. Opt-out handling. Every marketing message must include an opt-out instruction. Opt-outs must be processed immediately and the contact removed from future marketing sends.

4. Data minimization. Use customer data only for the stated consent purpose. Do not use WhatsApp opt-in data for purposes not covered by the consent text.

5. Data storage. Meta’s data storage under the EU-US Data Privacy Framework is compliant. Your BSP’s data storage must also be GDPR-compliant. Zipchat stores data in EU-region infrastructure.

6. Data subject rights. Customers have the right to access, rectify, and delete their data. Zipchat’s dashboard supports customer data deletion requests.


Connecting WhatsApp API to Shopify

The integration connects three systems: WhatsApp Business API, Shopify store data, and Zipchat’s AI layer.

Data flowing from Shopify to WhatsApp:

  • Abandoned cart events (trigger cart recovery sequences)
  • Order created events (trigger order confirmation messages)
  • Fulfillment events (trigger shipping update messages)
  • Customer records (match WhatsApp phone numbers to customer profiles)
  • Product catalog (AI product knowledge)
  • Order history (AI context for support conversations)

Data flowing from WhatsApp to Shopify:

  • Customer opt-in records (stored to Shopify customer metafields)
  • Shopify return requests initiated via WhatsApp
  • Discount codes applied via WhatsApp conversations
  • Revenue attribution for orders completed after WhatsApp touchpoints

Setup via Zipchat requires no Shopify development. The Zipchat Shopify app uses standard Shopify APIs and reads data with the permissions granted at install.


API errors and common integration issues

Error: Message not delivered (failed) Cause: recipient’s number is not registered on WhatsApp, or the number format is incorrect. Fix: validate phone number format (international format with country code, no spaces or dashes). Remove invalid numbers from your list.

Error: Template rejected post-approval Cause: Meta periodically re-reviews approved templates. If a policy violation is found post-approval, the template is deactivated. Fix: review the policy change, edit the template, resubmit.

Error: Quality rating drop Cause: opt-out rate above 2% on a recent campaign, or spam reports. Fix: pause marketing sends for 7 days. Audit recent campaigns for relevance. Resume with tighter segmentation.

Error: Webhook not receiving events Cause: webhook URL is unreachable, SSL certificate expired, or webhook verification failed. Fix: verify SSL certificate validity, confirm the webhook URL is publicly accessible, and re-register the webhook in Meta Business Manager.

Integropet connected WhatsApp API via Zipchat and runs order support and product recommendations through WhatsApp at scale. Read the Integropet story.



Get WhatsApp API access through Zipchat

Zipchat provides WhatsApp Business API access as part of its platform. No separate Meta API setup. No engineering resources required for standard Shopify integrations.

See WhatsApp features or book a demo to discuss API access for your store’s volume and market.