Cloud API, Embedded Signup

WhatsApp Business app phone numbers from Nigeria and South Africa are now supported when onboarding WhatsApp Business app users via Embedded Signup.

Cloud API, Embedded Signup

WhatsApp Business app phone numbers from Nigeria and South Africa are now supported when onboarding WhatsApp Business app users via Embedded Signup.

Cloud API, Webhooks

The account_update webhook’s PARTNER_REMOVED event now includes a disconnection_info object when your client was using both the WhatsApp Business app and Cloud API and the disconnection was due to a business downgrade or device inactivity. The object contains a reason field (BUSINESS_DOWNGRADE, PRIMARY_INACTIVITY, or COMPANION_INACTIVITY) and an initiated_by field (USER or SYSTEM). This feature is part of a gradual rollout and may not be available to you immediately.

Cloud API, Pricing

Updated per-message rate cards with rate changes for Saudi Arabia, India, Pakistan, and Turkey. Introduced 8 new billing currencies for both messaging and calling: AED, ARS, CLP, COP, MYR, PEN, SAR, and SGD.

Cloud API, Conversational Components

Removed the request_welcome webhook and welcome message feature from conversational components. This feature is no longer supported. The enable_welcome_message parameter has been removed from the Conversational Automation API.

Cloud API, Marketing Messages API for WhatsApp, Pricing

Added upcoming rates for 2026 for the following countries:

Argentina (ARS), Australia (AUD), Chile (CLP), Colombia (COP), Euro (EUR), India (INR), Indonesia (IDR), Malaysia (MYR), Mexico (MXN), Peru (PEN), Saudi Arabia (SAR), Singapore (SGD), United Arab Emirates (AED), United Kingdom (GBP), United States (USD).

Added a new Automatic Creative Optimization type: Auto promotion tag.

Added new unsupported message types in the unsupported messages webhook.

Added account_offboarded and account_reconnected webhooks for Coexistence.

Cloud API Groups are now available to all businesses with an Official Business Account.

Multi-solution conversations are now available for Marketing Messages API for WhatsApp.

Added new pricing policy for AI Providers.

Effective February 16, 2026, in countries where Meta is legally required to support AI Providers, Meta will charge AI Providers for non-template messages sent to WhatsApp users.

Added business portfolio pacing, a new template message delivery batching mechanism that allows time to gather feedback on any template sent as part of a large-scale messaging campaign.

Businesses that use Marketing Messages API for WhatsApp can now view metrics for quick replies.

Coupon code templates now support codes with up to 20 characters, instead of 15.

Added No Storage, an alternative Local Storage configuration. With No Storage, in-transit data is kept for a shorter period of time, and at-rest data is not persisted.

Added a note in embedded signup indicating users may experience a new completion flow for all versions. A new View your setup guide button will take users to a new setup guidance page in the WhatsApp Manager, which will provide next steps on:

The following messages event webhooks are now supported for Coexistence in Embedded Signup:

Marketing Messages API for WhatsApp (formerly known as Marketing Messages Lite API) is now generally available.

Updated the unsupported message webhookby adding details about the actual message type.

Added new played status message webhook which indicates when a voice messge is played by the Whatsapp user.

The following countries/regions are now supported for Coexistence in Embedded Signup:

Ad click IDs will not be included in incoming text messages webhooks payloads describing an incoming message that originated from a WhatsApp Status ad placements⁠.

Added marketing_messages_onboarding_status and owner_business_info fields to check Terms of Service and Intent request status for business manager.

If you don’t want to configure and host the Embedded Signup implementation code on your website or customer portal, you can now use Hosted Embedded Signup (“Hosted ES”) instead.

Hosted ES is a pre-configured implementation of Embedded Signup that is hosted by Meta. You can get a link to Hosted ES in the App Dashboard and add it to your website or customer portal. Business customers who click the link will be presented with a webpage with a “Get started” button that launches the Embedded Signup flow:

