Summary
The WhatsApp Business API enables medium and large businesses to communicate with customers at scale. Businesses can integrate the API into their systems to manage both automated and human-driven customer interactions.
WhatsApp Business API is available in two hosting options:
Cloud API (hosted by Meta)
On-Premises API (self-hosted by businesses or Business Solution Providers (BSPs))
Choosing the right option depends on your business needs. This guide breaks down the differences between Cloud API and On-Premises API, helping you determine which is best for your use case.
Important: A phone number can only be associated with one of these APIs at a time. You cannot use the same number on both platforms simultaneously.
Instructions
Cloud API Overview
Cloud API is hosted by Meta and allows businesses to send messages via the Graph API. It uses webhooks to receive events such as incoming messages and delivery status updates.
Key Features:
No server maintenance – Meta manages hosting and infrastructure.
Automatic updates – Businesses always have access to the latest features and security patches.
Higher message throughput – Supports up to 500 messages per second (combined sending and receiving).
Simplified authentication – Uses User Access Tokens.
Lower infrastructure costs – Businesses only pay for messages sent.
To learn more, refer to the Graph API Developer Documentation.
On-Premises API Overview
On-Premises API requires businesses or BSPs to host and maintain the WhatsApp API software on their own servers.
Key Features:
Greater control – Businesses manage their own infrastructure.
Custom security – Businesses control their own Certificate Authority (CA) and webhook certificates.
Supports Check Contacts API and Media Provider API, which are deprecated in Cloud API.
Lower latency for local deployments, depending on business infrastructure.
High availability required – Businesses must implement disaster recovery solutions.
Comparison: Cloud API vs. On-Premises API
Feature | Cloud API (Hosted by Meta) | On-Premises API (Self-hosted) |
Hosting | Hosted by Meta | Businesses/BSPs host on their own servers |
Maintenance | Meta handles upgrades and patches | Businesses/BSPs must manage updates and scaling |
Cost | Businesses pay per message sent | Additional infrastructure costs for server setup & maintenance + per-message fees |
API Protocol | Graph API | REST API |
Message Throughput | Up to 500 messages per second (combined sending & receiving) | Up to 70 messages per second (single-connect), 250 messages per second (multi-connect) |
Certificate Management | Managed by Meta | Businesses manage their own certificates |
Disaster Recovery | Meta ensures uptime (99.9% goal) | Businesses must implement failover solutions |
Single vs. Multi-Tenant | Multi-tenant (supports multiple phone numbers) | Single-tenant (one phone number per deployment) |
Monitoring | Meta monitors instance health | Businesses must set up monitoring themselves |
Baseline Error Rates | ~0.1% | Not published; varies by infrastructure |
Server Location | North America | Determined by business infrastructure |
SLA (Uptime) | Target 99.9% uptime | Varies depending on business setup |
Support | 24/7 support for critical issues | Best effort 24/7 support for critical issues |
Key Considerations for Choosing Between Cloud API and On-Premises API
When to Choose Cloud API
You do not want to manage servers and infrastructure.
You need scalability with minimal effort.
You want automatic updates without downtime.
Your business needs high throughput for messaging (up to 500 messages per second).
When to Choose On-Premises API
You require full control over infrastructure and security.
Your business cannot use Meta-hosted services due to regulatory constraints.
You rely on Check Contacts API and Media Provider API (deprecated in Cloud API).
You have existing infrastructure and resources for server management.
Deprecations in Cloud API
Some features available in On-Premises API are deprecated in Cloud API:
Feature | On-Premises API | Cloud API |
Check Contacts API | Required to verify phone numbers before sending messages | No longer needed – just use the phone number |
Media Provider API | Supported | Deprecated – use Cloud API media upload steps |
Conclusion
The choice between Cloud API and On-Premises API depends on your business needs:
Cloud API is best for businesses looking for ease of use, lower maintenance, and scalability.
On-Premises API is ideal for businesses that require full control, custom security, and on-premise hosting.
If you're still unsure, consider your infrastructure capabilities, security requirements, and scalability needs before making a decision.
Frequently Asked Questions (FAQs)
General Questions
1. What is the WhatsApp Business API?
→ The WhatsApp Business API allows businesses to communicate with customers at scale, enabling automated and human-driven messaging.
2. What are the two types of WhatsApp Business API hosting options?
→ There are two hosting options:
Cloud API – Hosted by Meta, requires no server maintenance.
On-Premises API – Self-hosted by businesses or Business Solution Providers (BSPs), requiring server management.
3. Can I use both Cloud API and On-Premises API at the same time?
→ No, a phone number can only be registered on one platform at a time.
Cloud API
4. What is Cloud API?
→ Cloud API is a Meta-hosted WhatsApp Business API that allows businesses to send messages via the Graph API without managing their own infrastructure.
5. What are the benefits of using Cloud API?
No need for server setup or maintenance.
Automatic updates with new features and security patches.
Higher message throughput (up to 500 messages per second).
Lower infrastructure costs (only pay for messages sent).
6. Where are Cloud API servers located?
→ Cloud API servers are hosted in North America.
7. What authentication method does Cloud API use?
→ Cloud API uses User Access Tokens for authentication.
8. Does Cloud API support Check Contacts API or Media Provider API?
→ No, these APIs are deprecated in Cloud API.
On-Premises API
9. What is On-Premises API?
→ On-Premises API is a self-hosted version of the WhatsApp Business API that businesses or BSPs must manage on their own servers.
10. What are the advantages of using On-Premises API?
Full control over infrastructure and security.
Ability to manage certificates and compliance requirements.
Can be deployed in high availability models for disaster recovery.
Supports Check Contacts API and Media Provider API (which are deprecated in Cloud API).
11. What are the infrastructure requirements for On-Premises API?
→ Businesses must set up and maintain their own servers, manage certificate authorities, and monitor system health.
12. How does message throughput compare to Cloud API?
On-Premises API supports up to 70 messages per second (single-connect) and 250 messages per second (multi-connect).
Cloud API supports up to 500 messages per second (combined sending and receiving).
13. Where can On-Premises API be hosted?
→ It can be hosted in any data center or cloud provider chosen by the business.
Choosing Between Cloud API and On-Premises API
14. How do I decide between Cloud API and On-Premises API?
Choose Cloud API if you prefer minimal maintenance, automatic updates, and higher message throughput.
Choose On-Premises API if you require full control over security, infrastructure, and custom deployments.
15. Does Cloud API have better uptime than On-Premises API?
→ Cloud API targets 99.9% uptime, whereas On-Premises API uptime depends on the business’s infrastructure.
16. Does Cloud API reduce costs compared to On-Premises API?
→ Yes. Cloud API eliminates server setup and maintenance costs, so businesses only pay for messages sent.
17. Can I migrate from On-Premises API to Cloud API?
→ Yes, but you will need to deregister your phone number from On-Premises API before registering it on Cloud API.
Support and Maintenance
18. Who manages updates for Cloud API?
→ Meta automatically handles software updates and security patches for Cloud API.
19. Who is responsible for maintaining On-Premises API?
→ Businesses or BSPs must perform upgrades, security updates, and server monitoring themselves.
20. What support options are available for both APIs?
Cloud API: 24/7 support for critical issues.
On-Premises API: Best-effort 24/7 support for critical issues.