WhatsApp Business API vs connecting your own number
Two ways to send WhatsApp from software, and they are not competing versions of the same thing. One is a Meta product with per-conversation pricing and a template approval queue; the other is the account already on your phone. Which one is right depends on whether you are broadcasting or replying.
There are two ways to send WhatsApp messages from software, and they are not two versions of the same product. One is a Meta product you apply for, pay per conversation, and submit message wording to for approval. The other is the account already on somebody’s phone, connected the same way WhatsApp Web connects.
Nearly every comparison of the two is written by somebody selling one of them. Here is the version that admits what each is bad at, because the honest answer is that they suit different businesses and a fair number of businesses want both.
What the official API actually is
The WhatsApp Business Platform — the Cloud API — is Meta’s product for sending at scale. You register a business, verify it, attach a phone number that is then owned by the platform rather than by a handset, and send through an HTTP API.
Three things follow from that, and they are the whole story:
- You pay per conversation, not per message. A 24-hour window opens when a conversation starts, and messages inside it are free. The price depends on who opened it and why — marketing costs more than a service reply, and rates vary by country, sometimes by an order of magnitude.
- You cannot start a conversation in your own words. Outside that 24-hour window you may only send a pre-approved template. You submit the wording, it is reviewed, and you use it as approved. This is the part that surprises people most.
- The number stops being a phone. Once a number is on the platform it is not in the WhatsApp app any more. Nobody on your team opens it and replies from the sofa; everything goes through whatever software you have connected.
The template queue is the real cost, and it is not measured in money. A business that wants to say something slightly different this week either has a template for it or waits for review. If your messages are genuinely repetitive, that is fine. If they are conversations, it is a poor fit.
What connecting your own number is
The alternative is to connect the WhatsApp account you already use, through the same multi-device mechanism that powers WhatsApp Web and the desktop app. Your software holds a session the way a second laptop would.
The consequences are the mirror image:
- No per-conversation fee to Meta. You pay your software vendor, and that is the bill.
- No templates and no approval queue. You write what you want to write, because the account is a normal account.
- The number stays a phone. Your team can still open WhatsApp and answer. This matters more than it sounds — it is the difference between software people adopt and software they route around.
- Nothing protects you from yourself. There is no rate limiter between you and a ban. Sending badly gets the number restricted, and the number is one your customers already have.
The comparison, without the sales pitch
| Official Cloud API | Your own connected number | |
|---|---|---|
| Cost model | Per conversation, varies by country and category | Flat software fee |
| Starting a conversation | Approved templates only, outside 24h | Anything you can type |
| Approval delay | Hours to days per template | None |
| Team can use the phone | No — the number leaves the app | Yes |
| Green tick verification | Possible | No |
| Ban exposure | Policy enforcement, appeal process | Ordinary account rules apply |
| Volume ceiling | High, tiered by quality rating | Whatever an account sustains |
| Good for | Notifications at scale, OTPs, large catalogues | Sales and support conversations |
How to choose, in one question
Are you broadcasting, or replying?
If most of your messages are generated by a system and sent to people who are expecting them — delivery updates, one-time codes, appointment reminders at real volume — the official API is built for exactly that, the per-conversation cost is predictable, and templates are not a constraint because the wording does not change.
If most of your messages are a person answering a question, the template queue is friction on every single interaction, and you are paying per conversation for the privilege. A connected number is closer to what you are actually doing.
Plenty of businesses end up with both: the official API for transactional sends, and a connected number that the sales team actually talks on. These are not mutually exclusive, and treating the choice as permanent is the mistake.
The part nobody writes down
Whichever you pick, the thing that determines whether the number survives is not the integration. It is whether people want your messages.
WhatsApp’s enforcement runs on signals from recipients — blocks, reports, and the absence of replies. A number on the official API with a poor quality rating gets its sending limits cut. A connected number in the same position gets restricted. The mechanism differs; the cause does not.
Which means the questions worth asking a vendor are about restraint, not throughput: does it pace sends, does it stop a campaign that is being blocked, does it know the difference between a message that failed and one that was merely accepted. We wrote about that last one here, and about what to do when it has already gone wrong on this page.
Where WaveSenda sits
WaveSenda connects the number you already have. That is a deliberate choice for the second column of that table — businesses whose WhatsApp is a conversation, who want a team answering it, a website widget feeding it and an agent handling the easy half. If you need approved templates going to two million people, we are the wrong tool and the official API is the right one.
Common questions
Is connecting my own number against WhatsApp’s terms?
Multi-device sessions are the same mechanism WhatsApp Web and the desktop app use, and an account connected that way is an ordinary account subject to ordinary rules. What gets accounts restricted is behaviour: messaging people who did not ask, sending faster than a human could, and accumulating blocks and reports. That is true whichever route you take.
Can I move to the official API later?
Yes, but not for free. Migrating a number to the Business Platform removes it from the WhatsApp app, so your team stops being able to answer from a handset, and your chat history does not come with it. It is a one-way door in practice, which is why it is worth being sure you are broadcasting before you walk through it.
How much does the official API cost?
Meta prices per 24-hour conversation, by category and by country, and the rates change. Marketing conversations cost several times a service conversation, and a market like India or Brazil differs sharply from the US. Check Meta’s current rate card for your countries rather than any figure quoted in an article, including this one.
Do I get the green verified badge either way?
Only through the official platform, and only after Meta approves your business as notable enough. Most small businesses do not get it on either route, and it has no effect on deliverability — it is a trust signal to the person reading, not a sending privilege.
What happens to my existing chat history?
Connecting your own number keeps it: the account is unchanged and the history is where it was. Moving a number onto the official platform does not bring it across, which for a business with years of customer conversations on that number is often the deciding factor.