The product_policy field is now 100% rolled out for businesses customers.

Embedded Signup version 4 is now available. Version 4 provides a simplified onboarding experience and allows you to onboard business customers to multiple products (WhatsApp Cloud API, Marketing Messages Lite API, Ads that click-to-WhatsApp⁠ and the Conversions API).

Embedded Signup version 4 is now available. Version 4 provides a simplified onboarding experience and allows you to onboard business customers to multiple products (WhatsApp Cloud API, Marketing Messages Lite API, Ads that click-to-WhatsApp and the Conversions API). For more information, see the versions and v4 page.

Updated the onboarding page with an onboarding video tutorial.

Introducing WhatsApp Groups API, which enables programmatic creation and management of groups on WhatsApp.

Access verification is no longer required to become a Tech Provider.

Changed WhatsApp Business Platform rates.

Updated the support page with new troubleshooting guides.

Added a Coexistence onboarding guide to MM Lite. Whatsapp Business users can now onboard with their existing WhatsApp Business app account and phone number.

Added note in the media document when retrieving a media from a media ID received via webhook, the media ID will only be available to download for 30 days. After October 9th this will only be available for 7 days.

Updated v3 document to display an example of the v3 syntax.

Added Call Permissions Request type under interactive objects for messages.

Added a features page comparing MM Lite and Cloud API features.

MM Lite API uptime and availability metrics are now live on metastatus.com⁠, providing visibility into service status.

In September we are simplifying the Embedded Signup flow across all versions. You can preview the simplified flow by configuring Embedded Signup with v#-public-preview (e.g. v3-public-preview) and launching the flow. See Versions for additional details.

Added AD_ACCOUNT_LINKED event to the account_update webhook, which triggers when a WABA has onboarded to MM LITE through Embedded Signup or Intent API giving the partner access to its ad accounts.

Added Welcome Message Sequences, which allow you to populate a set of pre-defined text and FAQs or a prefilled message, that can appear in a WhatsApp thread when a user taps a Click-to-WhatsApp ad.

Added a image background generation field for automatic creative optimization.

Added new whatsapp_business_manage_events permission to log events.

Changed the Media Card Carousel Template requirements so that card body text is no longer mandatory.

Added the Tap target title URL override message template.

Local Storage is now available for MM Lite. If you have already enabled Local Storage for the Cloud API, your existing settings are automatically applied to the MM Lite API.

Added a troubleshooting guide on how to identify admins of a business portfolio using Meta Business Suite or the API. Both methods return the same results.

WhatsApp Business Calling API now available.

Multi-solution Conversations enables businesses to use multiple partners and solutions on the same phone number, enabling a seamless chat thread experience for their customers.

Added PROFILE_PICTURE_LOST as a new alert_type to account_alerts webhooks, to notify you when a business phone number’s business profile photo has been deleted.

Per-message pricing now applies to MM Lite API! See Pricing on the WhatsApp Business Platform to learn more.

Per-message pricing is now live.

The ads_read permission is now optional for partners. This change impacts the Intent API and the Embedded Signup onboarding flows. Prior to this change, partners had to apply for App Review to get advanced access for this new permission, regardless of whether or not their app intended to call the Insights API for conversion metrics. Now, partners only need to request advanced access for this permission via App Review if their app intends to use the Insights API.

Added text overlays and image animation Automatic Creative Optimizations. Like other optimizations, these are enabled by default on all templates, but can be disabled upon template creation, or when editing a template.

Businesses in Russia who were previously unable to send messages via MM Lite API can now do so. Note that these businesses will not have access to some advanced features, but can still take advantage of all other benefits, such as exclusive marketing features. For more details, see Geographic availability of features.

Solution Partners can now claim sandbox accounts.

You can now request Official Business Account status via API and edit your display name via API. Before you could only do this using WhatsApp Manager.

Added two new Insights API fields so you can get read rate and click rate benchmarks via API instead of only via WhatsApp Manager:

