Updated on October 25, 2026
To get access to the official WhatsApp Business API, you need a Meta business portfolio, a WhatsApp account with a phone number registered on Cloud API, a Messaging account with a payment method, and an app (yours or a provider’s) with permission to use those assets. There are two paths: integrate directly through Meta’s developer dashboard, or go through a provider’s Embedded Signup, which creates everything in a few screens. There is no approval queue to “unlock the API”; what takes time is verifying your business and getting the number ready.
This guide covers what to prepare, both paths step by step, and the most common blockers.
What you need before you start
| Item | What it’s for | Note |
|---|---|---|
| Business portfolio (Meta Business Suite) | Groups accounts, numbers, users and payment | Required to use the platform |
| WhatsApp account | Holds the number, display name and profile | Under the 2026 account model, separate from the Messaging account |
| Messaging account (formerly WABA) | Holds templates, billing and webhook subscriptions | The waba_id still works as its ID |
| Phone number | Sends and receives messages | Must be able to receive SMS or a voice call |
| Business-type Meta app | Makes the API calls | Yours (direct integration) or the provider’s |
| Payment method | Pays for delivered messages | Attached to the Messaging account, unless the provider invoices you |
Sources: About the platform and Updates to WhatsApp Business accounts.
Phone number requirements
According to the business phone numbers documentation, the number must:
- be owned by your business;
- have a country and area code (short codes are not supported);
- be able to receive a voice call or SMS for the verification code.
Numbers already in use on WhatsApp can only be registered after they are deleted from the app. The exception is a WhatsApp Business app number, which can move to the API without leaving the app through coexistence. If the number is on regular WhatsApp, see how to free up a number for the API. Landlines and toll-free numbers are accepted too, as long as they can receive the verification call, including when there is an IVR.
Path 1: direct integration with Meta
This is the path for teams with their own developers who will use the API only for their own business. The steps follow Meta’s Get started guide.
- Create the app. In the App Dashboard, create an app and pick the “Connect with customers through WhatsApp” use case. During setup, select an existing business portfolio or create one.
- Use the test resources. Meta automatically creates a test account and a test phone number. They have relaxed limits and don’t need a payment method to send templates.
- Send your first message. In WhatsApp > API Setup, generate a temporary token and send a test message. That token expires quickly and is only for this first contact.
- Set up the webhook. Enter your callback URL and verify token in WhatsApp > Configuration and subscribe to the
messagesfield. Without a webhook you don’t receive messages or statuses. - Create a permanent token. In Business settings > System users, create a system user, give it access to the app and accounts, and generate a token with
business_management,whatsapp_business_managementandwhatsapp_business_messaging. Details in permanent token. - Add your real number. In WhatsApp Manager, add the number to the account and confirm ownership with the SMS or voice code. This is where you enter the display name.
- Register the number on Cloud API. Adding and verifying are not enough: registration is an API call with a six-digit two-step verification PIN.
- Add a payment method. In Billing Hub, attach a payment method to the Messaging account.
- Create and approve templates. Outside the 24-hour window, only approved templates can be sent.
Step 7 looks like this:
curl 'https://graph.facebook.com/v26.0/YOUR_PHONE_NUMBER_ID/register' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR_SYSTEM_USER_TOKEN' \
-d '{
"messaging_product": "whatsapp",
"pin": "212834"
}'If the number doesn’t have two-step verification yet, the PIN you send becomes its PIN. Keep it safe: you need it to change the PIN or delete the number from the platform. The registration page limits this endpoint to 10 requests per number in 72 hours; beyond that, the API returns error 133016 and blocks new attempts for 72 hours.
To confirm it worked, check the number’s status. It must be CONNECTED to send and receive:
curl 'https://graph.facebook.com/v26.0/YOUR_PHONE_NUMBER_ID?fields=status,verified_name,quality_rating' \
-H 'Authorization: Bearer YOUR_SYSTEM_USER_TOKEN'Path 2: through a provider, with Embedded Signup
Providers (Solution Partners and Tech Providers, explained in what a BSP and a Tech Provider are) offer Embedded Signup, a Meta window launched from the provider’s website. In it, the business:
- logs in with its Facebook or Meta Business account;
- accepts the Cloud API, WhatsApp Business and Meta terms;
- picks an existing business portfolio or creates one;
- picks an existing WhatsApp account or creates one;
- enters and verifies the phone number;
- sets the display name;
- authorizes the provider’s app to access those assets.
When it finishes, Meta returns the waba_id, the phone_number_id and a code that the provider exchanges for a token scoped to that client. The provider then registers the number, subscribes to webhooks and, if it is a Solution Partner, shares its credit line.
The next step depends on the provider type. With a Solution Partner (or a partner of one), the business can start messaging right away. Otherwise, it must attach a payment method to the Messaging account first.
The assets created belong to the business’s portfolio, and the business keeps full access to WhatsApp Manager. The provider cannot restrict that access.
Direct or through a provider: comparison
| Direct integration | Through a provider | |
|---|---|---|
| Who creates and maintains the Meta app | You | The provider |
| Access credential | System user token from your portfolio | Defined by the provider, which holds the Meta token |
| Webhook | One endpoint per app, configured by you | Configured by the provider |
| Number registration | You call /register | The provider does it during onboarding |
| Paying Meta | Your payment method | Your payment method or the provider’s invoice, depending on the model |
| Coexistence with the Business app | Meta requires a Solution Partner or Tech Provider | Available if the provider offers it |
| Initial technical effort | App, token, webhook and registration are on you | Complete signup and integrate with the provider’s API |
The WhatsApp Business FAQ sums up the choice: direct access is for businesses with in-house developers, and the partner route serves those who don’t build software or want to connect WhatsApp to tools such as an inbox, CRM or chatbot.
Business verification and display name
Verification isn’t required to start, but it changes what you can do:
- Messaging limit. New portfolios start at 250 unique recipients per 24 hours outside the customer service window. Verifying your business is one of the paths to 2,000 (messaging limits).
- Phone numbers. New portfolios can register two numbers; with verification or after reaching the 2,000 limit, the cap rises to 20.
- Templates. Messaging accounts in unverified portfolios can have up to 250 templates; verified ones with an approved display name can have up to 6,000.
The display name is entered at registration and automatically reviewed when your messaging limit goes up. You can change it up to 10 times every 30 days. Rules and rejection reasons are in display names on the WhatsApp API.
Payment method
Meta charges per delivered message, based on category and the recipient’s country. Since October 1, 2026, each number gets 1,000 free service messages per month, and the pricing page warns that, without a payment method, service messages stop being delivered after that free tier.
Businesses whose billing country is Brazil can have Messaging accounts in Brazilian reais (BRL), invoiced by Facebook Brasil, Meta’s local entity. Meta requires those businesses to move all their Messaging accounts to BRL by June 30, 2027.
Most common blockers
| Symptom | Likely cause | What to do |
|---|---|---|
| Number won’t register | It’s still on WhatsApp or the Business app | Delete the app account or use coexistence through a provider |
Error 133016 | More than 10 registration attempts in 72 hours | Wait 72 hours |
Error 133010 when sending | Number added but not registered | Call /register with the PIN |
Error 200 on client accounts | App without Advanced access | Complete App Review (only for those serving other businesses) |
Error 131042 | Payment method problem | Check the payment method on the Messaging account |
Error 190 | Expired token | Replace the temporary token with a system user token |
Sources: error codes and number registration.
How to do it with Vectalk
With Vectalk, access follows Path 2, and Vectalk takes care of the app, the Meta tokens and webhook routing:
- Create your account at apps.vectalk.com.br/register.
- In Instances, click Connect account and complete Embedded Signup. Vectalk imports the
phone_number_id, thewaba_idand the Meta token. - In Settings → API Tokens, generate an organization or instance token.
- Send your first message with
POST /api/messagesand register a webhook withPOST /api/webhooks.
The quickstart requires a verified Meta Business account to connect the number. For billing, you pay Vectalk and Vectalk pays Meta, with no card on file at Meta. Vectalk also supports coexistence to keep the number on the WhatsApp Business app. To see the first sends in code, read how to send a message with the WhatsApp API.
Frequently asked questions
Does Meta need to approve my API access?
There is no blanket approval to “unlock the API”. For your own use, you create the app, register the number and add a payment method. App Review with advanced access is required for providers, which access accounts owned by other businesses. What Meta does review is your business (verification), your display name and each template.
Can I test without paying?
Yes, with the test resources Meta creates along with the app: a test account and test number that can send templates without a payment method on file. For production with your own number, a payment method becomes necessary.
Can I use the number that’s already on my phone?
If it’s on the WhatsApp Business app, yes, through coexistence, which requires a provider. If it’s on regular WhatsApp, you need to delete the app account before registering the number on Cloud API.
How long does it take?
The technical part can be done the same day. Business verification, display name review and template approval depend on Meta, so start with those.
Can I still use the On-Premises API?
No. Meta sunset the On-Premises API on October 23, 2025; numbers can only be registered on Cloud API. See what the WhatsApp Cloud API is.
Official sources consulted on October 25, 2026: Get started, About the platform, Business phone numbers, Register a business phone number, Embedded Signup, Access tokens, Messaging limits, Display names, Templates, Pricing, Error codes, Updates to WhatsApp Business accounts, On-Premises API Sunset, WhatsApp Business FAQ.