{"id":2246,"date":"2026-10-01T11:38:35","date_gmt":"2026-10-01T11:38:35","guid":{"rendered":"https:\/\/360dialog.com\/blog\/?p=2246"},"modified":"2026-10-01T11:38:37","modified_gmt":"2026-10-01T11:38:37","slug":"embedded-signup-versions-migration","status":"publish","type":"post","link":"https:\/\/360dialog.com\/blog\/embedded-signup-versions-migration\/","title":{"rendered":"WhatsApp Embedded Signup for SaaS Platforms: Versions, Migration, and the v2 and v3 Deadline"},"content":{"rendered":"\n

WhatsApp Embedded Signup is the sign-up flow a SaaS platform adds to its own product so business customers can connect their WhatsApp accounts and phone numbers to the platform in a pop-up window.<\/strong> Meta deprecates version 2 (v2), version 3 (v3) and their public preview versions on October 15, 2026.[1] Version 4 (v4) has no announced end date, keeps support for the Marketing Messages API for WhatsApp, and adds Click to WhatsApp Ads and Conversions API support. This guide shows how to check which version you run, what changes in v4, and how to migrate before the deadline.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Key Takeaways<\/h2>\n\n\n\n
    \n
  1. The extras object in your Embedded Signup launch code shows which version you run, and reading it takes a few minutes.<\/li>\n\n\n\n
  2. Embedded Signup v2, v3, and their public previews reach their deprecation date on October 15, 2026, while v4 and its public preview have no announced end date.<\/li>\n\n\n\n
  3. Meta estimates up to one week of developer effort to reach v4, including testing.<\/li>\n\n\n\n
  4. Meta upgrades most remaining v2 and v3 integrations automatically, but v2 integrations that use only_waba_sharing, marketing_messages_lite, or coex need developer updates before October 15, 2026.<\/li>\n\n\n\n
  5. A platform needs Solution Partner or Tech Provider status and advanced access from App Review before it can onboard business customers.<\/li>\n<\/ol>\n\n\n\n

    <\/p>\n\n\n\n

    What Is WhatsApp Embedded Signup?<\/h2>\n\n\n\n

    Embedded Signup is an authentication and authorization interface, compatible with desktop and mobile, that business customers use to generate the WhatsApp assets a partner needs to onboard them to the WhatsApp Business Platform.[2] A SaaS company launches it from a link or button, and it opens in a new window. The flow gathers business information, creates the assets, and grants your Meta app access to them. It runs on Facebook Login for Business and the Facebook JavaScript SDK, and customers keep ownership of every asset along with full WhatsApp Manager access.<\/p>\n\n\n\n

    Two partner types can run the flow. Solution Partners must already have a line of credit that they share with their customers for billing. Tech Providers are the software platforms that obtain advanced access to the whatsapp_business_messaging and whatsapp_business_management permissions through Meta’s App Review, and their customers add a payment method to their own Messaging account.<\/p>\n\n\n\n

    Meta’s account terms are changing: older documentation and many code samples say WhatsApp Business account (WABA), the container for a business’s WhatsApp assets. Meta is splitting it into a WhatsApp account and a Messaging account, with a rollout that starts on September 23, 2026 and reaches all businesses by mid-October 2026, and existing waba_id values now denote Messaging account IDs.[3] Meta states that existing IDs, endpoints, and access tokens keep working throughout the rollout, and its Embedded Signup overview labels the change a beta that is subject to change. This guide uses the new terms from here on.<\/p>\n\n\n\n

    360Dialog, an Official Meta Solution Partner, offers Embedded Signup to SaaS partners through its Partner Platform. Integrated Onboarding there has four methods: Direct Link (no-code), Connect Button (a React NPM package, low-code), Custom IO (framework-agnostic), and Partner-Hosted Embedded Signup (high-code, for Meta-approved Tech Providers).[4] The 360Dialog Embedded Signup is triggered automatically throughout Integrated Onboarding, and partners can host their own flow after meeting Meta’s requirements. The business side of the decision, including build-or-buy trade-offs, monetization, and partner choice, is covered in our SaaS integration context<\/a> article.<\/p>\n\n\n\n

    If your platform has to offer customers WhatsApp onboarding before Meta retires v2 and v3 on October 15, 2026, talk to us<\/a> about which Integrated Onboarding method fits your product.<\/strong><\/p>\n\n\n\n

    <\/p>\n\n\n\n

    Which Embedded Signup Versions Are Still Available?<\/h2>\n\n\n\n

    Meta lists six Embedded Signup versions: v2, v3, v4, and a public preview for each. Meta deprecates v2 and v3 together with their public previews on October 15, 2026, and announces no end date yet for v4 and the v4 public preview. A public preview is an opt-in version that you select with the version value in the extras object.<\/p>\n\n\n\n

    The extras object is the options property you pass to FB.login in your launch code, and its shape tells you the version. Meta prints these shapes for v2, v3, and v4:<\/p>\n\n\n\n

    \/\/ v2: no version field; sessionInfoVersion turns session logging on (possible value: 3)\nextras: {\n    setup: \"<SETUP_DATA>\",\n    features: [ { name: \"<FEATURE_NAME>\" } ],\n    featureType: \"<FEATURE_TYPE>\",\n    sessionInfoVersion: \"<SESSION_INFO_VERSION>\"\n}\n\/\/ v3\nextras: {\n    setup: \"<SETUP_DATA>\",\n    features: [ { name: \"<FEATURE_NAME>\" } ],\n    featureType: \"<FEATURE_TYPE>\",\n    version: \"v3\"\n}\n\/\/ v4: the extras object is purposely empty\nextras: {}<\/code><\/pre>\n\n\n\n
    A Facebook Login for Business configuration is a saved set of login options in your Meta app dashboard, identified by a configuration ID, that defines which products the flow includes. Meta documents that creating a new configuration and selecting products automatically sets you to v4.[5] That makes the configuration part of the version check for any integration whose launch code omits a version value. To opt into the v4 preview first, set the version value:<\/p>\n\n\n\n
    extras: { version: \"v4-public-preview\" }<\/code><\/pre>\n\n\n\n
    Meta’s versions page gives these dates:<\/p>\n\n\n\n
    Version<\/th>Date Introduced<\/th>Available Until<\/th><\/tr><\/thead>
    v4 public preview<\/td>May 12, 2026<\/td>Not announced<\/td><\/tr>
    v4<\/td>October 8, 2025<\/td>Not announced<\/td><\/tr>
    v3 public preview<\/td>August 14, 2025<\/td>October 15, 2026<\/td><\/tr>
    v2 public preview<\/td>August 14, 2025<\/td>October 15, 2026<\/td><\/tr>
    v3<\/td>May 29, 2025<\/td>October 15, 2026<\/td><\/tr>
    v2<\/td>January 2023<\/td>October 15, 2026<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    <\/p>\n\n\n\n
    If you are sizing how many customer channels your platform will move to v4 before the October 15, 2026 deadline, talk to us<\/a> about plans and pricing.<\/strong><\/p>\n\n\n\n
    <\/p>\n\n\n\n
    What Changes When You Move to v4?<\/h2>\n\n\n\n
    v4 selects products through a Facebook Login for Business configuration and can onboard a business to several Meta messaging products in one flow. Meta’s v4 page lists Conversions API, Click to WhatsApp Ads, Click to Messenger Ads, and Click to Direct Ads as additional supported products, and states that v4 continues to support Cloud API, the Marketing Messages API for WhatsApp, WhatsApp Business app onboarding, partner-led Business Verification, and the Automatic Events API.<\/p>\n\n\n\n
    Cloud API is Meta’s hosted WhatsApp Business API. The Marketing Messages API for WhatsApp is Meta’s API for sending marketing messages. Click to WhatsApp Ads (CTWA) are Meta ads that open a WhatsApp conversation, and the Conversions API returns conversion events to Meta for ad measurement. Meta’s versions table lists the Marketing Messages API for WhatsApp, Click to WhatsApp Ads, and Conversions API (WhatsApp) as products selectable through the login configuration for v4 only, while v2 and v3 integrations reach the Marketing Messages API through the marketing_messages_lite feature name.<\/p>\n\n\n\n
    The flow itself changes in several ways:<\/p>\n\n\n\n