Embedded Signup now gives business customers the option to have us automatically identify purchase or lead gen events in message threads that originate from ads that click to WhatsApp.

To be notified of these events, you can subscribe to the new new automatic_events webhook, and optionally, report them via Conversions API. See Automatic Events API for more details.

A phone_number_quality_update webhook with event set to THROUGHPUT_UPGRADE and current_limit set to TIER_UNLIMITED will now be triggered if your business phone number is upgraded to higher throughput.

Added error code 132018 for help diagnosing invalid parameters when attempting to send a template message. Applies to version 23.0 and newer versions.

Version 3 is now available. As part of this release, we have introduced versioning that will align with Graph API’s release cadence. The following changes apply to version 3:

Added Android deep link support.

Added an Error messages section to WhatsApp Manager that shows a summary of errors encountered by your templates within a given period of time.

Added new error codes to help diagnose messaging errors. These will be available with Graph API version 23.0.

Solution providers can now onboard WhatsApp Business app users who have a WhatsApp Business app phone number with an India country dialing code.

We are offering a limited roll-out of webhook access to click events on marketing messages sent using MM Lite. Read the “Tracking click events” page for more information

We are piloting a new optimization capability exclusive to MM Lite API (not available on Cloud API), which automatically enhances the visual appeal and engagement of marketing messages. Similarly to Advantage+ creative, this capability tests minor variations of your existing image header with different crop orientations or color filters, and automatically selects the variant which is getting the highest click-through rate over time with no input needed from you.

A small group of businesses will be getting early access to this feature starting May 5, with the ability to opt Templates out via the message template API. For more details, see Automated Creative Optimizations.

Please reach out to your partner, if you would like to be included in early access to this feature.

We no longer support the allow_category_change property during template creation. Previously, if set to true in a template creation request, this allowed us to update a template’s category to marketing, if we determined marketing to be its category per its content and our guidelines. This is now the default behavior.

Added typing indicators so you can let WhatsApp users know that you are preparing a response.

Added ability to create and share WhatsApp Business Accounts using WhatsApp Manager.

With this update, MM lite has:

Lowered authentication-international pricing rates for Egypt, Nigeria, Pakistan, and South Africa.

Payments API for business portfolios with Singapore addresses is no longer available.

This update applies across all Templates on the Business Messaging API, and is not specific to MM Lite API (also applies on Cloud API).

As part of our ongoing efforts to improve the performance and user experience of our messaging platform, we are introducing changes to the body component of marketing templates via Cloud API and MM Lite API. These changes will impact the character limits and emoji usage in the body component, depending on the format and tag of the template.

Key Updates:

These updates are designed to enhance the performance and user experience of our messaging platform. While these changes may require some adjustments to your template creation process, they can ultimately lead to better performance and engagement with your customers.

Added partner-initiated WABA creation to replace the On-Behalf-Of (“OBO”) account ownership model, which is being deprecated. Starting September 30, 2025, WABAs can no longer be onboarded to the OBO model.

Added additional tiles to the App Dashboard > WhatsApp > Quickstart panel to make it easier for you to get started with complementary products that can help you scale business messaging:

These tiles make it easier to find documentation for these products and automatically add required permissions to an App Review request, which you can review and submit at your convenience.

Note that these tiles only appear for products that you are eligible to use.

Added new endpoints to support template groups and template group analytics, which allows you group sets of templates for easier analytic analysis.

Added ability for solution providers to onboard WhatsApp Business app users via Embedded Signup (aka “Coexistence”).

Added ability for business customers of solution providers to claim “555” business phone numbers when onboarding via Embedded Signup.

Added the Block API giving businesses the ability to manage unwanted spam by blocking or unblocking specific customer phone numbers.

Added Sandbox accounts for easier testing of the Embedded Signup flow.

Businesses in the USA are now eligible to use the MM Lite API.

In addition, a new MM Lite enrolment parameter allows businesses and partners to programmatically check MM Lite eligibility. See API docs for details.

