中文(香港) 的翻譯尚未完成。
中文(香港) 更新時間：
Support
Troubleshooting
Message Not Delivered
The following scenarios can cause a message to appear as sent but not delivered. For many of these reasons, we will not disclose the underlying cause of the error, due to privacy and policy reasons.
- The customer did not come online during the 30 day window where we hold messages for offline customers.
- The customer has blocked the business phone number, or another business phone number owned by the business.
- The customer is in a restricted or sanctioned country.
In some scenarios, the API returns an error code with an error message describing the nature of the error. Example scenarios:
- Invalid request parameters
- Integrity errors
- The customer has not accepted our new Terms of Service and Privacy Policy. Please send your end user this link https://wa.me/tos/20210210 to accept the latest Terms of Service.
- The customer is using an old version of WhatsApp. Customers should use the following version or greater:
- Android: 2.21.15.15
- SMBA: 2.21.15.15
- iOS: 2.21.170.4
- SMBI: 2.21.170.4
- KaiOS: 2.2130.10
- Web: 2.2132.6
- The customer is part of an experiment group.
- The message was not delivered to create a high quality user experience. See Per-User Marketing Template Message Limits.
Possible Solutions
Using a non-WhatsApp communication method, ask the WhatsApp user to:
- confirm that they can actually send a message to your WhatsApp business phone number(s)
- confirm that none of your WhatsApp business phone numbers are in their list of blocked numbers (Settings > Privacy > Blocked or Blocked contacts)
- confirm that they have accepted our latest Terms of Service (Settings > Help, or Settings > Application information will prompt them to accept the latest terms/policies if they haven't done so already)
- update to the latest version of the WhatsApp client
Country Restrictions
Businesses in Cuba, Iran, North Korea, Syria, and three sanctioned regions in Ukraine (Crimea, Donetsk, Luhansk) are not eligible to use the WhatsApp Business Platform.
WhatsApp Messenger (WhatsApp) and WhatsApp Business app users in Cuba, Iran, North Korea, Syria, and three sanctioned regions in Ukraine (Crimea, Donetsk, Luhansk) are not eligible to receive messages sent via the WhatsApp Business Platform.
Businesses in Turkey can use the platform, but messages sent via Cloud API to WhatsApp users who have a Turkish country calling code will not be delivered, and messages sent from these users to a business phone number registered for use with Cloud API will not be delivered.
Webhooks
Conflicting Message Delivery Status
In rare cases, the same message may trigger both success and failure message status update webhooks. For example, a message may trigger message webhooks with "status":"delivered" and another webhook with "status":"failed". This can happen when a customer is logged in to WhatsApp on multiple devices and the message is successfully delivered to one device but not the other. Any message that triggers a "delivered" message status webhook has been delivered to at least one of the user's devices.
Error Code 2 - API Service
When we update the API, you may experience up to 5 minutes of downtime. During this period of time, the service is unavailable. We try to make these updates with minimal disruption to businesses, but you may end up being affected
How To Debug
We suggest that you wait 5 minutes and try to make the API call again.
Authentication and Authorization Errors
These errors are returned when there was a problem with the access token you are using for the API call.
How To Debug
You can directly paste the access token you are using into the Access Token Debugger. Then, check if you have selected the whatsapp_business_management and whatsapp_business_messaging permissions.
If your token doesn’t have access to the permissions, you need to generate a new one. While generating the token, make sure to select:
- The Meta app you are using for the API calls
- The following permissions:
whatsapp_business_managementandwhatsapp_business_messaging
FAQs
General FAQs
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.
Technical Implementation FAQs
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.
Reliability FAQs
請參閱我們的 WhatsApp Business API 狀態頁面 ，獲取雲端 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.