How do you get the WhatsApp Business API?
You do not get the WhatsApp Business API through an application form at Meta. You create a Meta business portfolio, build an app on the WhatsApp Business Platform, register a phone number that you own and get your message templates approved. You can also go through a solution partner (a BSP, or business solution provider) who carries out those steps for you.
When people say "WhatsApp Business API" they usually mean Meta's Cloud API. It does not replace the WhatsApp Business app on your phone. It lets your own software, such as a CRM, an online shop or a chatbot, send and receive WhatsApp messages automatically. Meta's Cloud API getting-started guide sets out three main steps: create a Meta app with the WhatsApp use case, connect it to a messaging account and a phone number, then send a test message and set up a webhook. A Facebook or managed Meta account and a developer registration are enough to begin, and Meta gives you a temporary test number.
In short, "getting the API" means doing a setup, not signing a contract. The hard part is not clicking the buttons. It is deciding in advance which number to use, who your messages go to and with what permission, and how your templates will be written. This guide puts those decisions in order.
What are the steps from application to going live?
The table below summarises the order you would follow on your own and what to have ready at each step.
| Step | What you do | What to have ready |
|---|---|---|
| 1. Meta account | Register as a developer, create a business portfolio | Facebook account, company name, admin email |
| 2. App | Create a Meta app with the WhatsApp use case | App name, portfolio choice |
| 3. Phone number | Add, verify and register the number for the API | A number you own that can receive SMS or calls |
| 4. Business verification | Have Meta verify your company | Official company documents, website |
| 5. Templates | Create message templates and submit them for review | Categorised texts with sample values |
| 6. Webhook and testing | Connect incoming messages and statuses to your server | HTTPS address, software that logs events |
| 7. Go live | Add a payment method and send the first real messages | Opt-in records, payment method |
Business verification (step 4) is one of the routes to a higher sending limit and a larger template allowance; details follow below. You can start building with the test number straight away, prepare the verification documents in parallel and finish verification before launch. Keep the company name, tax details and the business name on your website consistent, because that makes the document check easier.
How do you choose the phone number?
The number must be yours, must have a country and area code (short codes are not supported) and must be able to receive a verification code by SMS or voice call. Meta's business phone numbers documentation lists these conditions and recommends a mobile number. It warns that landlines, freephone numbers and VoIP numbers can be unreliable for receiving codes by SMS.
Two details cause most of the trouble. First, you cannot register a number that is already used on WhatsApp for the API; you must delete that account first. Second, a number registered for the API can still be used for ordinary calls and SMS, but it cannot be used in the WhatsApp app. If you plan to move the number your customer service team uses today, plan what happens to old chats and devices beforehand. If you can, set aside a separate number for the API.
Solution partner (BSP) or direct Cloud API?
If you have a technical team, you can use the Cloud API directly. If you do not, a solution partner can take over the setup, template management and the screen your agents work in. The decision is usually less about price than about control: who holds the number, the templates and the customer conversations decides how hard it will be to change provider later.
- Direct Cloud API: No intermediary and control stays with you. Webhooks, security, template management and error monitoring are your responsibility. It is the easiest route if you want to connect your own CRM or an AI assistant.
- Through a solution partner: Setup and a dashboard come ready-made. In return you usually pay a service fee and your set-up depends on the partner.
- Questions to ask: Who owns the number and the templates? Can you move them if you leave? Does the partner pass on Meta's message price at cost, and what do they add on top?
If you go through a partner, the partner may also handle verification. Meta's messaging limits documentation says that for businesses onboarded by a partner, verification can be done by that partner.
How do message templates get approved?
You need a template whenever the business starts the conversation, or when the customer last wrote more than 24 hours ago. Templates are checked by automated systems and manual review. Meta's template review documentation says a decision can take up to 24 hours. An approved template can be sent; a rejected one can be edited and resubmitted, or you can appeal. To reduce rejections, check the following.
- Format parameters properly: Variables such as {{1}} and {{2}} must be sequential, a template must not start or end with a parameter, and every variable needs a sample value.
- Do not ask for sensitive data: Asking for full card or national ID numbers is a rejection reason; partial details such as the last four digits are accepted.
- Avoid threats: Wording that threatens a customer with legal action or public shaming is rejected.
- Avoid duplicates: A second template with the same body and footer is treated as a duplicate and rejected.
- Choose the right category: Every template must be marketing, utility or authentication. The category affects not only approval but also the price of the message, and mixed content that includes promotion can count as marketing.
Approval is not the end. If customers complain or read rates fall, a template can be paused or disabled. Watch template quality in WhatsApp Manager, and simplify or replace a low-rated template before complaints build up.
How do sending limits and pricing work?
A new business portfolio can reach 250 unique recipients in 24 hours outside a customer service window. According to Meta, you can raise that to 2,000 by verifying your business, or by reaching 2,000 people within 30 days using high-quality templates. Later increases come automatically when quality and usage conditions are met. The documentation also lists tiers of 10,000, 100,000 and unlimited.
On pricing, Meta's pricing page states that since 1 July 2025 charges are per message, only for delivered messages from a business to a user. Messages from users to your business are free. The price depends on the message category and the country code of the recipient. The same page says that from 1 October 2026 service messages are charged again, with each business phone number receiving 1,000 free service messages per month. Rates and rules change, so check the current list for recipients in Türkiye on that page. We give no figures here.
What should you watch on opt-in and data protection?
WhatsApp's policy allows you to contact people only if they have given you their phone number and have confirmed that they want to receive later messages (opt-in). The WhatsApp Business Messaging Policy says that choosing the opt-in method, and obtaining it in line with applicable law, is the business's responsibility, and that blocking and opt-out requests must be respected.
In Türkiye this may require assessing personal data protection (KVKK) and commercial electronic message rules alongside WhatsApp opt-in. The notice you give people should say why their phone number is kept and for how long. Settle this point with your legal adviser. If you plan to connect an AI assistant, the data protection side matters even more; our guide to KVKK and generative AI covers those questions.
Example: a clinic with three branches
For example, take a hypothetical clinic with 3 branches that wants to send appointment reminders on WhatsApp. Its booking system holds 1,800 patients, but only 1,100 agreed to receive messages when they booked. The clinic puts only those 1,100 people on the sending list.
Because a new portfolio is limited to 250, it can message 250 patients on day one and spreads the rest over the following days. It submits the reminder template as utility and a promotional announcement as marketing. Once business verification is complete, the limit rises to 2,000 and the 1,100-person list can go out in a single day. If a patient replies "cancel", that incoming message is free, and the clinic can answer in free text within the 24-hour window. These figures are hypothetical; work out the difference for your own list with your real data.
What are the most common mistakes?
- Trying to register a number already in use: The number must first be deleted from WhatsApp, and the team's chat history needs to be kept separately.
- Bulk sending without consent: Blocks and complaints lower quality and templates can be paused.
- Choosing the wrong category: A reminder that carries a promotion can count as marketing and changes the price.
- Leaving number ownership with the intermediary: The number and templates may not be portable when you leave a partner, so put it in the contract.
- Skipping the webhook: Incoming messages and delivery statuses arrive through the webhook, and unmonitored messages leave customers unanswered.
- Budgeting with a fixed figure: Category and service-message rules change, so check the current price list.
How Hatson Tech helps
Hatson Tech builds the software that connects a WhatsApp line to your CRM, your booking or order system and, where needed, an AI assistant. In our AI agent development service we work out with you which answers the assistant may give on its own, which topics it hands to a person and where records are stored. If needed, the model can run on your own servers. We do not publish fixed prices, and the first meeting and discovery are free.
Related reading: our articles on AI in customer service and AI agents.