Businesses in the USA are now eligible to use the MM Lite API.

In addition, a new MM Lite enrolment parameter allows businesses and partners to programmatically check MM Lite eligibility. See API docs for details.

MM Lite team has quickly responded to feedback on “async” or “delivery” latency. This is defined as the time between an API call being received by MM Lite API, and MM Lite API dispatching a “delivered” webhook, assuming a user is online when the message is sent.

MM Lite previously had a p99 “async” delivery time of 12s, vs. p99 of 5s on Cloud API. This time has now been reduced to 9s. No action is required on a business or partner’s part.

MM Lite is rolling out a new way for partners to guide a business through signing the MM Lite Terms of Service and moving to MM Lite.

In parallel with the Embedded Signup flow already available, a partner will also alternatively be able to initiate the following flow:

See API docs for details on this new onboarding flow.

Added GET /<SOLUTION_ID>/access_token endpoint for getting business tokens of business customers who have onboarded to the platform via a Multi-Partner Solution.

Added POST /<WHATSAPP_BUSINESS_ACCOUNT>/set_solution_migration_intent endpoint to enable Tech Providers to migrate business customers from one Solution Partner and Multi-Partner Solution to another Solution Partner and Multi-Partner Solution.

Businesses can now use MM Lite API to measure when marketing messages lead users to perform app events, such as purchases, searches, or achieving levels in games. See Integrate with App Conversions for details.

Added POST /<BUSINESS_PORTFOLIO_ID>/self_certify_whatsapp_business endpoint for partner-led business verifiation.

Service conversations are now free for all businesses, including via AI-enabled conversational experiences.

To represent this new conversation type, MM Lite API conversations are available in every surface where reporting is offered:

For full details on how to see MM Lite API metrics via API and in pricing webhooks, consult the MM Lite API docs.

Businesses can now see MM Lite metrics as “Marketing - lite” in the WhatsApp Manager UI:

We recommend you integrate with the Marketing API “Insights API” for MM Lite Metrics, and encourage end businesses to log into Ads Manager UI to see their metrics, instead of using the WhatsApp business surface. Ads Mgr UI and Insights API show conversion metrics that are not available on WhatsApp surfaces, and will continue to support new metrics and features as the primary surface for MM Lite API reporting as the API grows.

API docs for partners have been updated to reflect how to fetch MM Lite metrics via API.

API docs have been updated to reflect how to fetch MM Lite metrics via API, see Viewing metrics.

We continue to invest to improve consumer experiences and business outcomes. We are introducing customizable message validity periods (time-to-live or TTL) for marketing messages on MM Lite API, to ensure marketing messages are always timely and relevant for users thus performant for businesses. We are also updating our customizable range for TTL for utility and authentication templates, to provide businesses more control and flexibility.

Businesses can customize the TTL of marketing, utility and authentication templates during template creation via WhatsApp Manager (via pre-set increments) and via API (in 1-second increments). This is reflected in our dev docs and Business Help Center⁠.

Marketing message conversations initiated via MM Lite API are counted and billed separately from Marketing message conversations initiated via Cloud API. This includes updates to pricing webhooks. For details, please see Pricing.

Added POST /<WHATSAPP_BUSINESS_ACCOUNT_ID>/set_solution_migration_intent endpoint for adding a WABA to an active multi-partner solution.

Updated pricing rates in India, Saudi Arabia, the United Arab Emirates, and the United Kingdom.

Changed steps in the App Dashboard to make it easier to become a Tech Provider.

Added checkout button templates (only available to India businesses that use business phone numbers with India country calling codes).

Changed media asset caching behavior from developer definable (via Cache-Control header) to a fixed time period of 10 minutes. You can still force us to fetch assets from your server instead of our cache, however. See Media Caching.

Lowered utility conversation pricing rates.

MM Lite metrics are now available from the Template Analytics API endpoint. See documentation for details.

Cloud API, On-Premises API

