If your customers already message you on WhatsApp, the WhatsApp Business API is the step that turns a phone in someone’s pocket into a system the whole team can run. The free WhatsApp Business app works well for one person answering chats. The API is what lets several team members share one number, lets a chatbot answer the routine questions, and lets your shop send order updates automatically.
Setting it up is not difficult, but it is a process with a fixed order. Skip a step and you will find yourself locked out of your own number for days, or paying for a platform before Meta has approved anything. This guide walks through the whole setup for a business in Pakistan, in the order that works, with the two routes you can take and the mistakes that catch most people out.
What the WhatsApp Business API actually is
The WhatsApp Business API, which Meta now calls the WhatsApp Business Platform, is the official way for a business to connect its own software to WhatsApp. Your messages travel through Meta’s hosted Cloud API. There is no phone that has to stay switched on and no unofficial app doing the work in the background.
One change matters more than any other in 2026. Meta retired the self-hosted On-Premises API on 23 October 2025. The Cloud API is now the only supported way to run the WhatsApp Business Platform. If a provider still offers you an on-premises setup, or a tool that logs in with a QR code like a second phone, that is not the official API. Walk away from it, because Meta can block numbers that use unofficial tools, and there is no appeal that reliably brings them back.
The API itself is not an inbox. It is a connection. You still need somewhere to read and reply to messages, which is either a provider platform such as WATI or respond.io, or software your own developers build. Digilistan builds that layer for clients, including chatbots and the inbox itself, on our AI chatbots and WhatsApp bots service page, but this guide covers the setup itself, which is the same whichever route you take. If you are still deciding between the app and the API, our comparison of the two explains which one your business actually needs.
Before you start: the five things you need
Gather these before you touch any signup form. Every one of them is checked at some point in the flow, and missing one halfway through is how a same-day setup turns into a two-week delay.
A Meta Business Portfolio. This used to be called Business Manager. It is the account in Meta Business Suite that owns your WhatsApp Business Account, your pages and your ad accounts. Create it with your legal business name, a business email you control, and your website. Meta will ask you to verify the business by submitting registration documents. Business verification is not required to start testing, but it is required to unlock higher messaging limits and certain template categories, so start it early and let it run in parallel.
A phone number that can receive a code. The number must be owned by your business, must have a country and area code, and must be able to receive an SMS or a voice call, because Meta verifies it with a one-time code. Short codes are not supported. A Pakistani +92 number works the same as any other number here. If the number is already registered on WhatsApp or the WhatsApp Business app, you will generally need to remove it from the app first, unless you use coexistence, which is covered below.
A display name. This is the name customers see in the chat header. Meta reviews it, and it should match your business. Do not add a city, a slogan or a phone number to it. A display name that does not match your business documents is one of the commonest reasons a setup stalls.
A payment method on the account. Meta charges per delivered message, and the account needs a payment method attached before it will send at volume. This is easy to forget because testing works without one. The first time you try to send properly, a missing payment method stops delivery outright. Add it during setup, not after launch.
A plan for who answers. The API does not answer messages by itself. Decide before you go live whether your team will reply in a provider inbox, whether a chatbot handles the first reply, or both. A number that goes live with nobody watching the inbox is worse than a number that is not live yet.
The two routes to set it up
There are two legitimate ways to connect a number to the Cloud API. They end in the same place. The difference is how much of the technical work you do yourself.
Route one: Embedded Signup through a provider. This is the route most small businesses should take. You create an account with a Business Solution Provider, a BSP, and start Meta’s Embedded Signup flow from inside that platform. A Meta window opens, you sign in with your Facebook or Meta Business account, accept the Cloud API and WhatsApp terms, pick an existing business portfolio or create one, and connect or create a WhatsApp Business Account and register the number. The provider handles the token, the webhook and the number checks. In practice the whole flow takes minutes once your documents are ready.
Route two: direct integration in the Meta developer dashboard. This is the route for businesses with their own developers. You create an app in the App Dashboard, pick the “Connect with customers through WhatsApp” use case, and select or create a business portfolio. Meta gives you a test account and a test phone number with relaxed limits, and a temporary token so you can send a test message. Then you add your real number in WhatsApp Manager, confirm ownership with the SMS or voice code, enter your display name, and register the number on the Cloud API with a six-digit two-step verification PIN. Keep that PIN safe. You need it to change the PIN or to delete the number from the platform later.
If you have no developers in-house, take route one. The direct route saves the provider’s monthly fee, but you take on the webhook, the token management and the number monitoring yourself, and that work does not stop after setup day.
Step by step: Embedded Signup
- Choose a provider and create an account with it. Check that it is a Meta-authorised partner and that you stay the admin of your WhatsApp Business Account in Business Manager. That last point matters. If the provider owns your account, leaving them later means starting over.
- Start Embedded Signup from inside the provider’s dashboard and sign in as the portfolio admin.
- Create or select your business portfolio, then create or select your WhatsApp Business Account.
- Add your phone number and verify it with the SMS or voice code.
- Submit your display name for review.
- Complete Meta business verification, submitting the documents that match your legal name. Verification typically takes one to three business days, though some cases take longer.
- Attach a payment method to the account.
- Submit your first message template for approval, then send a test message to your own number before you tell customers anything is live.
Step by step: direct Cloud API setup
- In the Meta App Dashboard, create an app and choose the “Connect with customers through WhatsApp” use case, selecting your business portfolio.
- Use the test number Meta creates to send a test message with the temporary token. This confirms your code works before your real number is involved.
- In WhatsApp Manager, add your real number and confirm ownership with the SMS or voice code, then enter your display name.
- Register the number on the Cloud API. This is a separate step from verifying it, and it needs the six-digit two-step verification PIN. Meta limits this endpoint to 10 requests per number in 72 hours. Past that, the API returns error 133016 and blocks new attempts for 72 hours, so do not hammer the button if a code fails. Wait, check the number, and try again calmly.
- Set up your webhook endpoint on a secure HTTPS address so Meta can deliver inbound messages and delivery statuses to your system.
- Complete business verification and attach a payment method.
- Submit a template and send your first real message.
Keeping your existing number: coexistence or migration
This is the decision most Pakistani businesses get wrong, because the number customers already know is usually the number on the WhatsApp Business app.
If your number is already on the WhatsApp Business app, you have two options. The first is the standard migration: remove the number from the app, then register it on the API. Your chat history on the phone stays on the phone, but the app stops working on that number. The second option is Meta’s coexistence feature, which lets the same number run in the WhatsApp Business app and on the API at the same time, with roughly six months of chat history synced across. Coexistence needs the WhatsApp Business app on version 2.24.17 or later, and a number running coexistence is capped at a fixed throughput of 20 messages per second, which is well below what a dedicated API number can reach.
For a shop that still takes orders by hand in the app, coexistence is usually the right start. For a business that has outgrown the app and wants automation to run the show, a dedicated API number is the cleaner long-term choice. Either way, read our full guide to using the Business app and the API on the same number before you decide, because the choice is hard to reverse once customers are used to it.
Business verification and messaging limits
Messaging limits are the part of the setup that surprises people most, because they are generous at the start and invisible until you hit them.
Since 7 October 2025, Meta applies messaging limits at the Business Portfolio level instead of per phone number. If your business has an approved display name and is verified, you now start at 2,000 conversations instead of the earlier 1,000. That is the starting tier. Higher tiers unlock as your messaging quality stays good and your volume grows, which is why business verification is worth doing properly the first time. A rejected verification with documents that do not match your legal name costs you days, and the fix is always the same: documents that match, submitted once, correctly.
Your display name also has to be approved. Submit the name your customers already know you by, exactly as it appears on your business documents. Creative spellings and extra words are the usual reason a display name comes back refused.
Templates: your first message
The API does not let you send any message you like to any customer at any time. Messages your business starts, such as an offer or a reminder, must use an approved template. Replies inside an open conversation are free-form, which is why the first reply matters so much.
Submit your templates early, while verification is running, so they are approved by the time you go live. Start with one utility template, such as an order confirmation or a delivery update, because utility templates are the messages customers actually want. Marketing templates have their place, but a business that opens with promotions and no useful messages trains its customers to ignore it. Keep the wording plain, keep it short, and write it the way your staff actually speak to customers.
What it costs
There is no licence fee from Meta itself. What you pay has two parts: Meta’s per-message fee and your provider’s platform fee if you use one.
On Meta’s rate card effective 1 October 2026, a marketing message to a Pakistani number costs $0.0473, and a utility, authentication or service message costs $0.0150. The first 1,000 service messages per number per month are free, and you only pay for messages that are delivered. Platform fees vary by provider and by plan. Our full breakdown of what a WhatsApp chatbot costs in Pakistan works through the real monthly bill, including a worked example, so read that before you budget.
One cost people forget is the payment method itself. Meta stops delivery when there is no payment method on file, even if the account is otherwise ready. If your first campaign silently fails, check the payment method before you check anything else.
Mistakes that stall a setup
Registering a number that is still active on WhatsApp. Remove it from the app first, or use coexistence. Trying to register an active number just burns your registration attempts.
Using an unofficial tool. Any tool that logs in with a QR code like a second phone is not the Cloud API. It can get the number blocked, and there is no reliable way back.
Letting the provider own your account. Stay the admin of your WhatsApp Business Account. If you ever change provider, you keep your number, your history and your templates.
Losing the two-step PIN. Without it you cannot move or delete the number. Store it where the business keeps its other credentials, not in one person’s phone.
Going live with no one watching the inbox. The first week sets the tone. If customers message and nobody replies, they will not message a second time.
Submitting templates on launch day. Template approval takes time. Submit them while verification is running.
What to do once you are live
Setup is the beginning, not the finish. The three moves that pay off first are usually these. Set up a WhatsApp Business catalog so customers can browse and order without leaving the chat. Add a chatbot for the questions your team answers ten times a day, such as prices, timings and delivery areas, and keep a human on the replies that need judgment. And connect your other channels, so the same customer who finds you on Google or Instagram can reach you on WhatsApp in one tap. Our AI automation service covers the chatbot and the workflows behind it, and the catalog guide walks through the shop setup step by step.
If the setup still feels like a lot to take on, that is normal. It is a one-time job with a fixed order, and once it is done, the number just works. Digilistan sets up the WhatsApp Business API, the inbox and the chatbot for businesses in Pakistan, the United Kingdom and the United States. Talk to us through the contact page and we will take the setup off your list.
