WhatsApp Cloud API
Overview
Readme
Cloud API Overview
Message Throughput
Rate Limits
Available Metrics
Scaling
Data Privacy & Security
Get Started
Readme
Step 1: Set up Developer Assets and Platform Access
Step 2: Send a Test Message
Step 3: Configure a Webhook
Step 4: Receive a Test Message
Next Steps
Get Started for BSPs
Prepare and Plan
Set up Assets
Sign Contracts
Build Integration
Step 1: Get System User Access Token
Step 2: Set up Webhooks
Step 3: Subscribe to your WABA
POST
Step 4: Get Phone Number ID
GET
Step 5: Register Phone Number
POST
Step 6: Receive a Message from Consumer App
VIEW
Step 7: Send a Test Message
POST
Guides
Readme
Mark Messages as Read
Sell Products and Services
API Reference
Readme
Account Migration
Block Users
Business Compliance
Business Profiles
Registration
Media
Messages
Phone Numbers
Two-Step Verification
WhatsApp Business Accounts (WABAs)
WABA Subscriptions
Payments API - SG
Payments API - IN
Typing indicators
Examples
Send Sample Issue Resolution Template
POST
Webhooks
Readme
Understanding Webhooks
Generate Endpoint for Webhook Testing
Components
Message Status Types
Status: Transaction Status - Order Details Message
VIEW
Support and Troubleshooting
Support
Errors
Technical Implementation FAQs
Data Privacy & Security FAQs
Regulatory Compliance FAQs
Prepare and Plan
创建时间: 2025-05-28 16:39

Read Documentation

Before you start, we recommend reading through our developer documentation and our Postman collection. This helps you understand how the Cloud API works, including how to get started and migrate numbers.

Plan Onboarding & Migration

You must use Embedded Signup to onboard new customers to the Cloud API. If you haven’t already, integrate and launch Embedded Signup. Embedded Signup is the fastest and easiest way to register customers, enabling them to start sending messages in less than five minutes.

Next, think about which clients you want to migrate to the Cloud API first. Our general recommendation is to migrate all of your clients from the On-Premises to the Cloud API, but each client’s need may vary. As you think about which clients to migrate, consider:

ConsiderationMore Context

Are my client’s throughputs and message volumes supported by Cloud API?


The Cloud API supports most businesses at 80 messages/second cumulative peak throughput, including text/media and ingoing/outgoing.


Are my client’s compliance needs met by the Cloud API?

The Cloud API is GDPR compliant and has SOC 2 certification. Servers are hosted in North America.


Are my clients using features supported by the Cloud API?


Most major features are supported. See full list here.

Once you know who’s going to be migrated, you can build a migration plan and timeline.

As you create your plan, remember to design your system for two scenarios: onboarding new customers and migrating current customers from On-Premises to Cloud API. For the migration scenario, include plans to backup your current On-Premises instance and migrate those numbers to the Cloud API.

Plan Communication With Clients

First, you need to decide whether to notify existing clients about migration. Then, you should determine if you need to create or update any documentation to support the Cloud API setup.

Make Pricing Decisions

Since the hosting costs for the Cloud API are covered by Meta, you should decide if you would like to update your prices accordingly.

最后更新: -