• Businesses can reserve and adopt a business username starting June 29, 2026 (previously “later in 2026”).
• Sending messages to a BSUID is supported starting July 2026 (previously listed as May 2026).
• The REQUEST_CONTACT_INFO button is available starting early July 2026 (previously listed as early May 2026).
• Clarified that the text field on a REQUEST_CONTACT_INFO button is optional and the button label cannot be customized, and removed the hardcoded text field from the template creation example.

• Corrected the Terms of Service URL required in the policy.tos field when you create your first signup with the In-App Signup API. The approved URL is https://www.facebook.com/legal/ads-manager-marketing-messages-terms. Create requests that send a different URL fail with error code 2494177 (SIGNUP_TOS_URL_NOT_ALLOWED).
• Updated the template analytics and template group analytics limitations to remove the United Kingdom from the unsupported regions.

• Clarified the Business phone numbers documentation: deleting a business phone number isn’t supported via the API. Use WhatsApp Manager⁠ to delete a business phone number.

• Business verification
• Resolving integrity issues and accessing Business Support Home
• Sending the first message via a partner solution
• Sending business-initiated messages using templates

• Edit messages
• Revoke messages

What Does This Mean for Businesses?

• Updated the unsupported messages webhook by adding details about the actual message type.
• Added new played status messages webhook status value, which indicates when a voice message is played by the Whatsapp user.

• Added two new Automatic Creative Optimization types: product extensions and text formatting optimization.
• Launched a new endpoint to support WABA-level opt-out for automatic creative optimizations.

• Australia
• Japan
• Philippines
• Russia
• South Korea
• Turkey
• European Economic Area (EEA)
• European Union (EU)
• United Kingdom (UK)

• Offsite conversion metrics is now available in WhatsApp Business Manager and in the Template Analytics API.
• Added two new Automatic Creative Optimization features: Headline extraction and Tap-target title extraction.

• Incoming media messages webhooks (image messages, video messages, etc.) now include the incoming media asset’s media URL, which is assigned to the url property.
• You can now designate an audio message as a voice message. Delivered voice messages appear in the WhatsApp client with a play icon, waveform graphic, profile image, and a microphone icon. If the recipient has enabled voice message transcripts⁠, a text transcription of the message can also appear:

• Messaging limits are now business portfolio-based instead of business phone number-based, and the initial increase via scaling path is now 2,000 instead of 1,000. To support this change, for version 24.0 and newer requests, a new whatsapp_business_manager_messaging_limit field has been added, which returns the owning business portfolio’s messaging limit. This field is available on the following endpoints:
  • GET /<BUSINESS_PORTFOLIO_ID>
  • GET /<WHATSAPP_BUSINESS_ACCOUNT_ID>
  • GET /<BUSINESS_PHONE_NUMBER_ID>
• For version 24.0 and newer requests, the messaging_limit_tier on the GET /<BUSINESS_PHONE_NUMBER_ID> endpoint now returns the owning business portfolio’s messaging limit.
• For version 24.0 and newer requests, added error code 131059 which is returned when querying the GET /<WHATSAPP_BUSINESS_ACCOUNT_ID>/message_templates endpoint with an invalid pagination cursor. If you get this error, retry your request without before or after cursors. This will generate and return new cursors for paginated responses.
• For version 24.0 and newer requests, the status messages webhook no longer includes the conversation object, unless the webhook is for a message sent during an open Free Entry Point window.

• Increased marketing message rates for United Arab Emirates.
• Increased utility and authentication message rates for Colombia.
• Decreased marketing message rates for Mexico.
• Decreased utility and authentication message rates for Saudi Arabia, Argentina, and Egypt.
• Zimbabwe is now mapped to our “Rest of Africa” region vs. “Other.” Messages delivered to WhatsApp users with a +263 country calling code (Zimbabwe) will now be charged “Rest of Africa” rates.

Validation for routing model and data model in Flow JSON

• Updated v3 document to display an example of the v3 syntax.
• Added Call Permissions Request type under interactive objects for messages.

