支持

We expect Cloud API to provide the same key features as the On-Premises API soon, including user change notifications and sticker pack management. Our goal is for the Cloud API to become the preferred platform for new features.

We will release updates monthly with new features and improvements. There is no work required to access these features - the Cloud API updates automatically.

WhatsApp develops and operates the WhatsApp Business API, which enables businesses to communicate with WhatsApp consumer users on the WhatsApp network. When using the Cloud API, Meta will host the WhatsApp Business API for you and provide an endpoint for the WhatsApp service for your incoming and outgoing WhatsApp communications.

No, we will continue to provide the On-Premises API for now. See On-Premises API for information.

No, there is no difference in messaging prices between the Cloud API and the On-Premises API. Access to Cloud API is free, and we expect it to generate additional cost savings for developers. The two types of cost savings for the Cloud API are 1) set up cost (including server or external cloud provider cost), 2) ongoing cost of maintenance (including engineering time for API upgrades).

A Solution Partner can select which setup a given client should use. We recommend that the majority of clients use the Cloud API for ease of implementation and maintenance. Solution Partners can also continue to maintain integration with the On-Premises API.

We want to make it clear what it means to message with a business on WhatsApp. Some businesses may choose to use Meta or another company to help them manage and store their messages. When a business chooses to manage their messages with another company, we will let consumers know by showing a different system message. Learn more.

The Cloud API architecture significantly simplifies the Solution Partner's operational and infrastructure requirements to integrate with WhatsApp Business Platform. First, it removes the infrastructure requirements to run Business API docker containers (CAPEX savings). Second, it obviates the need of operational responsibilities to manage the deployment (OPEX savings). For details, refer to the architecture diagram comparing the On-Premises and Cloud API deployments.

Solution Partners and direct clients do not need the WebApp and CoreApp containers that are used in the On-Premises API. Meta will manage all database data and media data on behalf of the Solution Partner or direct client.

As your on-premises performance depends heavily on your hardware, software, and connectivity to WhatsApp servers, if you wish to understand these differences, you can perform your own load tests on Cloud API as you might have done for your own on-premises installation. You can also refer to our performance comparison to understand more details around how the on-premise and Cloud APIs compare.

Migrating between the on-premises and Cloud APIs is seamless, and can be done bidirectionally. See migration details for more information.

请查看我们的 “WhatsApp Business API 状态”页面 ，获取云端 API 的具体可观测性指标。

详情请参阅 API 状态页面 。

库存每天更新一次。

在某些情况下，某些用户错误可能会被自动错误计入非正常运行时间。在这些情况下，在经过一周时间内的详细分析之后，我们会覆盖非正常运行时间，将其计入正常运行时间。

可能存在一些不影响我们全球可用性的问题。在这种情况下，WhatsApp Business API 状态页面将显示一个状态，反映可能存在一些不影响全球可用性的干扰。请提交 站内支持 工单，以便开展深入调查。

在以下情况下，系统不会自动追踪可用性当中的非正常运行时间：

• 存在网络问题，导致请求在到达图谱 API 层（第一层）之前失败。
• 存在网络问题，导致出站 Webhooks 无法到达企业的 Webhooks 端点。

进入系统之前出现的任何问题，在此之后，此类问题将显示为错误或与成功失之交臂。还有在首次尝试发出 Webhooks 后遇到的问题，但系统会继续尝试发出，直至成功送达 Webhooks 端点。

在进行人工检测后，可用性面板中反映的其他情况包括（非系统错误）：

• 确定了 Meta 身份验证问题，如身份验证口令（安全库）问题，无论是合格请求未能验证身份还是未能进行授权。
• 拒绝合法请求的验证。

在这两种情况下，WhatsApp 将在事后近乎实时（并非实时）地检测并解释这些问题。

针对正常运行时间和/或延迟时间，我们目前不提供商用产品服务水平协议。

We will have disaster recovery and data replication across multiple regions. The expected downtime would be within our SLA and usually in the order of less than a minute to less than five minutes.