{"id":650,"date":"2026-10-29T13:10:08","date_gmt":"2026-10-29T13:10:08","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/official-whatsapp-api\/"},"modified":"2026-10-29T13:10:23","modified_gmt":"2026-10-29T13:10:23","slug":"official-whatsapp-api","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/official-whatsapp-api\/","title":{"rendered":"Official WhatsApp API: the complete guide (2026)"},"content":{"rendered":"\n

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

The official WhatsApp API is Meta’s WhatsApp Business Platform, offered today as the WhatsApp Cloud API: an HTTP API hosted by Meta that lets your systems send and receive WhatsApp messages. To use it you need a Meta business portfolio, a phone number registered on the platform, approved templates to start conversations and a way to pay, since Meta charges per delivered message. It’s the only route Meta authorizes for automating a company’s WhatsApp.<\/p>\n\n\n\n

This guide covers what separates the official WhatsApp Business API from unofficial libraries, the requirements, how to choose between integrating directly with Meta or going through an intermediary, what it costs in broad terms and when switching is worth it.<\/p>\n\n\n\n

What the official WhatsApp API is<\/h2>\n\n\n\n

The WhatsApp Business Platform is the set of APIs Meta makes available to businesses. In practice, when people say “official WhatsApp API” today they mean the Cloud API<\/strong>: Graph API endpoints (graph.facebook.com<\/code>) that take JSON and return JSON, plus webhooks that notify your server when a message arrives or the status of a sent message changes.<\/p>\n\n\n\n

A few terms show up all the time in Meta’s documentation. It helps to know them before you start:<\/p>\n\n\n\n

Term<\/th>What it is<\/th>Where it appears<\/th><\/tr><\/thead>
Business portfolio<\/td>Your company’s account at Meta (formerly Business Manager). It can be verified.<\/td>business_id<\/code><\/td><\/tr>
WhatsApp Business Account (WABA)<\/td>Since September 23, 2026, Meta splits it into a WhatsApp account (the phone number) and a Messaging account (templates, billing, webhooks). Old IDs and endpoints keep working during the transition.<\/td>waba_id<\/code><\/td><\/tr>
Business phone number<\/td>The number registered on the Cloud API, used to send and receive.<\/td>phone_number_id<\/code><\/td><\/tr>
Template (message template)<\/td>A pre-approved message, required to start contact outside the customer service window.<\/td>type: \"template\"<\/code><\/td><\/tr>
Customer service window<\/td>A 24-hour period opened by each customer message, during which you can reply with free-form messages.<\/td>sending and pricing rules<\/td><\/tr>
Webhook<\/td>A URL on your system that receives events (incoming messages, delivery statuses).<\/td>object: \"whatsapp_business_account\"<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The account split is explained step by step in WhatsApp account vs Messaging account: the new WABA structure<\/a>.<\/p>\n\n\n\n

Official API vs unofficial API<\/h2>\n\n\n\n

Libraries such as Baileys and WPPConnect, and tools built on them (such as Evolution API’s Baileys mode), work by emulating WhatsApp Web: you scan a QR code with your phone and the software takes over that session. There’s no agreement with Meta, no templates and no per-message billing. There’s also no guarantee the next WhatsApp update won’t break the integration.<\/p>\n\n\n\n

The WhatsApp Terms of Service<\/a> prohibit accessing or using the service through automated means that aren’t authorized, and creating accounts “through unauthorized or automated means.” They also list bulk messaging and auto-messaging among impermissible communications. That’s why numbers used with unofficial APIs can be banned without warning.<\/p>\n\n\n\n

Criterion<\/th>Official API (Cloud API)<\/th>Unofficial API (Baileys, WPPConnect, etc.)<\/th><\/tr><\/thead>
Authorized by Meta<\/td>Yes, it’s Meta’s product for businesses<\/td>No; it goes against the Terms of Service<\/td><\/tr>
Connection<\/td>Access token and HTTP calls<\/td>WhatsApp Web session via QR code<\/td><\/tr>
Ban risk from the tool itself<\/td>No; risk comes from quality and policy<\/td>High and unpredictable<\/td><\/tr>
Starting a conversation<\/td>Only with an approved template<\/td>Free-form message (and that’s where the risk is)<\/td><\/tr>
Message cost<\/td>Per delivered message, Meta’s rate card<\/td>No Meta charges<\/td><\/tr>
Stability<\/td>Versioned, with a changelog and deprecation dates<\/td>Depends on reverse engineering<\/td><\/tr>
Webhooks<\/td>Format documented by Meta<\/td>Each library’s own format<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Worth noting: Evolution API also offers an integration with the official Cloud API, besides its Baileys-based mode. What defines the risk is the channel, not the tool’s name. If that’s your situation, How to migrate from an unofficial API to the official WhatsApp API<\/a> has the step by step, and Official vs unofficial WhatsApp API<\/a> goes deeper into the ban risk.<\/p>\n\n\n\n

Requirements to use the official API<\/h2>\n\n\n\n

A business portfolio at Meta<\/h3>\n\n\n\n

Everything on the platform starts from a business portfolio. That’s where your WhatsApp and Messaging accounts, numbers, system users and payment method live.<\/p>\n\n\n\n

Business verification<\/h3>\n\n\n\n

Verification isn’t required for your first steps, but it changes what you can do. According to Meta’s messaging limits documentation<\/a>, new portfolios start with a limit of 250 unique recipients per rolling 24 hours outside the customer service window. Verifying the business is one of the ways to move up to 2,000 (the others are having your partner verified, or delivering 2,000 messages outside the window to unique numbers within 30 days with high-quality templates). The limit on registered numbers depends on it too: new portfolios can register two numbers, and the cap rises to 20 once the business is verified or reaches the 2,000 limit.<\/p>\n\n\n\n

In Vectalk’s flow, the quickstart<\/a> asks for a verified Meta Business account to connect the number. So treat verification as part of the project, not an optional step. Our guide to Meta business verification<\/a> covers the process.<\/p>\n\n\n\n

Phone number<\/h3>\n\n\n\n

Per Meta’s business phone numbers documentation<\/a>, the number must:<\/p>\n\n\n\n