• On September 8th, 2025, we’re launching a new “MM Lite ToS signed” webhook, which will be sent whenever a business signs the MM Lite ToS via any method (e.g. Embedded Signup, or in WhatsApp Manager). The webhook will have a more descriptive name than the existing AD_ACCOUNT_LINKED webhook. The older webhook will be deprecated by Jan 1, 2026.
• Conversion metrics will now also be available in WhatsApp Manager UI and via the WhatsApp Business Management API. This means that we’re removing the ability to view MM Lite metrics for read-only Ad Accounts in Ads Manager.
• The /marketing_messages endpoint will accept marketing messages for both MM Lite API and Cloud API.

• Updated references to “Mobile App ID” to “Meta App ID” when creating a template to avoid confusion.
• Added a Template-to-ad-syncing guideline for clients to follow to ensure all templates be set up for conversion metrics.

• Meta Business Suite⁠: Navigate to the Business Settings to view users with Full Control access.
• API: GET /<WHATSAPP_BUSINESS_ACCOUNT_ID> and GET /<BUSINESS_PORTFOLIO_ID>/business_users endpoints to get a list of business portfolio admins.

• Added marketing_messages_onboarding_status field which provides more granular eligibility status data. The field will be a replacement for marketing_messages_api_status field which will be deprecated in version 24.0.
• Fixed the marketing_messages_lite_api_status field to correct a bug which was erroneously returning ELIGIBLE when it should have returned ONBOARDED. This field will be deprecated in version 24.0, so we recommend using the new marketing_onboarding_status field instead.
• Changed the marketing_messages_api_status field to no longer require one or more registered phone numbers, or one or more MM Lite API-ready templates, in order for ONBOARDED to be returned.

Validation for nested expressions in Flow JSON actions

Update to the ChipsSelector component

Image Carousel component

• marketing_messages_read_rate_benchmark
• marketing_messages_click_rate_benchmark

• only_waba_sharing is no longer a valid extras.featureType value, since bypassing the phone number screen is obsolete now that business customers are able to complete the flow with a verified business phone number, unverified number, or no number at all.
• Added extras.version which must be set to 3 to enable version 3.
• Added extras.features for enabling Marketing Messages Lite API and App-Only Install onboarding.
• Added extras.features.api_access_only for enabling App-Only Install onboarding.
• Enabling Marketing Messages Lite API onboarding must now be done through the extras.features instead of extras.featureType.
• Session info will be automatically enabled for all users. Partners will still have to add an event listener on the same window to process incoming information.
• coexistence is no longer a valid extras.featureType value, you must use whatsapp_business_app_onboarding to launch the Whatsapp Business App onboarding flow.
• Measurement partners currently cannot use version 3.
• Pre-filled data will no longer bypass any screens, to provide business customers the opportunity to review and change data.

• 134100
• 134101
• 134102
• 134103

Flows can now be sent with other buttons in message templates

• Self-signup for all partners and businesses. All businesses and solution providers (including Solution Partners, Tech Providers and Tech Partners) can now use self-serve onboarding flows to onboard to MM Lite API. See documentation on Onboarding for more details.
• Global availability. MM Lite API is now available in all regions where Cloud API is also available. Note that while the API is available, some geographic variation of features may apply, see details here.

• Character limits for the body component will vary based on the template format and tag
• The number of emojis allowed in the body component may also be limited.

New property “label-variant” on TextArea and TextInput

Update to on-select-action behaviour

Form validations introduced for init-values and error-messages

• Marketing Messages Lite API
• Conversions API
• Marketing API

• Added GET /<WABA_ID>/template_groups
• Added POST /<WABA_ID>/template_groups
• Added GET /<WABA_ID>/template_group_analytics
• Added GET /<TEMPLATE_GROUP_ID>
• Added POST /<TEMPLATE_GROUP_ID>
• Added DELETE /<TEMPLATE_GROUP_ID>

• Lowered authentication pricing rates for Egypt, Malaysia, Nigeria, Pakistan, Saudi Arabia, South Africa, and the United Arab Emirates.
• Added authentication-international pricing rates for Egypt, Malaysia, Nigeria, Pakistan, Saudi Arabia, South Africa, and the United Arab Emirates.

Chips selector component

Footer supported with RichText component

Published Flow can be created in a single API call

Simplified send Flow API call

Simplified creation of message template with a Flow

