{"id":796,"date":"2026-10-29T13:30:01","date_gmt":"2026-10-29T13:30:01","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/find-whatsapp-phone-number-id\/"},"modified":"2026-10-29T13:30:10","modified_gmt":"2026-10-29T13:30:10","slug":"find-whatsapp-phone-number-id","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/find-whatsapp-phone-number-id\/","title":{"rendered":"Where to find the Phone Number ID, WABA ID and App ID for the WhatsApp API"},"content":{"rendered":"\n

Updated on October 29, 2026<\/em><\/p>\n\n\n\n

Your WhatsApp Phone Number ID<\/strong> is shown in the API Setup<\/strong> section of your app in Meta’s App Dashboard, next to the Messaging account ID (the former WABA ID); the App ID<\/strong> sits in the toolbar at the top of the app dashboard. If you don’t have dashboard access, the API gives you everything: GET \/debug_token<\/code> returns the App ID and the Messaging account IDs a token can reach, and GET \/{waba-id}\/phone_numbers<\/code> lists the numbers with their IDs.<\/p>\n\n\n\n

This guide explains what each ID identifies, where to find it in Meta’s interface, how to get it from the Graph API, and where it lives in Vectalk.<\/p>\n\n\n\n

The three IDs (and why they’re not interchangeable)<\/h2>\n\n\n\n

People new to the official WhatsApp API<\/a> often mix up these IDs because they’re all long numbers with no prefix. Each one points to a different Graph API object:<\/p>\n\n\n\n

ID<\/th>What it identifies<\/th>Where you use it<\/th><\/tr><\/thead>
Phone Number ID<\/td>A phone number registered on the Cloud API<\/td>POST \/{phone-number-id}\/messages<\/code>, media, number registration, business profile<\/td><\/tr>
WABA ID (Messaging account ID)<\/td>The account that holds templates, billing and webhook subscriptions<\/td>GET\/POST\/DELETE \/{waba-id}\/message_templates<\/code>, GET \/{waba-id}\/phone_numbers<\/code>, webhook subscriptions<\/td><\/tr>
App ID<\/td>The app you created in Meta’s developer dashboard<\/td>Webhook configuration, Embedded Signup, token debugging<\/td><\/tr>
Business portfolio ID<\/td>The business in Business Manager<\/td>System users, assets and business verification<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The classic mistake is putting the WABA ID in the \/messages<\/code> path. The call fails because that object isn’t a phone number. The reverse also happens: trying to list templates with a Phone Number ID. If the acronyms are new to you, the WhatsApp API glossary<\/a> covers each one.<\/p>\n\n\n\n

What changed with the new WABA structure<\/h3>\n\n\n\n

Since September 23, 2026, Meta splits the WABA into two accounts (the migration was staged and, per Meta’s timeline, reaches all businesses by mid-October 2026): the WhatsApp account<\/strong>, which holds the phone number and profile, and the Messaging account<\/strong>, which holds templates, billing and webhooks. According to Meta’s WhatsApp Business account updates<\/a> page, existing WABA IDs stay the same and now denote Messaging account IDs. Phone Number IDs also keep working with every API.<\/p>\n\n\n\n

The WhatsApp account ID isn’t exposed yet: Meta plans that for a new Graph API version in the first half of 2027, and only from Phase 3 (first half of 2028) will endpoints that take the Phone Number ID in the path require that new ID instead. The details are in WhatsApp account vs. Messaging account<\/a>. So throughout this article, “WABA ID” and “Messaging account ID” mean the same number.<\/p>\n\n\n\n

Where to find them in Meta’s App Dashboard<\/h2>\n\n\n\n

These steps follow the Cloud API get-started guide<\/a>.<\/p>\n\n\n\n

    \n
  1. Go to developers.facebook.com\/apps<\/a> and open the app that uses the WhatsApp use case.<\/li>\n\n\n
  2. Open API Setup<\/strong> in the left-side menu (right after creating the app you land on Customize use case > Connect on WhatsApp > Quickstart<\/em>, and API Setup is in the menu on the left).<\/li>\n\n\n
  3. Once the app is connected to a Messaging account, the Messaging account ID<\/strong> is displayed in the API Setup panel.<\/li>\n\n\n
  4. In the same panel you pick the number in the From<\/strong> field to send a test message. Meta’s guide tells you to keep the phone number ID<\/strong> and the Messaging account ID<\/strong> from this step for later.<\/li>\n\n<\/ol>\n\n\n\n

    If you have more than one number, check which one is selected under From<\/strong> before copying: each number has its own Phone Number ID, and they can all belong to the same Messaging account.<\/p>\n\n\n\n

    App ID<\/h3>\n\n\n\n

    The App ID is generated when the app is created. Meta’s App Dashboard documentation<\/a> says the toolbar at the top of the dashboard, once you select an app, displays the App ID and lets you switch between apps. Settings are split into Basic<\/strong> and Advanced<\/strong>; Basic is where you find the App Secret, which you use to validate webhook signatures. The App ID can appear in front-end code (in Embedded Signup, for example); the App Secret never should.<\/p>\n\n\n\n

    Where to find them in Business Settings<\/h2>\n\n\n\n

    If you’re not a developer on the app but you are a business admin, use Business Manager. Meta’s system users<\/a> page says:<\/p>\n\n\n\n