Embedded Signup can now be used to migrate customer business phone numbers from one WhatsApp Business Account to another.

Business Management API, Cloud API, On-Premises API

Business Management API, Cloud API, On-Premises API

Cloud API, On-Premises API

Cloud API, On-Premises API

Added a new boolean field, override_default_response_type. When set to true, any response types passed in response_type will take precedence over the default types.

Added granular business tokens that exist at the client business level as an opt-in feature to help partners improve account security. In addition, we have updated the creation screens for Pre Filled Data.

Pre-verified business phone numbers now have a VERIFIED status of 28 days (up from 14).

Authentication template copy code button text and autofill button text are now optional upon creation.

We are requiring Solution Partners to request the whatsapp_business_messaging permission to use the API calls on the Cloud API, hosted by Meta. There is now a permissions acknowledgement screen businesses must go through in order to complete Embedded Signup.

Added latency to the WhatsApp Business API Status Page⁠.

Added Business Management API error code 2494100 that indicates a business phone number is temporarily in maintenance mode.

Added error signals that can help debug authentication templates with one-time password autofill buttons.

Added multi-product message templates.

Added hsm_id field to DELETE WhatsApp Business Account > Message Templates endpoint. If included, deletes a single template that matches the supplied ID (instead of deleting all templates that match the supplied name).

Added last_onboarded_time to WhatsApp Business Phone Number node. Indicates when a user created a business phone number on their WhatsApp Business Account by completing the Embedded Signup flow.

Added last_onboarded_time field to the GET /<WHATSAPP_BUSINESS_PHONE_NUMBER_ID> and GET <WABA_ID>/phone_numbers endpoints to enable sorting results by when a user last onboarded the Embedded Signup flow. If this parameter is not specified, the results are sorted in descending order.

Added WhatsApp Business Phone Number > Business Compliance Info endpoint for adding/updating a business phone number’s India-based compliance information.

Business Management AI, Cloud API, On-Premises API

You can now share location information with users by adding a Location Header in your template.

Conversely, users can now share their location information with businesses via Location Request Messages.

Cloud API, On-Premises API

Migrating an India-based business phone number from On-Premises API to Cloud API no longer deletes its online selling compliance data⁠, so you no longer have to manually repopulate this data after migration.

Added a new template comparison endpoint that allows you to compare template send counts and block ratios.

Cloud API, On-Premises API

Added a new WhatsApp Business Phone Number > Commerce Settings endpoint to enable/disable the shopping cart and product catalog on individual business phone numbers. See Set Commerce Settings for Cloud API and Set Commerce Settings for On-Premises API for usage instructions and to learn how these settings can help you sell products and services.

Business Management API, Cloud API

Graph API version 16 is now available. Changes to message template categories, API error responses, and webhooks have been introduced as part of this version.

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

These changes are reflected in the following errors properties in error-related webhooks:

Unverified businesses can now initiate up to 250 conversations in a rolling 24-hour period.

We have started rolling out the new embedded signup UI.

Added new optional phone_number_id field to the Media endpoint. If you include this parameter and a business phone number ID, the operation will only be processed if the phone number ID matches the ID of the phone number upon which the media was uploaded.

Added a new template_performance_metrics field. Notifies you weekly of all template performance metrics, including messages sent count, messages opened count, and top reasons for blocks.

New account_alerts field:

New account_update field values:

Sample Webhooks notifications that are sent when these new events are triggered:

Added the following WhatsApp Business Account node fields:

Added the following filter options to the Business Client Whatsapp Business Accounts endpoint:

Added the following filter options to the Business Owned WhatsApp Business Accounts endpoint:

Applies to v15.0 and newer.

Added the following WhatsApp Business Phone Number node fields:

In addition, you can filter WhatsApp Business Account Phone Numbers endpoint by is_official_business_account.

Applies to v15.0 and newer.

Cloud API now supports up to 500 (up from 350) messages per second (mps) of combined text and media messages, by request. See Throughput for details.