• Added ability to migrate business customers off of Multi-Partner Solutions via Embedded Signup and via Meta Business Suite. Both methods skip business phone number re-verification.
• Added app_id parameter to the POST /<WHATSAPP_BUSINESS_ACCOUNT>/set_solution_migration_intent endpoint to allow for migration off of Multi-Partner Solutions.

NavigationList component

Regular expressions supported in TextInput component

Published Flows can be edited from the Builder

API to migrate (copy) Flows from one WABA to another

Endpoint encryption examples in C# & Go

Flow previews can be shared from the Builder

New Flow JSON deprecation webhooks

• Added user preferences for marketing messages.
• Added user_preferences webhook field for user preferences for marketing messages.
• Added error code 131050 for messages webhooks, indicating message non-delivery due user marketing preferences.

1. Call an ‘Intent API’ endpoint to indicate a BMID the partner wishes to assist in migrating to MM Lite. (If a BMID contains any OBO WABAs, these must be migrated to ‘shared’ prior to this event).
2. Admins of that BMID will receive a notification that they have been invited to start sending marketing messages with optimizations via MM Lite. This notification is in Business Manager and via email.
3. Once accepted, and MM Lite setup and Ad account syncing is complete, a webhook will be triggered to the partner and all subscribers indicating that MM Lite onboarding is complete, and including the linked Ad IDs.
4. The partner may now call the “send” endpoint of MM Lite on this business’ behalf, and call an API to fetch an updated token with permission to access the business’ Ad account metrics.

CalendarPicker component

Nested Expressions and string concatenation in component properties

New update_data action

New on-unselect-action property

OptIn and EmbeddedLink can now open external links

Business insights

Published Flows can now be edited

Simplified Flows onboarding

1. Ads Manager UI [recommended]
2. Marketing API “Insights API” [recommended]
3. WhatsApp Manager UI “WABA Insights” page and “Template Insights” page
4. Business Management API
5. Pricing webhooks

