{"id":660,"date":"2026-10-29T13:11:31","date_gmt":"2026-10-29T13:11:31","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/whatsapp-api-coexistence\/"},"modified":"2026-10-29T13:11:46","modified_gmt":"2026-10-29T13:11:46","slug":"whatsapp-api-coexistence","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/","title":{"rendered":"WhatsApp coexistence: how to use the same number in the Business app and the official API"},"content":{"rendered":"\n<p><em>Updated on October 29, 2026<\/em><\/p>\n\n\n\n<p>Coexistence is the Meta feature that connects a number already active in the WhatsApp Business app to the WhatsApp Cloud API without removing it from the app. After onboarding, the business keeps chatting from the phone and, at the same time, sends and receives messages through the API, with history synced between the two. The connection is made through a Meta partner&#8217;s Embedded Signup and comes with limits: a fixed throughput of 20 messages per second, some app features turned off, and the need to open the app regularly.<\/p>\n\n\n\n<p>In Meta&#8217;s documentation, the feature is called &#8220;Onboard WhatsApp Business app users&#8221; (<a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/embedded-signup\/onboarding-business-app-users\" target=\"_blank\" rel=\"noreferrer noopener\">Onboard WhatsApp Business app users<\/a>), and Meta notes that it is sometimes referred to as &#8220;Coexistence&#8221; in support channels and partner documentation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why coexistence exists<\/h2>\n\n\n\n<p>Before it, putting a number on the WhatsApp Business API meant deleting it from the app. The <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/business-phone-numbers\/phone-numbers\" target=\"_blank\" rel=\"noreferrer noopener\">Cloud API phone numbers documentation<\/a> still says that numbers already in use with WhatsApp cannot be registered unless they are deleted first; coexistence, documented on the onboarding page, is the route for WhatsApp Business app numbers. For small businesses, the old route meant losing chat history and the phone-based way of working.<\/p>\n\n\n\n<p>With coexistence, the Business app number also becomes an API number. The owner keeps replying from the phone, and a connected system (CRM, chatbot, AI agent, notification platform) starts operating on the same number.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happens to the account during onboarding<\/h2>\n\n\n\n<p>When the customer finishes the flow, Meta converts the existing WhatsApp Business account into a compatible messaging account. In practice:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The ID returned by Embedded Signup is the same numeric ID the account had before the conversion: in the <code>waba_id<\/code> field in version 4, and in the <code>messaging_account_ids<\/code> field in version 5.<\/li>\n\n\n<li>No separate messaging account is created for the partner.<\/li>\n\n\n<li>The WhatsApp account tied to the number and the converted messaging account are shared with the partner, but stay in the customer&#8217;s business portfolio.<\/li>\n\n\n<li>The phone number registration step is skipped, because the number is already registered.<\/li>\n\n<\/ul>\n\n\n\n<p>Since September 23, 2026, Meta splits the old WABA into a WhatsApp account (the number) and a messaging account (templates, billing, webhooks). If that structure is new to you, see <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-account-messaging-account-waba\/\">WhatsApp account vs. messaging account<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Requirements<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Requirement<\/th><th>Detail<\/th><\/tr><\/thead><tbody><tr><td>App version<\/td><td>WhatsApp Business app 2.24.17 or later on the customer&#8217;s phone<\/td><\/tr><tr><td>Who onboards<\/td><td>A Meta Solution Partner or Tech Provider<\/td><\/tr><tr><td>Flow<\/td><td>Embedded Signup with session logging<\/td><\/tr><tr><td>Webhooks<\/td><td>An endpoint able to receive and process the extra fields (see below)<\/td><\/tr><tr><td>Embedded Signup version<\/td><td>Versions 2 and 3 are discontinued; in version 5 (October 20, 2026), coexistence is on by default<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>The last row changed recently. Meta announced that Embedded Signup versions 2 and 3 would be deprecated on October 15, 2026, and on October 20, 2026 it released version 5, where onboarding WhatsApp Business app users is enabled by default. Older integrations need to be updated.<\/p>\n\n\n\n<p>Meta&#8217;s onboarding page does not list country restrictions for the feature.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How the flow works for the customer<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In Embedded Signup, the customer chooses to connect an existing WhatsApp Business app account and enters the number.<\/li>\n\n\n<li>WhatsApp shows a verification code.<\/li>\n\n\n<li>The customer receives a message in the app from the official Facebook Business account and taps <strong>Connect<\/strong>, then <strong>Connect to the Business Platform<\/strong>.<\/li>\n\n\n<li>The app asks whether they want to share their chat history with the partner.<\/li>\n\n\n<li>The customer pastes the code and completes the flow.<\/li>\n\n<\/ol>\n\n\n\n<p>On the partner side, Embedded Signup returns the IDs and an exchangeable token code, like any onboarding. The difference is the session event, which in version 4 looks like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code class=\"language-json\">{\n  \"data\": { \"waba_id\": \"&lt;CUSTOMER_WABA_ID&gt;\" },\n  \"type\": \"WA_EMBEDDED_SIGNUP\",\n  \"event\": \"FINISH_WHATSAPP_BUSINESS_APP_ONBOARDING\"\n}<\/code><\/pre>\n\n\n\n<p>In version 5, the event keeps the same name when the number comes from the app (<code>is_on_biz_app: true<\/code>), but <code>data<\/code> changes: <code>waba_id<\/code> gives way to <code>messaging_account_ids<\/code>, alongside <code>phone_number_id<\/code>, <code>is_on_biz_app<\/code> and <code>business_id<\/code>.<\/p>\n\n\n\n<p>In version 4, you opt in to the feature with <code>featureType<\/code> inside the <code>extras<\/code> object of the Embedded Signup launch code (<code>FB.login<\/code>). In this version, <code>sessionInfoVersion<\/code> is ignored and is always 3:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code class=\"language-js\">FB.login(fbLoginCallback, {\n  config_id: \"&lt;CONFIGURATION_ID&gt;\",\n  response_type: \"code\",\n  override_default_response_type: true,\n  extras: {\n    setup: {},\n    featureType: \"whatsapp_business_app_onboarding\"\n  }\n});<\/code><\/pre>\n\n\n\n<p>In version 5 (<code>version: \"v5\"<\/code> in <code>extras<\/code>), <code>featureType<\/code> is no longer needed, because the option is on by default. To turn it off, add the feature to <code>features<\/code> with <code>enabled: false<\/code>; according to Meta, the opt-out applies even if <code>featureType<\/code> is also passed:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code class=\"language-js\">FB.login(fbLoginCallback, {\n  config_id: \"&lt;CONFIGURATION_ID&gt;\",\n  response_type: \"code\",\n  override_default_response_type: true,\n  extras: {\n    version: \"v5\",\n    features: [\n      { name: \"whatsapp_business_app_onboarding\", enabled: false }\n    ]\n  }\n});<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Sync: the 24-hour deadline<\/h2>\n\n\n\n<p>After onboarding, the partner has <strong>24 hours<\/strong> to sync contacts and history. If the deadline is missed, the customer has to offboard and go through the flow again. Each sync can only be requested once.<\/p>\n\n\n\n<p>Sync uses the SMB App Data API (<code>smb_app_data<\/code>), first for contacts and then for message history:<\/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;BUSINESS_PHONE_NUMBER_ID&gt;\/smb_app_data\" \\\n  -H \"Authorization: Bearer &lt;ACCESS_TOKEN&gt;\" \\\n  -H \"Content-Type: application\/json\" \\\n  -d '{ \"messaging_product\": \"whatsapp\", \"sync_type\": \"smb_app_state_sync\" }'\n\ncurl -X POST \"https:\/\/graph.facebook.com\/&lt;API_VERSION&gt;\/&lt;BUSINESS_PHONE_NUMBER_ID&gt;\/smb_app_data\" \\\n  -H \"Authorization: Bearer &lt;ACCESS_TOKEN&gt;\" \\\n  -H \"Content-Type: application\/json\" \\\n  -d '{ \"messaging_product\": \"whatsapp\", \"sync_type\": \"history\" }'<\/code><\/pre>\n\n\n\n<p>The response includes a <code>request_id<\/code>, worth storing for support tickets. History covers up to six months of one-to-one chats and is only sent if the business agreed to share it; if it declined, the <code>history<\/code> webhook arrives with error <code>2593109<\/code>. Meta recommends asking the customer to keep the app open during the process. The full breakdown of phases, chunks and media is in <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-coexistence-what-syncs\/\">what syncs and what doesn&#8217;t in coexistence<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Additional webhooks<\/h2>\n\n\n\n<p>On top of the fields you already subscribe to, coexistence requires four messaging account fields:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Field<\/th><th>What it carries<\/th><\/tr><\/thead><tbody><tr><td><code>account_update<\/code><\/td><td>Account lifecycle changes, including disconnection (<code>PARTNER_REMOVED<\/code>)<\/td><\/tr><tr><td><code>history<\/code><\/td><td>Past messages sent and received by the customer<\/td><\/tr><tr><td><code>smb_app_state_sync<\/code><\/td><td>New and existing contacts from the app<\/td><\/tr><tr><td><code>smb_message_echoes<\/code><\/td><td>Messages the customer sends from the app after onboarding<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><code>smb_message_echoes<\/code> is what keeps your system up to date: when the owner replies from the phone, the event arrives and you store the message in the contact&#8217;s history. Without it, your system only sees half of the conversation.<\/p>\n\n\n\n<p>To understand the event structure and build a robust endpoint, see <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-webhooks\/\">WhatsApp API webhooks: a practical guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What changes in the WhatsApp Business app<\/h2>\n\n\n\n<p>Meta publishes a table comparing features before and after onboarding. The main points:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>App feature<\/th><th>After onboarding<\/th><th>Available through the API?<\/th><\/tr><\/thead><tbody><tr><td>One-to-one chats<\/td><td>Continue; editing and revoking messages become supported<\/td><td>Yes, mirrored between app and API<\/td><\/tr><tr><td>Contacts<\/td><td>No change<\/td><td>Yes, synced<\/td><\/tr><tr><td>Groups<\/td><td>No change in the app<\/td><td>Not synced<\/td><\/tr><tr><td>Disappearing messages<\/td><td>Turned off for one-to-one chats<\/td><td>No<\/td><\/tr><tr><td>View once<\/td><td>Disabled<\/td><td>No<\/td><\/tr><tr><td>Live location<\/td><td>Disabled<\/td><td>No<\/td><\/tr><tr><td>Broadcast lists<\/td><td>Disabled; existing lists become read-only<\/td><td>No<\/td><\/tr><tr><td>Voice and video calls<\/td><td>No change in the app<\/td><td>No<\/td><\/tr><tr><td>Catalog, orders, status<\/td><td>No change in the app<\/td><td>No<\/td><\/tr><tr><td>Greeting, away messages, quick replies, labels<\/td><td>No change in the app<\/td><td>No<\/td><\/tr><tr><td>Linked devices<\/td><td>Unlinked during onboarding; can be linked again<\/td><td>Except WhatsApp for Windows and WearOS<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>About linked devices: the app supports up to four companion devices. Messages that a WhatsApp user sends from an unsupported companion device do not trigger the messages webhook, so they do not appear in your system.<\/p>\n\n\n\n<p>The Groups API is also not available for WhatsApp Business app numbers, according to the <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/groups\" target=\"_blank\" rel=\"noreferrer noopener\">groups documentation<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Limits that affect operations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Throughput fixed at 20 mps<\/h3>\n\n\n\n<p>Numbers that use the app and the API at the same time have a fixed throughput of 20 messages per second. Regular Cloud API numbers start at 80 mps and can be automatically upgraded to up to 1,000 mps when eligible. For large notification sends, this matters.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Inactivity drops the connection<\/h3>\n\n\n\n<p>The <code>account_update<\/code> webhook with the <code>PARTNER_REMOVED<\/code> event reports the reason for the disconnection. Documented reasons include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>PRIMARY_INACTIVITY<\/code>: the primary device was inactive for about 14 days;<\/li>\n\n\n<li><code>COMPANION_INACTIVITY<\/code>: a companion device was inactive for about 30 days;<\/li>\n\n\n<li><code>BUSINESS_DOWNGRADE<\/code>: the number was registered on regular WhatsApp (Messenger);<\/li>\n\n\n<li><code>CHANGE_NUMBER<\/code> and <code>USER_RE_REGISTERED<\/code>: number change or new registration on another device;<\/li>\n\n\n<li><code>ACCOUNT_DISCONNECTED<\/code>: the account was disconnected due to an enforcement action or because the business deleted its WhatsApp account.<\/li>\n\n<\/ul>\n\n\n\n<p>In practice, tell the customer to open the app on the primary phone regularly. Handle <code>PARTNER_REMOVED<\/code> in your system and alert the team, instead of finding out from messages that stopped going out.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Disconnection only from the app<\/h3>\n\n\n\n<p>The Deregister endpoint does not work for numbers in coexistence. The customer disconnects from the app, under <strong>Settings &gt; Account &gt; Business Platform &gt; Disconnect Account<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Error 131060 on the first message<\/h3>\n\n\n\n<p>Meta documents that incoming messages may arrive with error <code>131060<\/code> when a user writes for the first time (common after an ad click) or uses an unsupported companion device. In the first case, the error usually resolves within seconds. In the second, tell the business to check the message in the app.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pricing and the customer service window in coexistence<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Messages sent <strong>from the app<\/strong> remain free.<\/li>\n\n\n<li>Messages sent <strong>through the API<\/strong> follow Cloud API pricing, by category and country.<\/li>\n\n\n<li>The 24-hour customer service window only opens for messages received <strong>after<\/strong> onboarding. If the customer wrote before, the reply through the API must be a template.<\/li>\n\n\n<li>Messages sent from the app do not open, extend or affect API windows or pricing.<\/li>\n\n<\/ul>\n\n\n\n<p>For numbers in Brazil, rates since October 1, 2026 are R$ 0.3217 per marketing message and R$ 0.0350 per utility, authentication or service message (BRL, the Brazilian real). Each business phone number gets 1,000 free delivered service messages per month, charged from the 1,001st, and utility templates sent inside the customer service window are now charged (they stay free only inside an open free entry point window). Details in <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-pricing-brazil\/\">WhatsApp API pricing in Brazil<\/a>; for other markets, see <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-pricing-by-country\/\">WhatsApp API pricing by country<\/a>. The source is Meta&#8217;s <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/pricing\" target=\"_blank\" rel=\"noreferrer noopener\">official pricing page<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to check whether a number is in coexistence<\/h2>\n\n\n\n<p>Request the <code>is_on_biz_app<\/code> and <code>platform_type<\/code> fields on the number:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code class=\"language-bash\">curl \"https:\/\/graph.facebook.com\/&lt;API_VERSION&gt;\/&lt;PHONE_NUMBER_ID&gt;?fields=is_on_biz_app,platform_type\" \\\n  -H \"Authorization: Bearer &lt;ACCESS_TOKEN&gt;\"<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code class=\"language-json\">{ \"is_on_biz_app\": true, \"platform_type\": \"CLOUD_API\", \"id\": \"106540352242922\" }<\/code><\/pre>\n\n\n\n<p>If <code>is_on_biz_app<\/code> is <code>true<\/code> and <code>platform_type<\/code> is <code>CLOUD_API<\/code>, the number works in both the app and the API.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">When coexistence is worth it<\/h2>\n\n\n\n<p>It fits businesses whose customers already talk to the app number and that want to automate part of their support or notifications without changing numbers. It works well for clinics, shops and service providers where the owner or team still replies from the phone. If you plan to plug a CRM into the number, read <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-coexistence-crm-hubspot\/\">coexistence with a CRM and messaging limits<\/a>.<\/p>\n\n\n\n<p>It is a weaker fit when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>your send volume needs more than 20 messages per second;<\/li>\n\n\n<li>your operation depends on broadcast lists, disappearing messages or groups through the API;<\/li>\n\n\n<li>nobody can keep the primary phone active.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Coexistence and Vectalk<\/h2>\n\n\n\n<p>Vectalk offers coexistence: the number stays in the WhatsApp Business app and also works through the WhatsApp Cloud API. Numbers are connected through Meta&#8217;s Embedded Signup, and payloads and webhooks are the same as in Meta&#8217;s documentation, so <code>history<\/code>, <code>smb_app_state_sync<\/code> and <code>smb_message_echoes<\/code> arrive at the URLs you register with <code>POST \/api\/webhooks<\/code>. Billing is a monthly fee plus prepaid credit: Vectalk attaches its own credit line to the number, each delivered message is deducted from the balance, and you do not need to add a card on Meta. See the <a href=\"https:\/\/docs.vectalk.com.br\/introduction\">documentation<\/a>.<\/p>\n\n\n\n<p>To create an account, use the <a href=\"https:\/\/apps.vectalk.com.br\/register\">sign-up page<\/a>; questions can go through the <a href=\"https:\/\/vectalk.com.br\/contato.html\">contact page<\/a>. If you are still deciding between the API and the app, the <a href=\"https:\/\/vectalk.com.br\/blog\/en\/official-whatsapp-api\/\">guide to the official WhatsApp API<\/a> helps compare them.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does coexistence work with regular WhatsApp (Messenger)?<\/h3>\n\n\n\n<p>No. The feature is for numbers in the WhatsApp Business app. If the number is on regular WhatsApp, you can move it to the Business app first, or delete the app account and register the number directly on the Cloud API; see <a href=\"https:\/\/vectalk.com.br\/blog\/en\/use-existing-whatsapp-number-business-api\/\">how to use an existing WhatsApp number with the API<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Will I lose my chat history?<\/h3>\n\n\n\n<p>Not in the app. For the system connected to the API, Meta lets you sync up to six months of one-to-one chats, if the business allows it, within 24 hours of onboarding. Groups are not synced.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I keep sending messages from my phone?<\/h3>\n\n\n\n<p>Yes. Messages sent from the app remain free and show up in the connected system through the <code>smb_message_echoes<\/code> webhook.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I set up coexistence with a direct integration, without a partner?<\/h3>\n\n\n\n<p>Meta&#8217;s documentation lists being a Solution Partner or Tech Provider as a requirement. A business that only integrates its own number usually does it through a provider.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why did my number disconnect from the API on its own?<\/h3>\n\n\n\n<p>Check the <code>PARTNER_REMOVED<\/code> event in the <code>account_update<\/code> webhook. The most common reason is the primary phone being inactive for about 14 days (<code>PRIMARY_INACTIVITY<\/code>). Reconnecting with the same partner triggers the <code>ACCOUNT_RECONNECTED<\/code> event.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>Sources checked on October 29, 2026:<\/strong> <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/embedded-signup\/onboarding-business-app-users\" target=\"_blank\" rel=\"noreferrer noopener\">Onboard WhatsApp Business app users<\/a>, <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/business-phone-numbers\/phone-numbers\" target=\"_blank\" rel=\"noreferrer noopener\">Business phone numbers<\/a>, <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/groups\" target=\"_blank\" rel=\"noreferrer noopener\">Groups API<\/a>, <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/pricing\" target=\"_blank\" rel=\"noreferrer noopener\">Pricing<\/a>, <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/changelog\" target=\"_blank\" rel=\"noreferrer noopener\">Changelog<\/a>, <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/account-model-evolution\/\" target=\"_blank\" rel=\"noreferrer noopener\">Account model evolution<\/a>, <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/embedded-signup\/versions\" target=\"_blank\" rel=\"noreferrer noopener\">Embedded Signup versions<\/a>, <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/embedded-signup\/version-5\" target=\"_blank\" rel=\"noreferrer noopener\">Version 5<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Coexistence connects a number already in the WhatsApp Business app to the Cloud API without removing it from the app. Requirements, sync, webhooks and limits.<\/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-660","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>WhatsApp API Coexistence: App and API, One Number | Vectalk<\/title>\n<meta name=\"description\" content=\"WhatsApp coexistence: use the same number in the WhatsApp Business app and the Cloud API. Requirements, sync, webhooks, 20 mps limit and pricing.\" \/>\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-api-coexistence\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"WhatsApp API Coexistence: App and API, One Number | Vectalk\" \/>\n<meta property=\"og:description\" content=\"WhatsApp coexistence: use the same number in the WhatsApp Business app and the Cloud API. Requirements, sync, webhooks, 20 mps limit and pricing.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog Vectalk\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-29T13:11:31+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-29T13:11:46+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=\"11 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-api-coexistence\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-api-coexistence\\\/\"},\"author\":{\"name\":\"wanderleyfcunha\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/ff36ecd9d8257856f227f8e5d639db2b\"},\"headline\":\"WhatsApp coexistence: how to use the same number in the Business app and the official API\",\"datePublished\":\"2026-10-29T13:11:31+00:00\",\"dateModified\":\"2026-10-29T13:11:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-api-coexistence\\\/\"},\"wordCount\":1967,\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-api-coexistence\\\/\",\"url\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-api-coexistence\\\/\",\"name\":\"WhatsApp API Coexistence: App and API, One Number | Vectalk\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#website\"},\"datePublished\":\"2026-10-29T13:11:31+00:00\",\"dateModified\":\"2026-10-29T13:11:46+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/ff36ecd9d8257856f227f8e5d639db2b\"},\"description\":\"WhatsApp coexistence: use the same number in the WhatsApp Business app and the Cloud API. Requirements, sync, webhooks, 20 mps limit and pricing.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-api-coexistence\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-api-coexistence\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-api-coexistence\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"WhatsApp coexistence: how to use the same number in the Business app and the official API\"}]},{\"@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":"WhatsApp API Coexistence: App and API, One Number | Vectalk","description":"WhatsApp coexistence: use the same number in the WhatsApp Business app and the Cloud API. Requirements, sync, webhooks, 20 mps limit and pricing.","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-api-coexistence\/","og_locale":"en_US","og_type":"article","og_title":"WhatsApp API Coexistence: App and API, One Number | Vectalk","og_description":"WhatsApp coexistence: use the same number in the WhatsApp Business app and the Cloud API. Requirements, sync, webhooks, 20 mps limit and pricing.","og_url":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/","og_site_name":"Blog Vectalk","article_published_time":"2026-10-29T13:11:31+00:00","article_modified_time":"2026-10-29T13:11:46+00:00","author":"wanderleyfcunha","twitter_card":"summary_large_image","twitter_misc":{"Written by":"wanderleyfcunha","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/#article","isPartOf":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/"},"author":{"name":"wanderleyfcunha","@id":"https:\/\/vectalk.com.br\/blog\/#\/schema\/person\/ff36ecd9d8257856f227f8e5d639db2b"},"headline":"WhatsApp coexistence: how to use the same number in the Business app and the official API","datePublished":"2026-10-29T13:11:31+00:00","dateModified":"2026-10-29T13:11:46+00:00","mainEntityOfPage":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/"},"wordCount":1967,"articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/","url":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/","name":"WhatsApp API Coexistence: App and API, One Number | Vectalk","isPartOf":{"@id":"https:\/\/vectalk.com.br\/blog\/#website"},"datePublished":"2026-10-29T13:11:31+00:00","dateModified":"2026-10-29T13:11:46+00:00","author":{"@id":"https:\/\/vectalk.com.br\/blog\/#\/schema\/person\/ff36ecd9d8257856f227f8e5d639db2b"},"description":"WhatsApp coexistence: use the same number in the WhatsApp Business app and the Cloud API. Requirements, sync, webhooks, 20 mps limit and pricing.","breadcrumb":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-coexistence\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/vectalk.com.br\/blog\/"},{"@type":"ListItem","position":2,"name":"WhatsApp coexistence: how to use the same number in the Business app and the official API"}]},{"@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\/660","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=660"}],"version-history":[{"count":1,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts\/660\/revisions"}],"predecessor-version":[{"id":662,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts\/660\/revisions\/662"}],"wp:attachment":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/media?parent=660"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/categories?post=660"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/tags?post=660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}