If you already have 350 mps it will be increased to 500 mps automatically. If you already requested 350 mps but the process has not been completed, you will receive 500 mps upon completion.

We are now beta testing Cloud API media HTTP caching. If you are a Solution Partner, see Media HTTP Caching to learn how to use headers in your server responses that instruct us to cache your media assets for reuse with future messages.

Cloud API now supports captions on documents sent to and received from customers. See Media Object in the Media reference.

WhatsApp Business Accounts can now have up to 6,000 message templates if their parent business has been verified⁠ and at least one of the parent business’s WhatsApp Business Accounts has a business phone number with an approved display name⁠.

As part of this change, translated versions of a message template now count against a WhatsApp Business Account’s template limit.

Businesses in India can now use a credit card to pay for messages sent using the platform. See Add a Credit Card to Your WhatsApp Business Platform Account⁠.

You can now migrate a business phone number to and from Cloud API WhatsApp Business Accounts. See Migrate Phone Number to a Different WABA.

Embedded Signup now supports mobile web browsers. The user interface will automatically optimize for a mobile experience when it detects that the viewer is using a mobile web browser.

Businesses that have been onboarded by a Solution Partner through the Embedded Signup or “On Behalf Of” process can now initiate up to 250 conversations with unique customers in a rolling 24-hour period, immediately.

The v2.41.3 version of our Business API client added a new table index on message_receipt_log that could benefit partners with high throughput needs. For instance, this improvement allows partners to send more than 200 messages/second.

Latest documentation for requesting migration from 80 messages per second to 250 messages per second of combined sending and receiving of text and media messages is now available. See Throughput.

In v2.41.2, we are introducing DB schema changes to improve the performance of the system. As a result, upgrades from v2.37.2 and v2.39.x for set ups with large databases which have millions of message and contact entries will take longer than usual.

Generally, perform upgrades during off-peak hours and upgrade lower-throughput setups first.

For large databases, follow these steps:

Once done, you will be able to upgrade API versions with minimal down time. It is strongly recommended to bring the API client down before using the dbupgrade tool.

Ensure the dbupgrade tool completes successfully (exit code 0), and avoid or limit API requests while the upgrade is taking place.

We recommend increasing the query timeout on your database servers to one hour, until the upgrade completes successfully.

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⁠.

The following values for the category parameter for the /WHATSAPP-BUSINESS-ACCOUNT-ID/message_template endpoint have been deprecated for v14.0 and later:

The following values have been added:

This client version contains all features and fixes shipped with v2.39.1. Additionally, this release:

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.

AWS Service Templates and Template URLs:

Changelog:

AWS Service Templates and Template URLs

Changelog:

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 Solution Partners and direct clients. Additionally, we’re releasing the following features for Cloud API developers:

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.

Known Issues:

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"]

The 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.

Known Issues:

Cloud API beta users can start sending and receiving video messages. The following documentation provides more information:

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.

The 2.39.1 version of our Business API client is available for developers starting today. The new client includes:

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.

With 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.

Some video messages fail to send under certain circumstances.

Starting today, Cloud API beta users can start sending audio messages to their customers. For supported audio types, see our media documentation.

We have updated our webhooks documentation to clarify the following: if you receive a message type that is not yet supported by Cloud API, you will be notified via an unknown message webhook. This means that, for the current API beta release, you will get an unknown message webhook if you receive any of the following message types: Media Messages (Video), Contact Messages, Location Messages, Stickers, Stickerpacks.

We have updated the list of features that will be available for the Cloud API Beta release. This is an updated snapshot of the features and their availability:

Available for beta:

Not available for beta:

Endpoint Availability:

The following endpoints will not be available for the Cloud API Beta release:

Staged Onboarding:

We’ve added specific instructions for each stage of the beta implementation. See more information here.

Migrating Between On-Premises and Cloud API:

We’ve added instructions to migrate from the Cloud API back to On-Premises, if needed. See more information here.