• In the Marketing API “Insights API” response, MM Lite events can be return using fields named marketing_messages_[event]
• In the Business Management API “Template Analytics” endpoint, MM Lite events can be returned using the query parameter MARKETING_MESSAGES_LITE_API
• In the Business Management API “Conversation Analytics” endpoints, MM Lite events can be returned using the product_type query parameter `MARKETING_LITE’
• In message status webhooks, the conversation:origin:type and pricing:category fields will show as marketing_lite

• Marketing: From 12 hours to 30 days, for businesses on MM Lite API
• Utility: From 30 seconds to 12 hours, for businesses on Cloud API
• Authentication: From 30 seconds to 15 minutes, for businesses on Cloud API or On-Premises API

• Starting with version 21.0 the package_name and signature_hash parameters must be defined within the supported_apps array when creating one-tap autofill and zero-tap authentication templates.
• Starting with version 21.0, to enable local storage on a business phone number, the number must be in an unregistered state, and you must use the POST /<WHATSAPP_BUSINESS_PHONE_NUMBER>/settings endpoint to enable local storage before registering the number (instead of enabling during registration). To support these changes:
  • Added a storage_configuration parameter to the POST /<WHATSAPP_BUSINESS_PHONE_NUMBER>/settings endpoint, which can be used to enable or disable local storage.
  • Removed the data_localization_region parameter from the POST /<WHATSAPP_BUSINESS_PHONE_NUMBER>/register endpoint.

• Added single-product message templates.
• Added product card carousel templates.

• Added Messages business asset access for more granular control of WhatsApp Business Account access.
• Added ability to create Multi-Partner Solutions via embeddable button.

• All DatePicker components now receive and set dates in “YYYY-MM-DD” format, which makes the values unrelated to time zones (more details).

• You can now check the status of the endpoint of your Flow with this new health check validator, which allows easy troubleshooting of any issues with encryption or health check requests.
• You can find it on the endpoint setup modal within the Flows Builder in WhatsApp Manager.

• A new panel is added to the existing Flows Builder in WhatsApp Manager, which allows viewing the data exchanged between the Flow and the Flow’s endpoint and the data passed between screens when navigating.
• You can find it at the bottom of the editor within the Flows Builder in WhatsApp Manager.

• Added ability to set a custom time-to-live on utility templates.

• Added automatic category updates to correct templates that are miscategorized according to our guidelines.

• v18.0 / Forward: New field endpoint_uri will be returned.
• v17.0 / Backwards: Old field data_channel_uri will be returned.

• Starting June 11th, 2024, WhatsApp Flows will only be supported on Android OS 6.0 and newer versions. This means that businesses will no longer be able to send Flow messages to users with Android OS 5.x.x devices and will receive a webhook containing a “Message Undeliverable” error when trying to do so. For more details on error, please refer to the error codes.
• Additionally, starting from July 9th, 2024, users on Android OS 5.x.x devices will no longer be able to interact with any existing Flow messages.

• Added webook callback URL override on business phone numbers.

• Extend the support of the opt-in component in the Message Templates in Flows UI editor to allow users to add and modify an additional “Read More” screen.
• This feature enables you to display additional information (for example, terms and conditions) on a separate screen instead of cluttering the main Flow screen. This improves the user experience and simplifies the Flow creation process.

• Added the Conversational Components API.

• Adds a new screen for creating flow. The users can now interact with the template before using it for creating a flow.

• New field “UpdatedAt” exposed for the GraphAPI endpoints.
• The field is updated for every flow when name, status, flow json, etc. changes.
• The field is returned with the GraphAPI endpoint and used on the WA Manager -> Flows page.

• Bug fix for Android implementation where ‘form_name’ was unintentionally included in payload. If businesses are using this, then they may need to modify server implementations for a more sustainable setup.

• Changed business phone number registration/deregistration attempt limits to 10 requests per business number in a 72 hour moving window (was a one-week moving window).

• Added per-user marketing template message limits to help deliver high-quality user experiences.

• Introduce a new details page that provides a clear overview of Flow endpoint performance, with data on availability, latency, requests, and errors.
• This page is available for published Flows with endpoint from the Flows Builder in WhatsApp Manager.

• Introduce a new Graph API field in WA Flow object named “metric” which allows businesses to retrieve a set of endpoint related metrics.

• Introduce a new feature in the Flows Builder that allows Flows to be sent directly via WhatsApp Manager. The functionality works only with phone numbers registered to Cloud API.

• Add a new flow JSON template “Book an Appointment” which can be used when creating a flow in Builder. The flow template can be found here.
• Add an endpoint example in NodeJS that works with the “Book an Appointment” flow JSON end to end. The endpoint code is available on GitHub⁠ and Glitch⁠.
• Enhance the endpoint example on GitHub⁠ and Glitch⁠ to include app secret validation, endpoint error codes, script to create public/private keys, and other improvements.

• Changed Cloud API template message delivery retry time-to-live from 24 hours to 30 days. You can still override this value for authentication templates.
• Changed biz_opaque_callback_data character maximum from 256 to 512.

• Added Conversational Components.

• Adds optional property success for terminal screens to indicate whether terminating on that screen results in a successful flow completion.
• Use the new endpoint_uri field instead of the deprecated data_channel_uri.

• Make parameter name optional for Update Flow API request.

• Added location request messages.

• Added cta_url_link_tracking_opted_out field on WhatsApp Message Template node for enabling/disabling button click tracking.
• Template analytics now include button clicks in templates categorized as UTILITY.

• Removes the data_channel_uri property from Flow JSON
• Introduces ability to specify Flow endpoint via API or WhatsApp Manager.

• Adds additional filtering options (by ID and status) on the listing page of Flows
• Adds support for deleting and deprecating Flows
• Adds the ability to clone Flows

• Adds support for attaching images when creating and attaching Forms in Message Templates
• Adds new custom form starter template when creating and attaching Forms in Message Templates

• Introduces new webhook sent at the flow creation.
• Deprecates the data_channel_uri field in the Get Flow API request and replaces it with the endpoint_uri field.

• Added console logging to help with debugging one-tap and zero-tap authentication templates.

• Added health_status field to various nodes for checking messaging health status.
• Added biz_opaque_callback_data field to free-form messages for including arbitrary strings in messages webhooks.

• Carousel template creation now requires at least one button.

• Added zero-tap authentication messages.

• WhatsApp Flows is now available.
• Added new data_localization_region field on WhatsApp Business Phone Number > Register endpoint for enabling local storage.
• Added new click-to-action URL buttons for free-form interactive messages.

• Authentication templates using the code expiration warning now use the code_expiration_minutes value (instead of a default of 10 minutes) to determine if the delivered template message should display an autofill button or copy code button.
• Autofill buttons displayed in a delivered template message will become disabled after the amount of time indicated by the template’s code_expiration_minutes value, if present (or after 10 minutes, if not present).

• Added new limited time offer templates and new limited_time_offer template component.

• Added ctwa_clid property to referral object in messages webhooks. Indicates the click ID generated when the user taps an ad that clicks to WhatsApp in order to send the message.

• Legacy authentication templates (authentication templates without one-time password buttons) can continue to be sent, edited, and appealed until April 1, 204 (extended from October 2, 2023).

• GET request responses on authentication templates now include add_security_recommendation and code_expiration_minutes template components in component value.
• Added new WhatsApp Business Account Access levels for more granular control.
• GET requests on WhatsApp Business Account > Phone Numbers and WhatsApp Business Account > Message Templates now return error code 200 if the user identified by token has not been granted appropriate WhatsApp Business Account Access.
• Added Template Migration.

• Added throughput and platform_type fields to WhatsApp Business Phone Numbers.
• Added Carousel Templates.

• Migrating business phone numbers that have multiconnect running 2 or more shards from On-Premises API to Cloud API automatically upgrades the numbers to higher Cloud API throughput.

• Added template_analytics (in beta).

• Added Cloud API localized storage status to WhatsApp Business API Status⁠ page.

• Added copy code button component for use with coupon code templates.
• Increased template button component total limit to 10, quick reply buttons can now be mixed with other button types, and URL button limit increased to 2.
• Added template bulk management.
• Added template previews for previewing template text in multiple languages.

• Added ability to bypass phone number selection in Embedded Signup.
• Added business phone number programmatic/bulk registration.
• Added pre-verified business phone numbers bulk registration.
• Added pre-verified business phone number sharing.

• Scheduling and performing an upgrade to a business phone number’s throughput no longer requires a live call.
• You can now specify an upgrade time when submitting a Direct Support ticket to request an upgrade to a business phone number’s throughput.
• Downtime for business phone numbers undergoing a throughput upgrade reduced to 5 minutes or less.

• Added identity change check feature.
• Added catalog messages.
• Added catalog templates.

• Attempting to send a paused template in a template message using v17 or later now returns error code 132015 instead of 132001.
• Attempting to send a disabled template in a template message using v17 or later now returns error code 132016 instead of 132001.

• Attempting to send a paused template in a template message now returns error code 2061.
• Attempting to send a disabled template in a template message now returns error code 2062.

• Added Stripe payments (Singapore only).
• Added address messages for requesting customer addresses (Singapore and India only).
• Added 1,000 messages per second throughput.

• Added Stripe payments (Singapore only).
• Added address messages for requesting customer addresses (Singapore and India only).

• Added new webhooks notifying you of denials of messaging limit increases to the account_alerts webhooks field.
• All templates must now be categorized as AUTHENTICATION, MARKETING, or UTILITY.

• Added the following endpoints to support pre-verified business phone numbers for Embedded Signup users:
  • WhatsApp Business Pre-Verified Phone Number
  • WhatsApp Business Pre-Verified Phone Number > Request Code
  • WhatsApp Business Pre-Verified Phone Number > Verify Code
  • Business > Add Phone Numbers
• In Version 2 of the Embedded Signup Flow, you can now retrieve both the phone number and WABA ID you selected by specifying the sessionInfoVersion inside the extras object at the end of the flow.

• The first template category migration is complete.
• Category validation is now part of the template review process for newly created templates. Applies to version v16.0+.
• API responses to template creation or editing requests now include template status and template category. Applies to all API versions.
• Added allow_category_change parameter to POST WhatsApp Business Account > Message Templates endpoint.
• Added INCORRECT_CATEGORY as a new rejection reason value for template status webhooks.
• Templates that rely on variables now require sample values upon creation or editing. Applies to all versions.
• Added previous_category field to WhatsApp Message Templates.
• Business-initiated conversations are no longer eligible for free tier conversations. If your WhatsApp Business Account relies on the services of a Solution Partner or a Meta partner, you are exempt from these changes until June 1, 2023.

• Added a new template_category_update webhook subscription field. If subscribed to this field, anytime a template’s category changes you will receive a webhook indicating the template’s previous and new category.
• API responses to template creation and editing requests now include the template’s status and category.

• Templates created or edited using v16.0 must now be categorized using one of the following categories; all other categories are no longer supported. Applies to Cloud API v16.0+. Will apply to all versions May 1, 2023. This change has been introduced to support our June 1, 2023 switch to a new conversation-based pricing model.
  • AUTHENTICATION
  • MARKETING
  • UTILITY
• Error subcodes, which are rarely used and should not be relied upon, will no longer be included in v16.0+ error responses. Use code and details instead.
• Error code 100 ("code":100) had multiple unique titles which indicated the nature of a given 100 error. All code 100 errors will now use Invalid parameter as their title. Old titles that described the nature of a given code 100 error have been moved to the details property. This change is also now reflected in webhooks payloads that describe a code 100 error response.

• The errors object in webhooks triggered by v16.0+ request errors now include message and error_data.details properties, and title values have changed for multiple error codes. Now, errors objects have the following structure and data:

[
  {
    "code": <CODE>,
    "title" : "<TITLE>",
    "message": "<MESSAGE>",
    "error_data": {
      "details": "<DETAILS>"
    }
  },
  ...
]

• The title property value has been updated for the following error codes. Their old values now appear in error_data.details.
  • 130470 new title is now Re-engagement message
  • 130429 new title is now Rate limit hit
  • 131045 new title is now Incorrect certificate
  • 131031 new title is now Business Account locked
  • 131053 new title is now Media upload error
  • 131027 new title is now Something went wrong
  • 131042 new title is now Business eligibility payment issue
  • 131026 new title is now Message Undeliverable
  • 131000 new title is now Something went wrong
• The message property value is the same as the title property value, which indicates the error code’s title. This property maps to the message property in API error response payloads.
• The error_data.details property now includes error code titles from the error codes listed above and describes the underlying cause of the error. This value maps to the details property in API error response payloads.

• entry.changes.value.errors
• entry.changes.value.messages.errors
• entry.changes.value.statuses.errors

• Cloud API HTTP media caching is out of beta and available to everyone.
• Cloud API will now reattempt to deliver failed webhooks notifications for up to 7 days instead of up to 30 days. See Webhooks Delivery Failure.

• Added a new account_alerts field. Notifies you of Business, WhatsApp Business Account, and business phone number alerts.

• Added a new account_update.events value: ACCOUNT_DELETED. Indicates that a phone number has been de-registered or deleted from a WhatsApp Business Account.
• Added a new message_template_status_update.events value: PENDING_DELETION. Indicates a message template has been marked for deletion.

• ACCOUNT_DELETED : WhatsApp Business Account Deleted
• PENDING_DELETION : Template Message Pending Deletion

• country (applies to v15.0+)
• ownership_type (applies to v15.0+)
• business_verification_status (applies to all versions)

• Filter by WhatsApp Business Account creation_time field using GREATER_THAN, LESS_THAN, or IN_RANGE operators.
• Filter by WhatsApp Business Account ownership_type using EQUAL or IN operators.

• Filter by WhatsApp Business Account creation_time using GREATER_THAN, LESS_THAN, or IN_RANGE operators.
• Filter by WhatsApp Business Account ownership_type using EQUAL or IN operators.
• Filter by WhatsApp Business Account country using EQUAL or IN operators.

• is_official_business_account
• messaging_limit_tier

• Starting in v2.43, there will be changes to the behavior of the contacts endpoint
• Responses for status will change. Regardless of whether a user has WhatsApp, it will always return valid for status in the response and a wa_id. There is no guarantee that the returned wa_id will be valid. These changes are applicable for both direct responses, as well as webhook responses for non-blocking calls
• Ensure your code avoids relying on status and wa_id returned in the contacts node. In addition, sending a message on v2.39.1 or higher can be completed without calling the contacts node
• Ensure your code handles a potential 1013 User is not valid error when trying to send a template message, which will be returned if you attempt to send the template message to a phone number without a WhatsApp account
• For non template messages, sending a message to a phone number without a WhatsApp account will return a 470 error

• Starting in v2.45, the optional cert parameter in the shards node will become mandatory for all requests. Please update your integration to always include a valid cert when calling the shards node
• Starting in v2.41.2, businesses can use the application node to filter out sent message statuses they are not interested in through the message object within the webhooks object. In v2.45, sent_status will be deprecated, so update your integration to use the webhooks object in the application node for all webhook controls
• As of v2.39.1, recipient_id is available in both the statuses object and in the message object. In v2.45, recipient_id will be removed in the statuses object, so update your integration to use recipient_id under the message object

• You can now use different callback URLs for each of your WhatsApp Business Accounts without having to create a unique app for each WhatsApp Business Account. See Overriding the Callback URL for details.
• All Cloud API endpoints now support version 15 calls.
• Text parameters (components.parameters.text) for message templates that only use a body component (components.type:body) can now total up to 32,768 characters. See Parameters object.
• Cloud API now supports up to 350 (up from 250) messages per second (mps) of combined text and media messages, by request. See Throughput for details. If you already have 250 mps it will be increased to 350 mps automatically. If you already requested 250 mps but the process has not been completed, you will receive 350 mps upon completion.

• Reactions are now supported. See Send Messages - Reaction Messages to learn how to send and receive reactions and Payload Examples - Reaction Messages for webhook payload notification examples.
• The about field on business profiles is now supported. See Business Profiles for details.

• You can now include animated stickers in outbound, business-initiated messages and receive message webhooks describing those messages the same way you would if you were sending a non-animated sticker. Refer to the Message object’s sticker property and for animated sticker asset requirements.
• You can now include products and services in messages sent to customers, and customers can add them to shopping carts without having to leave the chat thread. Refer to the Share Products guide to learn how to send Single and Multi-Product messages to customers.

• Businesses can now reply to any message in a conversation thread. Replies will include a contextual bubble referencing the replied-to message. Refer to the Send Messages guide to learn how to reply to a message.
• Cloud API now supports up to 250 messages per second of combined sending and receiving (inclusive of text and media messages), by request. If you are an enterprise partner you can open a Direct Support⁠ ticket to request 250 MPS throughput by selecting Question Topic: “Cloud API Issues”, Request Type: “Request to migrate to 250 MPS throughput” and filling out the required information.

• Run garbage collection via the /services/message/gc endpoint before your upgrade, and ensure it completes successfully
• Please use the dbupgrade tool to upgrade the DB schemas prior to the version upgrade.

• Improvements to the latency of the bulk /contacts endpoint requests and resolution of deadlock issues.
• Improvements to the performance and reliability of the garbage collection process.
• Businesses now have the ability to enable/disable delivered and read webhook notifications which gives them greater control over webhook notifications for messages. This can be achieved through the settings/applications endpoint.
• namespace field is optional for the template object.
• More robust handling of media download errors so businesses should experience less issues downloading media sent by customers.
• Additional reliability and bug fixes within the send message and registration workflows.

• TRANSACTIONAL
• MARKETING

• Fixes a bug that prevented video messages from being sent under certain circumstances. This fix was also included in v2.39.2.
• Fixes a bug that prevented businesses from sending messages to a customer, if the customer was the first to initiate an interaction between the two parties on WhatsApp, and that initiation happened more than 7 days ago. This fix was also included in v2.39.3.
• Fixes a bug that prevented businesses from receiving disappearing messages from customers. After v2.39.4 is 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.

• Enterprise: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent.yml?versionId=0pACuWHFUL7U1RjxGcTkAsza7rj._5tK
• DB: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent_db.yml?versionId=4BtYzof0_z0yl7Pbat9mln8Xj5CYS07Z
• Lambda: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent_lambda.yml?versionId=o1JUcpuOHKfTU_hRExFxhib5YCeXeZx.
• Network: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent_net.yml?versionId=_D2yaFcS1zEqRLf23t2Wesnh3M.Qw1UF
• Monitoring: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent_monitoring.yml?versionId=H534ejFNiHnMpWyy1ERh3kr9TvM5VtyS

• Updating AMIs for CentOS 7 machines

• Fixed an issue related to disappearing messages from users.
• Better determination of thumbnail quality for media messages.

• Enterprise: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent.yml?versionId=bNECfwPYZZNGlhzkfCyheoQugydIiui4
• DB: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent_db.yml?versionId=RRa0vGtuodHnWNyww8uLyZUAWFOfQ7hN
• Lambda: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent_lambda.yml?versionId=Sp2BO2LgxkVWH2XTxZ6pgOx3yf1xEqUQ
• Network: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent_net.yml?versionId=uNubDzGLs1WddCGB0EgEa6OMSF1vw4Mn
• Monitoring: https://wa-biz-cfn.s3-us-west-2.amazonaws.com/wa_ent_monitoring.yml?versionId=HyC5PA5IZy9d.CFDkNTGDBEyxSHf5gHI

• Moved from using pip to pip3 to install AWS bootstrap scripts.
• Fixed an issue with awscli installation.

• Respond to unlimited customer-initiated conversations.
• Send business-initiated conversations to 50 unique customers in a rolling 24-hour period.

• WhatsApp Account checks and display name review will no longer be a requirement to get started on the platform. After signup, a compliance check with the WhatsApp Platform Policy Checks will be auto-triggered and will be performed in the background.
• Display name review will be initiated after Business Verification is completed. Businesses should still follow the display name best practice guidelines when adding a new phone number. For more information, see Display Names.
• Business Verification only needs to be completed when businesses are ready to scale business-initiated conversations or request to become an Official Business Account (OBA). For more information, see how to increase limits.
• Since businesses get access to sending messages after sign up, the Unverified Trial Experience will be deprecated.
• Businesses will be able to see the messaging limits in the Overview Dashboard in WhatsApp Manager -after completing the signup process.

• Messages with Stickers: Send media messages containing third-party static stickers. See the following documentation for more details: Reference, Messages and Reference, Media. We support inbound both and outbound stickers. For outbound, we only support static third-party stickers. For inbound, we support all types of stickers.
• Deregister Phone Number API: Make POST calls to PHONE_NUMBER_ID/deregister in order to remove a phone number from the WhatsApp Business API. See Registration for information.
• New Phone Verification Option: Verify your business phone number via Graph API calls. See Phone Numbers for information.
• New Referral Webhooks: Receive Webhooks notifications when a user clicks on an ad that clicks to WhatsApp and sends a message to the business. See Webhooks for information. Be aware that the Cloud API’s webhooks referral object is different from the On-Premises API’s referral object.

• Fixed a bug that prevented businesses from sending messages to a customer, if the customer was the first to initiate an interaction between the two parties on WhatsApp, and that initiation happened more than 7 days ago.
• Fixed a bug that prevented businesses from receiving disappearing messages from customers. After v2.39.3 is installed, businesses will get notified they received a disappearing message by a webhooks notification. On their end, customers will see a warning saying that the disappearing messages mode has been turned off.

• Reference, Messages
• Webhooks: List Messages and Reply Button
• Webhooks, Components

• Reference, Messages

• Migrate Between On-Premises and Cloud API

• A bug exists that prevents businesses from sending messages to a customer, if the customer was the first to initiate an interaction between the two parties on WhatsApp, and that initiation happened more than 7 days ago.
• A bug exists that prevents businesses from receiving disappearing messages from customers.

• Media, Upload Media
• Supported Media Types
• Messages, Examples, Media Messages
• Webhooks, Components

• Starting today, Cloud API beta users can start sending and receiving location and contact messages. See the documentation below for more information:
  • Reference, Messages: Location and Contacts
  • Webhooks, Examples: Received Messages
• 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.

• New field for the Set Shards API.
• New hostname added to network requirements.
• New error code 1031.
• Deprecations of the hsm type and the webhook_payload_conversation_pricingmodel_disabled application setting.

• Messages API: The hsm type has been deprecated with v2.39. You should use the template type instead.
• Application Setting: The application setting webhook_payload_conversation_pricingmodel_disabled has been deprecated.

• Text Messages
• Text-Based Message Templates
• Media Messages (Images and Documents)
• Media-Based Message Templates (Images and Documents)
• Interactive Message Templates

• Media Messages (Audio and Video)
• Media-Based Message Templates (Audio and Video)
• Contact Messages
• Location Messages
• Stickers and Stickerpacks
• List Messages
• Dynamic Reply Buttons
• Multi-Product Messages

• /PHONE_NUMBER_ID/deregister
• /PHONE_NUMBER_ID/application_settings