WhatsApp Cloud API, production-ready in 24 hours
Meta-hosted WhatsApp Cloud API — managed end-to-end by LandinChat. No servers, no maintenance. Green tick, templates, broadcasts, automation and a unified inbox out of the box.
- Official Meta Tech Partner
- Live in 24–72 hours
- Green tick assistance
- No servers to manage
Key things to know
Meta-hosted infrastructure
Zero servers. Meta runs Cloud API on Google Cloud with 99.99% SLA and global routing.
Fast feature access
Flows, interactive messages, calling and other Cloud-only features ship to you first.
Enterprise security
End-to-end encryption, SOC2-aligned controls, RBAC, audit log and IP-allowlisted webhooks.
Developer-friendly
Clean REST endpoints, webhook events, SDKs and code samples for Node, Python, Go and PHP.
People also ask
Q.What is the WhatsApp Cloud API?
WhatsApp Cloud API is Meta's hosted version of the WhatsApp Business Platform. Meta runs the messaging infrastructure on Google Cloud, so you don't have to host or maintain servers like with the legacy On-Premise API. It's the recommended path for almost every new project.
Q.Cloud API vs On-Premises API — which should I pick?
Cloud API for 99% of teams: free hosting, faster feature releases, simpler scaling. On-Prem only makes sense for strict data-residency or compliance requirements that prevent any Meta-hosted traffic.
Q.Is the Cloud API free?
Hosting is free. You only pay Meta for conversations (per the conversation-based pricing model) and for value-added platform features. See our pricing page for full plans.
Q.Do I still need a BSP if I'm on Cloud API?
Technically you can go direct to Meta, but a BSP / Tech Partner like LandinChat handles green tick verification, template approval, broadcasts, inbox, automation, ads, analytics and 24/7 support — things Meta's raw API does not provide.
Q.How fast can I go live on Cloud API with LandinChat?
Most customers are live in 24–72 hours: WhatsApp Business Account creation, phone number provisioning, display name approval, first templates approved, and broadcasts running.
Q.Does Cloud API support webhooks, media, interactive messages and Flows?
Yes. Cloud API supports text, media, list & button messages, interactive replies, WhatsApp Flows, location, contacts, and full delivery / read webhooks.
What WhatsApp Cloud API actually is
WhatsApp Cloud API is Meta's hosted implementation of the WhatsApp Business Platform. Instead of running your own server stack (the legacy On-Premises API), Meta runs the messaging infrastructure on Google Cloud and exposes a simple REST + webhook interface.
For builders, that means zero server ops, faster feature releases (Flows, interactive messages, calling), automatic scaling and lower total cost. Meta only bills you for conversations under its conversation-based pricing model.
LandinChat sits between you and the raw Cloud API: we handle Meta Business Verification, WABA setup, display-name approval, template policy review, green tick submission, broadcasts, inbox, automation flows, click-to-WhatsApp ads and analytics. Bring the use-case, we bring the platform.
Built for serious growth teams
Meta-hosted infrastructure
Zero servers. Meta runs Cloud API on Google Cloud with 99.99% SLA and global routing.
Fast feature access
Flows, interactive messages, calling and other Cloud-only features ship to you first.
Enterprise security
End-to-end encryption, SOC2-aligned controls, RBAC, audit log and IP-allowlisted webhooks.
Developer-friendly
Clean REST endpoints, webhook events, SDKs and code samples for Node, Python, Go and PHP.
Global reach
Send and receive in 180+ countries with localized templates and language detection.
Multi-number / multi-brand
Run multiple WABAs and numbers from one workspace with separate inboxes and flows.
Get live in days, not months
- 1
Tell us your number
Share your business phone number and Meta Business Manager details — or let us create them.
- 2
We verify your business
We complete Meta Business Verification and create your WhatsApp Business Account (WABA).
- 3
Display name & first templates
We get your display name and first 5 message templates approved by Meta.
- 4
Connect & broadcast
Connect to LandinChat inbox, build flows, import contacts and run your first broadcast.
- 5
Apply for green tick
We submit your Official Business Account application through the Tech Partner channel.
Cloud API vs On-Premises API
| Capability | LandinChat | On-Premises API |
|---|---|---|
| Hosting | Meta-hosted (free) | Self-hosted (servers + ops) |
| Time to live | 24–72 hours | 2–6 weeks |
| New features | First-class access | Delayed / deprecated |
| Scaling | Automatic | Manual capacity planning |
| Maintenance | Meta handles it | Your DevOps team |
| Recommended by Meta | Yes — strategic platform | Being phased out |
What teams ship with this
D2C & e-commerce
Abandoned cart recovery, order updates, COD confirmations and click-to-WhatsApp ads.
Fintech & lending
OTPs, KYC nudges, EMI reminders and statement delivery with verified sender identity.
Edtech & coaching
Lead qualification, demo bookings, drip nurture and student support at scale.
Travel & hospitality
Booking confirmations, itinerary delivery, check-in reminders and feedback.
Healthcare
Appointment reminders, report delivery and post-consult follow-ups.
SaaS & B2B
Trial activation, renewal nudges, billing and customer success at scale.
Frequently asked questions
What WhatsApp Cloud API actually is (and isn't)
Cloud API is Meta's own hosted REST + webhook interface to the WhatsApp Business Platform. Meta runs the messaging plane on Google Cloud, you run nothing. It is not a marketing suite, a shared inbox, a chatbot builder or a broadcast tool — it is the raw pipe. Everything a business team associates with "WhatsApp software" — templates library, campaigns, contact segments, agent routing, analytics — is built on top by a Tech Partner or by your own engineers.
That distinction matters because Meta has never sold Cloud API as a product to operators. The docs assume you are a developer wiring a backend. If your team is not building a platform, you need a Tech Partner between you and the API — otherwise every template approval, green-tick submission, quality-tier issue and Meta policy update becomes an engineering ticket.
Cloud API vs On-Premises: the honest table
| Dimension | Cloud API | On-Premises API |
|---|---|---|
| Hosting | Meta / Google Cloud | Your infra (K8s or VMs) |
| Time to live | 24–72h | 2–6 weeks |
| Ops overhead | None | Full: upgrades, DB, TLS, backups |
| Feature access | First-class (Flows, calling, ads) | Deprecated — Meta sunset in Oct 2025 |
| Throughput ceiling | 1000 msg/s (unlocked tier) | Bounded by your hardware |
| Media handling | Meta-hosted URLs | Your storage |
| Cost floor | $0 hosting + Meta conversations | Cluster + DevOps + Meta conversations |
Reference architecture that ships to prod
The minimum production shape:
- Outbound: your backend → POST
/{phone-number-id}/messages→ Meta Cloud → recipient. - Inbound: Meta Cloud → HTTPS webhook (verified via
hub.verify_token) → your queue (SQS / Kafka) → worker. - Media: upload once via
/media, reuse the media ID across sends; never re-upload the same file. - Templates: stored server-side, referenced by
name+language— never send free-form outside the 24h window. - Idempotency: log every send with a client-side UUID; Meta's
message_idis authoritative for delivery/read reconciliation.
Webhook events you must handle
| Event | Why it matters | Action |
|---|---|---|
| messages.status | Delivery reconciliation (sent/delivered/read) | Update outbound row by wamid |
| messages (inbound) | New user message | Enqueue → route to agent/bot; opens 24h window |
| account_alerts | Quality tier / limit changes | Alert ops; pause marketing if RED |
| template_status_update | Template approval / rejection | Update template state; notify author |
| phone_number_quality_update | Sender health change | Auto-throttle marketing sends |
Rate limits, tiers and how to unlock them
New numbers start at Tier 1 (1,000 unique business-initiated conversations / 24h). Tiers auto-upgrade when you send to your current limit with high quality for 2 consecutive days: T2 = 10K, T3 = 100K, T4 = unlimited. The trap: sending to a cold, unfiltered list at T1 will spike block rate, freeze the tier, and demote quality to YELLOW/RED within 48h. Ramp deliberately.
Five mistakes that kill Cloud API projects
- Building the platform layer in-house "because Cloud API is free" — then reinventing template management, quality monitoring, and inbox for 6 months.
- No opt-in ledger — Meta will ask for evidence when quality drops.
- Ignoring
phone_number_quality_update— marketing keeps sending on a RED number, WABA gets banned. - Storing media locally instead of Meta media IDs — hitting media upload rate limits.
- Free-form messages outside the 24h window — Meta silently drops them, reporting looks fine, delivery is zero.
Related: WhatsApp API overview · Cloud API pricing · WhatsApp Flows.
Ready to ship on WhatsApp?
Talk to our team about plans, onboarding and how LandinChat fits your stack.