Guaranteed 100% Facebook, Instagram and WhatsApp Approvals & App Review
Quick Transfer Ready to use app available for Facebook, Instagram and WhatsApp
Guaranteed 100% Facebook, Instagram and WhatsApp Approvals & App Review
Quick Transfer Ready to use app available for Facebook, Instagram and WhatsApp
WhatsApp Business API

WhatsApp Cloud API Setup in 2026: What Changed After the On-Premises API Shutdown

Meta shut down the WhatsApp Business API on-premises client in October 2025. The self-hosted Docker-based API is gone. Every new WhatsApp Business API setup in 2026 goes through the Cloud API — hosted by Meta, no server infrastructure required. But the setup is not as simple as it sounds.

What this means for new setups: If you are starting a new WhatsApp Business API integration in 2026, there is only one path: the Cloud API. You do not need a server or BSP portal to access the API itself — Meta hosts it. But Business Verification, phone number registration, display name approval, webhook setup, and template approval are all still required gates. Removing the infrastructure complexity does not remove the compliance complexity.

What Changed and What Stayed the Same

✕ What is gone (on-premises only)

✕Docker container or VM running the self-hosted client
✕Server infrastructure managed by the business or developer
✕Local database for message storage on your server
✕BSP portal as the mandatory access layer for API calls
✕Version upgrades pushed manually to self-hosted containers

✓ What remains (Cloud API too)

✓Meta Business Verification as the primary access gate
✓Phone number registration and display name approval
✓Message template approval before outbound messaging
✓Webhook setup for incoming messages and status updates
✓Messaging tier limits and quality rating system

What Cloud API Setup Requires in 2026

✅

Meta Business Manager and Business Verification

A WhatsApp Business Account (WABA) is created under your Meta Business Manager account. Before you can message any non-test phone numbers at production scale, the Business Manager must pass Meta Business Verification. Without verification, the account is limited to messaging registered test numbers only. Business Verification requires legal business documents, a matching business name, and an address or phone confirmation — and Meta's review takes 5–15 days on average, with no fast-track option.

📞

Phone number registration and display name

The phone number you register on the Cloud API must not be actively used in the WhatsApp consumer app or another WABA. Once registered, you submit a display name — a short business label shown to recipients. Meta's team reviews the display name against the WhatsApp Business Display Name guidelines. A mismatched, generic, or policy-violating display name is declined, and the account remains in a restricted state until a compliant name is approved. Numbers previously registered with another BSP require a formal migration or release process before they can be re-registered on the Cloud API.

🔗

Webhook setup for incoming messages

The Cloud API delivers incoming messages, message status updates, and account events via webhooks — HTTPS callbacks to a URL you register in your App Dashboard. The webhook endpoint must be publicly accessible, must complete Meta's verification challenge (responding with the hub.challenge value), and must return HTTP 200 for event deliveries within 20 seconds. Without a working webhook, you can send messages but cannot receive replies or status notifications — making two-way communication impossible.

📄

Message template approval for outbound messaging

WhatsApp Cloud API does not allow free-form outbound messages to users outside an active 24-hour customer service window. Business-initiated conversations must use approved message templates. Interactive in-chat forms run on the Cloud API but need their own approval, and our WhatsApp Flows API App Review guide covers the prerequisites. Each template must be submitted to Meta for approval — reviewed against the WhatsApp Business Policy for content type, variable formatting, and category classification. Templates can be rejected, recategorized, or paused. Approval typically takes minutes to hours, but rejections require revision and resubmission before the outbound use case goes live.

📈

Messaging limits and quality rating

New WABAs start at Tier 1: 1,000 business-initiated conversations per 24 hours. Cloud API access is free, but per-message charges still apply, so see how WhatsApp per-message pricing works in 2026. Messaging tiers scale based on the account's quality rating — which Meta calculates from user feedback signals (blocks, reports, low read rates). A poor quality rating drops the account to a lower tier or places it under review. Maintaining high deliverability requires template content that matches recipient expectations and consent-based contact lists. The Cloud API does not change this system — infrastructure simplification does not simplify the quality management requirements.

Related: If you are a SaaS platform onboarding multiple client phone numbers through WhatsApp, the Cloud API direct setup is not your path — you need the WhatsApp Tech Provider program and Embedded Signup. See the WhatsApp Embedded Signup and Tech Provider Onboarding guide for that workflow. For the general WhatsApp App Review service, see the WhatsApp App Review support page.

Where Cloud API Setup Stalls in Practice

✕Business Verification rejected or stuck at pending. The most common stall point. Meta's document review is strict: name on the business document must match the Business Manager name, documents must be recent (bank statements and utility bills within 12 months), mobile phone bills are not accepted. A single mismatch restarts the review. During the wait — which can stretch weeks if appeals are involved — the account cannot be used for production messaging.
✕Phone number is locked to another WABA or still registered on WhatsApp consumer app. Numbers must be fully released from any existing registration before they can be added to a Cloud API account. You no longer have to choose between the Business app and the API on one number, as explained in our guide to running the Business app and Cloud API on the same number. The release process (deleting the consumer account from the device, or formally migrating from a BSP) has specific steps — skipping any of them leaves the number in a state that blocks Cloud API registration.
✕Display name rejected, WABA restricted. A declined display name does not just delay setup — it places the account in a restricted state. Until a compliant name is approved, the number cannot be used for production messaging. Common rejection reasons include names that do not represent a verifiable business, names containing "Official" or "Verified," or names that do not match the verified business identity on record.
✕Webhook not configured or misconfigured. Many teams complete Business Verification and number registration, then treat the account as ready to go — without configuring the webhook. The result: the number can send messages, but all replies are silently lost. Proper webhook setup requires a production-accessible HTTPS URL, correct verification token handling, and event field subscriptions for the message types you need.
✕Templates rejected before go-live. The most common post-setup blocker. Templates that are promotional in structure but submitted as Utility, that contain floating variables, or that use language triggering Meta's content policy filters are rejected. A REJECTED template cannot be sent. The revised template must be resubmitted and re-approved before outbound campaigns or automated messages can launch.

For background on the WhatsApp Business Verification process that gates Cloud API production access, see the Meta Business Verification guide. For issues with WhatsApp display name rejection specifically, see the display name rejection guide.

Meta and WhatsApp make all Business Verification, display name, template approval, and account decisions independently. Setup outcomes and timelines cannot be guaranteed. This guide is based on publicly available Meta and WhatsApp developer documentation — it is not an official Meta or WhatsApp publication and is not affiliated with or endorsed by Meta Platforms, Inc. Not an official Meta partnership.