支援

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.

Please view information about the sunset of the On-Premises API.

Access to Cloud API is free, and we expect it to generate additional cost savings for developers, as Meta hosts and maintains the Cloud 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 狀態頁面將顯示一個狀態，反映可能存在一些不影響全球可用性的干擾。請提交 直接支援（服務） 案件，以便我們深入調查。

在某些情況下，系統或許未能自動追蹤停機時間而判斷為有服務：

• 網絡問題，導致要求在到達 Graph 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.