{"id":469,"date":"2026-10-28T16:01:28","date_gmt":"2026-10-28T16:01:28","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/whatsapp-account-messaging-account-waba\/"},"modified":"2026-10-28T16:01:38","modified_gmt":"2026-10-28T16:01:38","slug":"whatsapp-account-messaging-account-waba","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/","title":{"rendered":"WhatsApp account vs. Messaging account: the new WABA structure"},"content":{"rendered":"\n<p><em>Updated on October 28, 2026<\/em><\/p>\n\n\n\n<p>Since September 23, 2026, Meta has been splitting the old WhatsApp Business Account (WABA) in two: the <strong>WhatsApp account<\/strong> (WAAC), which holds the phone number and profile, and the <strong>Messaging account<\/strong>, which holds templates, billing and webhook subscriptions. The migration is automatic, current IDs and tokens keep working, and the Messaging account inherits the WABA ID. The most practical consequence: switching or adding a provider no longer requires migrating the number; you just share the WhatsApp account.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why Meta changed the WABA<\/h2>\n\n\n\n<p>The <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/account-model-evolution\/\" target=\"_blank\" rel=\"noreferrer noopener\">Updates to WhatsApp Business accounts<\/a> page explains the problem. The WABA bundled the number, templates, billing, webhooks and partner access into a single entity. To work with two partners, a business needed two numbers, and end users saw two different contacts for the same brand.<\/p>\n\n\n\n<p>The new model separates the business identity (the number) from messaging operations (templates and billing). One number can have several Messaging accounts, one per integration, each with its own templates, payment method and metrics. WhatsApp users still see a single contact.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What lives in each account<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Asset<\/th><th>Before (WABA)<\/th><th>After (new model)<\/th><\/tr><\/thead><tbody><tr><td>Phone number<\/td><td>WABA<\/td><td>WhatsApp account (WAAC)<\/td><\/tr><tr><td>Business username (upcoming)<\/td><td>didn&#8217;t exist<\/td><td>WhatsApp account<\/td><\/tr><tr><td>Business profile and catalogs<\/td><td>WABA<\/td><td>WhatsApp account<\/td><\/tr><tr><td>Templates<\/td><td>WABA<\/td><td>Messaging account (one per partner)<\/td><\/tr><tr><td>Billing and payment method<\/td><td>WABA<\/td><td>Messaging account<\/td><\/tr><tr><td>Webhook subscriptions<\/td><td>WABA<\/td><td>Messaging account<\/td><\/tr><tr><td>Conversation history and quality<\/td><td>Number<\/td><td>Number (unchanged)<\/td><\/tr><tr><td>Business verification<\/td><td>Portfolio<\/td><td>Portfolio (unchanged)<\/td><\/tr><tr><td>Access tokens<\/td><td>App + WABA<\/td><td>App + Messaging account (same tokens)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>A few details the table doesn&#8217;t show:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Each WAAC holds a single number.<\/strong> To group numbers, Meta uses a hierarchy with a primary WAAC and linked WAACs. Sharing the primary one grants access to every number in the set.<\/li>\n\n\n<li><strong>The WAAC always belongs to the client<\/strong> (or direct developer). The Messaging account can belong to the client or the partner.<\/li>\n\n\n<li><strong>In the Terms of Service<\/strong>, the WAAC is called the &#8220;WhatsApp Business Account&#8221; and the other one the &#8220;Messaging account&#8221;. Worth knowing when you read a contract.<\/li>\n\n\n<li><strong>Templates aren&#8217;t shared<\/strong> between Messaging accounts. If you need the same template in two, create it in each or use the template migration API. When templates are migrated, quality rating and messaging tier reset to defaults, with an adjustment period of 2 to 4 weeks.<\/li>\n\n\n<li><strong>Throughput and messaging limits stay where they were.<\/strong> Throughput belongs to the number, and the unique-recipients-per-24-hours limit belongs to the portfolio; when several partners use the same number, they share both.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">What changes (and what doesn&#8217;t) in the API<\/h2>\n\n\n\n<p>The list of what <strong>doesn&#8217;t<\/strong> change is long: Cloud API, Business Management API and Marketing Messages API endpoints; <code>POST \/&lt;PHONE_NUMBER_ID&gt;\/messages<\/code>; phone number IDs; tokens; template workflows; number registration; business verification; display names; quality; and the <code>whatsapp_business_account<\/code> webhook subscription, now made with the Messaging account ID (the same as the WABA ID). <code>GET\/POST\/DELETE \/&lt;WABA_ID&gt;\/message_templates<\/code> stays the same.<\/p>\n\n\n\n<p>What changes comes in three phases:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Phase<\/th><th>When<\/th><th>What ships<\/th><th>What you do<\/th><\/tr><\/thead><tbody><tr><td>1. General availability<\/td><td>Sept 23, 2026 through mid-October 2026<\/td><td>Automatic migration; Messaging accounts keep the WABA ID; WAACs created but IDs not exposed; <code>messaging_account_id<\/code> optional<\/td><td>Nothing, unless your token reaches more than one Messaging account on the same number<\/td><\/tr><tr><td>2. New Graph API version<\/td><td>H1 2027<\/td><td>WAAC ID returned alongside the number ID; new endpoints; <code>whatsapp_account<\/code> webhook topic; separate permissions for WAAC and Messaging account scopes; <code>messaging_account_id<\/code> required on the new version in multi-account setups<\/td><td>Capture <code>waac_id<\/code> in events and adopt the new version if you have several Messaging accounts<\/td><\/tr><tr><td>3. Mandatory transition<\/td><td>H1 2028<\/td><td>APIs that take the phone number ID in the path (including <code>\/messages<\/code> and <code>\/marketing_messages<\/code>) require the WAAC ID<\/td><td>Have your code migrated during 2027<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Meta notes that the whole page is subject to change. The 2027 and 2028 dates are half-years, not specific days.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The messaging_account_id parameter<\/h3>\n\n\n\n<p>When your token can reach more than one Messaging account on the same number, Meta can&#8217;t tell which to bill. This parameter resolves it:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code class=\"language-bash\">curl -X POST 'https:\/\/graph.facebook.com\/&lt;API_VERSION&gt;\/&lt;PHONE_NUMBER_ID&gt;\/messages' \\\n  -H 'Authorization: Bearer &lt;ACCESS_TOKEN&gt;' \\\n  -H 'Content-Type: application\/json' \\\n  -d '{\n    \"messaging_product\": \"whatsapp\",\n    \"to\": \"15551234567\",\n    \"messaging_account_id\": \"&lt;MESSAGING_ACCOUNT_ID&gt;\",\n    \"type\": \"template\",\n    \"template\": { \"name\": \"order_shipped\", \"language\": { \"code\": \"en_US\" } }\n  }'<\/code><\/pre>\n\n\n\n<p>Rules from the <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/account-model-evolution\/messaging\/\" target=\"_blank\" rel=\"noreferrer noopener\">Messaging accounts page<\/a>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>if the token reaches only one Messaging account on that number, Meta picks it for you;<\/li>\n\n\n<li>if it reaches two or more and you omit the parameter, the message may be billed to the wrong account or the request may be rejected;<\/li>\n\n\n<li><code>paid_messaging_account_id<\/code> is a legacy alias: migrate to <code>messaging_account_id<\/code> by <strong>December 31, 2026<\/strong>; if you send both, <code>messaging_account_id<\/code> wins;<\/li>\n\n\n<li>to check whether a Messaging account has a payment method, call <code>GET \/&lt;MESSAGING_ACCOUNT_ID&gt;?fields=primary_funding_id<\/code>; without that field, it can&#8217;t send paid messages.<\/li>\n\n<\/ul>\n\n\n\n<p>Typical cases that need the parameter: a direct developer outsourcing marketing to a partner on the same number, a partner that received two Messaging accounts from one client, and a client billed in different currencies (each currency requires its own Messaging account).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">IDs in webhooks<\/h3>\n\n\n\n<p>In phase 1 nothing changes in code, but the <code>waba_id<\/code> in events now means the Messaging account ID. In phase 2, events gain <code>waac_id<\/code>. Store all three (<code>waac_id<\/code>, phone number ID and <code>waba_id<\/code>) in your instance records. If your CRM is also adapting to <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-usernames-bsuid\/\">usernames and BSUIDs<\/a>, it&#8217;s worth doing both data model changes together.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Switching providers got simpler<\/h2>\n\n\n\n<p>This is the most visible impact for anyone buying API access. Since August 18, 2026, Meta documents that <strong>phone number migration between partners isn&#8217;t supported<\/strong> in the new model. Instead:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The client shares the WhatsApp account (WAAC) with the new provider.<\/li>\n\n\n<li>Embedded Signup automatically creates a new Messaging account for that provider, returning its ID in the WABA ID field.<\/li>\n\n\n<li>The number, conversations and quality rating stay where they were; there&#8217;s no downtime.<\/li>\n\n\n<li>The client decides whether to keep or remove the previous provider, whenever they want.<\/li>\n\n<\/ol>\n\n\n\n<p>Two caveats. First, because templates are isolated per Messaging account, the new provider starts without your templates: recreate or migrate them. Second, registration with the new provider is routed to the already registered number without resetting the PIN, and Meta is phasing out the 6-digit two-step verification PIN for eligible Cloud API numbers (still, keep sending a valid <code>pin<\/code> to <code>\/register<\/code> until Meta announces a different contract). More context in <a href=\"https:\/\/vectalk.com.br\/blog\/en\/switch-whatsapp-api-provider\/\">how to switch WhatsApp API providers<\/a> and <a href=\"https:\/\/vectalk.com.br\/blog\/en\/register-phone-number-whatsapp-cloud-api\/\">registering a number on the Cloud API<\/a>.<\/p>\n\n\n\n<p>When a provider is removed from a Messaging account, it receives the <code>account_update<\/code> webhook. For setups with more than one partner on the same number, Meta launched Conversation Routing on September 23, 2026, which defines which partner receives each inbound message.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Coexistence and the new structure<\/h2>\n\n\n\n<p>WhatsApp Business app numbers in coexistence (connected to the API while still using the app) are migrated too. During coexistence onboarding, Meta converts the client&#8217;s existing WABA into a backward-compatible Messaging account (same ID) and shares both the WhatsApp account and that Messaging account with the partner; no partner-specific Messaging account is created. The coexistence guide now requires subscribing to <code>account_update<\/code>. What syncs between app and API is covered in <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-coexistence-what-syncs\/\">WhatsApp coexistence: what syncs<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What changes in Meta Business Suite<\/h2>\n\n\n\n<p>For businesses already migrated, Meta Business Suite shows two tabs: <strong>WhatsApp accounts<\/strong> (numbers and usernames) and <strong>Messaging accounts<\/strong> (templates and billing). Until your business is migrated, WhatsApp Manager and Business Suite keep the old view, so the docs may be ahead of what you see. If you manage several brands, this changes the routine described in <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-for-agencies\/\">WhatsApp API for agencies<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How it works with Vectalk<\/h2>\n\n\n\n<p>Vectalk is a proxy for the official <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-cloud-api-en\/\">WhatsApp Cloud API<\/a>. Connecting still happens through Embedded Signup under <strong>Instances \u2192 Connect account<\/strong>, which imports <code>phone_number_id<\/code>, <code>waba_id<\/code> and the token; under the new model, that <code>waba_id<\/code> is the Messaging account ID. If you&#8217;re coming from another provider, Meta&#8217;s rule for the new model applies here too: the number isn&#8217;t migrated; the WhatsApp account is shared with the new provider. Step by step in the <a href=\"https:\/\/docs.vectalk.com.br\/quickstart\">quickstart<\/a>; sign up at <a href=\"https:\/\/apps.vectalk.com.br\/register\">apps.vectalk.com.br\/register<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Did my WABA ID change?<\/h3>\n\n\n\n<p>No. The WABA ID became the Messaging account ID and keeps working in template, webhook and Business Management API calls.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need to change my code now?<\/h3>\n\n\n\n<p>Only if your token can reach more than one Messaging account on the same number; in that case, send <code>messaging_account_id<\/code>. Also replace <code>paid_messaging_account_id<\/code> with <code>messaging_account_id<\/code> by December 31, 2026. The bigger task, using WAAC IDs, is for 2027, ahead of phase 3 in 2028.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I use two providers on the same number?<\/h3>\n\n\n\n<p>Yes. The new model was built for that: each provider has its own Messaging account, with separate billing. They share the number&#8217;s throughput and the portfolio&#8217;s messaging limit.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do my templates come with me when I switch providers?<\/h3>\n\n\n\n<p>Not automatically. Templates belong to the Messaging account. Recreate them with the new provider or use the template migration API, knowing that quality and tier restart from defaults.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is phone number migration between providers still possible?<\/h3>\n\n\n\n<p>Not in the new model. Meta documents that the request is rejected if the destination WhatsApp account doesn&#8217;t own the number. The path is sharing the WAAC.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>Official sources consulted on October 28, 2026:<\/strong> <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/account-model-evolution\/\" target=\"_blank\" rel=\"noreferrer noopener\">Updates to WhatsApp Business accounts<\/a> (updated September 22, 2026), <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/account-model-evolution\/messaging\/\" target=\"_blank\" rel=\"noreferrer noopener\">Managing Messaging accounts<\/a> (updated August 29, 2026), <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/account-model-evolution\/onboarding\/\" target=\"_blank\" rel=\"noreferrer noopener\">Onboarding changes<\/a> (updated June 26, 2026), <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/changelog\" target=\"_blank\" rel=\"noreferrer noopener\">WhatsApp Business Platform changelog<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Since Sept 23, 2026, the WABA became two accounts: the WhatsApp account, with the number, and the Messaging account, with templates and billing.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-469","post","type-post","status-publish","format-standard","hentry","category-blog"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>New WABA Structure: WhatsApp vs. Messaging Account | Vectalk<\/title>\n<meta name=\"description\" content=\"The new WABA structure: what lives in the WhatsApp account vs. the Messaging account, API IDs, phases through 2028, and switching providers.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"New WABA Structure: WhatsApp vs. Messaging Account | Vectalk\" \/>\n<meta property=\"og:description\" content=\"The new WABA structure: what lives in the WhatsApp account vs. the Messaging account, API IDs, phases through 2028, and switching providers.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog Vectalk\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-28T16:01:28+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-28T16:01:38+00:00\" \/>\n<meta name=\"author\" content=\"wanderleyfcunha\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"wanderleyfcunha\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-account-messaging-account-waba\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-account-messaging-account-waba\\\/\"},\"author\":{\"name\":\"wanderleyfcunha\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/ff36ecd9d8257856f227f8e5d639db2b\"},\"headline\":\"WhatsApp account vs. Messaging account: the new WABA structure\",\"datePublished\":\"2026-10-28T16:01:28+00:00\",\"dateModified\":\"2026-10-28T16:01:38+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-account-messaging-account-waba\\\/\"},\"wordCount\":1468,\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-account-messaging-account-waba\\\/\",\"url\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-account-messaging-account-waba\\\/\",\"name\":\"New WABA Structure: WhatsApp vs. Messaging Account | Vectalk\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#website\"},\"datePublished\":\"2026-10-28T16:01:28+00:00\",\"dateModified\":\"2026-10-28T16:01:38+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/ff36ecd9d8257856f227f8e5d639db2b\"},\"description\":\"The new WABA structure: what lives in the WhatsApp account vs. the Messaging account, API IDs, phases through 2028, and switching providers.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-account-messaging-account-waba\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-account-messaging-account-waba\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-account-messaging-account-waba\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"WhatsApp account vs. Messaging account: the new WABA structure\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/\",\"name\":\"Blog Vectalk\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/ff36ecd9d8257856f227f8e5d639db2b\",\"name\":\"wanderleyfcunha\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g\",\"caption\":\"wanderleyfcunha\"},\"sameAs\":[\"https:\\\/\\\/vectalk.com.br\\\/blog\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"New WABA Structure: WhatsApp vs. Messaging Account | Vectalk","description":"The new WABA structure: what lives in the WhatsApp account vs. the Messaging account, API IDs, phases through 2028, and switching providers.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/","og_locale":"en_US","og_type":"article","og_title":"New WABA Structure: WhatsApp vs. Messaging Account | Vectalk","og_description":"The new WABA structure: what lives in the WhatsApp account vs. the Messaging account, API IDs, phases through 2028, and switching providers.","og_url":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/","og_site_name":"Blog Vectalk","article_published_time":"2026-10-28T16:01:28+00:00","article_modified_time":"2026-10-28T16:01:38+00:00","author":"wanderleyfcunha","twitter_card":"summary_large_image","twitter_misc":{"Written by":"wanderleyfcunha","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/#article","isPartOf":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/"},"author":{"name":"wanderleyfcunha","@id":"https:\/\/vectalk.com.br\/blog\/#\/schema\/person\/ff36ecd9d8257856f227f8e5d639db2b"},"headline":"WhatsApp account vs. Messaging account: the new WABA structure","datePublished":"2026-10-28T16:01:28+00:00","dateModified":"2026-10-28T16:01:38+00:00","mainEntityOfPage":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/"},"wordCount":1468,"articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/","url":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/","name":"New WABA Structure: WhatsApp vs. Messaging Account | Vectalk","isPartOf":{"@id":"https:\/\/vectalk.com.br\/blog\/#website"},"datePublished":"2026-10-28T16:01:28+00:00","dateModified":"2026-10-28T16:01:38+00:00","author":{"@id":"https:\/\/vectalk.com.br\/blog\/#\/schema\/person\/ff36ecd9d8257856f227f8e5d639db2b"},"description":"The new WABA structure: what lives in the WhatsApp account vs. the Messaging account, API IDs, phases through 2028, and switching providers.","breadcrumb":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/vectalk.com.br\/blog\/"},{"@type":"ListItem","position":2,"name":"WhatsApp account vs. Messaging account: the new WABA structure"}]},{"@type":"WebSite","@id":"https:\/\/vectalk.com.br\/blog\/#website","url":"https:\/\/vectalk.com.br\/blog\/","name":"Blog Vectalk","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/vectalk.com.br\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/vectalk.com.br\/blog\/#\/schema\/person\/ff36ecd9d8257856f227f8e5d639db2b","name":"wanderleyfcunha","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g","caption":"wanderleyfcunha"},"sameAs":["https:\/\/vectalk.com.br\/blog"]}]}},"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts\/469","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/comments?post=469"}],"version-history":[{"count":1,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts\/469\/revisions"}],"predecessor-version":[{"id":472,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts\/469\/revisions\/472"}],"wp:attachment":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/media?parent=469"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/categories?post=469"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/tags?post=469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}