This changelog covers what has changed in the WhatsApp Business Platform.
|Cloud API Changes||On-Premises API Changes||Changes Affecting All APIs|
Cloud API users don’t need to perform any software upgrades to use the new features announced in this changelog. Cloud developers may need to update their application’s code to use the new features.
Starting today, the WhatsApp Business Cloud API is open to all developers building products or services for themselves or their organizations. To get started, see our guide. If you are interested in offering API access to your customers, please join our waitlist.
This client version contains all features and fixes shipped with
v2.39.1. Additionally, this release:
v2.39.4is installed, businesses will get notified they received a disappearing message by a webhooks notification with type set to
"ephemeral". Businesses will not be able to see the message's content.
When we launched
v2.39.3, the disappearing messages issue was handled by WhatsApp automatically disabling these messages in the chat thread with the client. For
v2.39.4, we will not do that. With this version, businesses that receive disappearing messages must ask the customer to disable disappearing messages and resend their latest message.
Starting today, the Cloud API includes the following upgrades:
We’re making it easier for businesses and partners to scale on the WhatsApp Business Platform with an improved onboarding experience. Starting May 2, 2022, businesses will be able to message customers immediately after signup and only need to complete Business Verification when they’re ready to scale business-initiated conversations or request to become an Official Business Account.
The changes mean that onboarded businesses will be able to:
These are the changes being implemented on May 2, 2022:
The changes listed above have no impact on pricing. See pricing for more details.
Starting today, the Cloud API is generally available to all existing Business Solution Providers (BSPs) and direct clients. Additionally, we’re releasing the following features for Cloud API developers:
PHONE_NUMBER_ID/deregisterin order to remove a phone number from the WhatsApp Business API. See Registration for information.
referralobject is different from the On-Premises API's
Additionally, we are announcing that App Review is no longer required for first-party developers using the Cloud API. All developers are subject to the WhatsApp Business Platform messaging limits.
This version contains the same features as
v2.37.1, but there's a different expiration date.
v2.37.2 expires on Sep 22, 2022.
Some Kubernetes developers may see
CrashLoopBackOff for their webapp container and their container may fail to start. To fix that, add following line in the Kubernetes deployment
YML file under webapp configuration:
command: ["/opt/whatsapp/bin/wait_on_mysql.sh", "/opt/whatsapp/bin/launch_within_docker.sh"]
v2.39.3 version of our Business API client is available for developers today. The new client includes two fixes and additional logs to support debugging. The two fixes are:
Starting today, Cloud API beta users can start sending and list and reply button messages. See the following documentation for more details:
Starting today, Cloud API beta users can add a preview URL box to text messages that include a URL. See the following documentation for more details:
We just released the On-Premises API
v2.39.2. This version fixes a bug that prevented video messages from being sent under certain circumstances.
Starting today, WhatsApp has switched from a notification-based pricing model to a conversation-based pricing model. Businesses are charged per conversation, which includes all messages delivered in a 24 hour session. See Conversation-Based Pricing for information.
Starting today, Cloud API beta users can start sending and receiving location and contact messages. See the documentation below for more information:
We now support 80 messages per second peak throughput per phone number. This includes incoming and outgoing messages, as well as text, template and media messages.
2.39.1 version of our Business API client is available for developers starting today. The new client includes:
hsmtype and the
Starting with the new API client version, you may provide your phone’s certificate when you are setting up multiconnect. That means that, when calling the /v1/account/shards endpoint, you can add the Base64-encoded certificate in the cert field. See Scale Your API Client With Multiconnect for information.
We have added
graph.whatsapp.com to the list of WhatsApp server hostnames that the Business API client requires connectivity to. See Set Up and Debug Your Network, Hostnames for information.
v2.39, we have added error code
1031. You will get this error if your account has been locked and can’t send any messages due to an integrity policy violation. See Error and Status Messages and Policy Enforcement for information.
hsmtype has been deprecated with
v2.39. You should use the
webhook_payload_conversation_pricingmodel_disabledhas been deprecated.
Some video messages fail to send under certain circumstances.