WhatsApp Business Platform vs unofficial APIs: the fork in the road

There are two ways to send WhatsApp messages programmatically, and they are not two options on a spectrum. One is the WhatsApp Business Platform, which Meta operates and supports. The other is a category of libraries that automate WhatsApp Web or reimplement the client protocol, which violate WhatsApp's Terms of Service and result in numbers being banned.

The second is cheaper, faster to start and has no approval process, which is why it keeps being chosen. What it actually costs is the number — and for most businesses the number is the asset, because customers have it saved.

What we'll cover

• Two genuinely different things
• What the Terms of Service say
• What a ban actually costs
• Building it with CodeWords
• What the official platform requires
• What it costs to run
• The constraints people object to
• When the Business App is enough
• Migrating a number that is already in use
• Making it survive
• Limits worth knowing about
• What to do first
• Frequently asked questions

Two genuinely different things

The WhatsApp Business Platform is Meta's official product, accessed through the Cloud API directly or through a Business Solution Provider.

The WhatsApp Business App is the free phone application for small businesses, operated by a person rather than by software.

Unofficial libraries drive WhatsApp Web through a browser or reimplement the client protocol, presenting as an ordinary user.

Modified clients — the various renamed WhatsApp builds — are a related category and are explicitly prohibited.

Only the first is a supported integration. The rest either involve a person or involve pretending to be one.

The distinction is not about capability, it is about whether Meta knows and permits what you are doing.

What the Terms of Service say

Automating the consumer client is prohibited. WhatsApp's terms address unauthorised access and automated use directly.

Modified and unofficial clients are named specifically in WhatsApp's own guidance as a violation that results in bans.

Detection is active rather than incidental, and the behavioural signals — message rate, contact patterns, client fingerprints — are what identify automation.

Bans are frequently permanent, and the appeal route for a consumer account is limited.

A Business Platform account has a different relationship, with a quality rating, a defined appeal process and a business support path.

"It has worked so far" is not evidence of permission, only of not having been caught yet.

What a ban actually costs

The number is the asset. Customers saved it, printed it, and have it in their phones from previous conversations.

Conversation history is gone, including everything the business relied on as a record.

Changing numbers is not a small operation. Every listing, sign, invoice, business card and customer's contact list is now wrong.

The replacement number starts cold, with no history and a fresh quality position.

It happens without warning in most accounts, and typically at the point where volume has grown enough to matter.

Weigh it against the saving, which is the actual comparison rather than the monthly fee.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which messages, in response to what, and what routes to a person.
3. Authorize the connection to your WhatsApp Business Platform account and to the systems the conversation needs.
4. Describe the exceptions: a message outside the customer service window, a template not yet approved, somebody asking for a person.
5. Run it against your own number first and read every message it produces before it reaches a customer.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

What the official platform requires

A Meta Business Portfolio and business verification, which takes documentation and time.

A phone number not currently registered to a consumer WhatsApp account, which frequently means a new one.

A display name subject to approval against Meta's naming rules.

Approved message templates for anything you send outside an open customer service window, reviewed by category.

Opt-in, obtained and recorded, before messaging somebody.

A provider decision: directly with Meta's Cloud API, or through a Business Solution Provider that adds tooling and its own margin.

What it costs to run

Pricing is per message for template messages, a model Meta moved to in July 2025 from the previous conversation-based charging.

Rates vary by template category and by country, and the categories — marketing, utility, authentication — are priced differently.

Further changes are scheduled. Meta has announced changes taking effect in October 2026 affecting service messages and utility templates inside the service window.

Check Meta's current pricing documentation rather than any figure in an article, including this one, because this has changed more than once and is changing again.

A provider adds its own fee on top, which is worth comparing separately from the Meta cost.

Budget for the messages you will actually send, which is usually dominated by one template nobody predicted.

The constraints people object to

The customer service window. Free-form replies are available for 24 hours after a customer messages you; outside it you need an approved template.

Template approval takes time and templates can be rejected, which makes rapid iteration on outbound copy harder.

No group messaging. The Business Platform does not support sending to groups, which surprises people planning community features.

Opt-in requirements mean you cannot message a list you obtained elsewhere.

Messaging limits start low and increase with demonstrated quality rather than with need.

Every one of these exists because of what unofficial automation did to the channel, which is worth understanding rather than resenting.

When the Business App is enough

Low volume handled by a person is what the app is for, and it is free.

A single location, a few conversations a day, no integration with other systems.

Quick replies and labels cover a surprising amount of small-business need.

It does not automate, and attempting to automate it is the unofficial route by another name.

Migrating later is possible and involves moving the number, which is easier before customers have years of history on it.

Start here if you are small, since the platform's overhead is not worth it below a certain volume.

Migrating a number that is already in use

The common situation is not a clean start. It is a business with a number customers already message, running on the consumer app or the Business App, wanting to automate.

A number can move from the Business App to the platform, and the process deletes the app's local chat history — which is frequently the thing nobody expected.

Export what you need first, since the history is not carried across and is not recoverable afterwards.

Two-step verification on the old registration must be cleared before the number can be registered elsewhere, and this catches people mid-migration.

Plan for a gap. The number is unavailable during the move, so a quiet period is better than a busy one.

Tell customers nothing changes, because from their side it should not — same number, same thread.

Do not migrate during a promotion, which is when both the volume and the cost of a problem are highest.

Making it survive

Do not build on an unofficial library and plan to migrate, since the migration is the hard part and the ban may arrive first.

Keep opt-in records, because you will be asked to demonstrate them.

Monitor the quality rating rather than discovering a problem through a restriction.

Have a second channel for anything critical, since a messaging channel you do not own is a dependency.

Report the outcome: messages sent by template, delivery, and quality rating changes.

Limits worth knowing about

Pricing and policy change, repeatedly, and have done so several times in recent years.

Template rejection reasons can be opaque, and resubmission is the usual route.

Number portability between providers is possible and is not instant.

Meta's rules apply regardless of your provider, and a provider cannot grant you an exemption.

No integration removes the policy constraints, which are the channel rather than the tooling.

What to do first

Work out what a ban would cost you specifically — the number on your signage, in your customers' phones, on your invoices — and compare that against the monthly platform cost. For most businesses with customers who have saved the number, that comparison ends the discussion, and it is worth doing explicitly rather than assuming either answer.

Two habits make the difference. Register a number that has never been a consumer WhatsApp account, since converting one is a common source of avoidable difficulty. And record opt-in at the point you obtain it, with the wording and the date, because reconstructing consent later is not possible and it is the thing you will be asked for.

Frequently asked questions

Are unofficial WhatsApp APIs against the rules?

Yes. Automating the consumer client and using modified or unofficial clients violate WhatsApp's Terms of Service, which name them directly. Detection is active and bans are frequently permanent.

What does a ban actually cost?

The number, which is usually the asset — customers have it saved, it is on your signage and your invoices — plus the conversation history and the accumulated quality position. The replacement starts cold.

What does the official platform require?

A Meta Business Portfolio with business verification, a phone number not registered to a consumer WhatsApp account, an approved display name, approved templates for messages outside the service window, and recorded opt-in.

How is the platform priced?

Per message for template messages since July 2025, replacing the previous conversation-based model, with rates varying by template category and country. Further changes take effect in October 2026, so check Meta's current documentation rather than any article's figures.

What is the customer service window?

A 24-hour period after a customer messages you, during which you can send free-form replies. Outside it, you need an approved template.

Can I message WhatsApp groups through the platform?

No. The Business Platform does not support sending to groups, which surprises people planning community or broadcast-to-group features.

Why are the rules so restrictive?

Largely because of what unautomated and unofficial bulk messaging did to the channel. The constraints are the channel rather than the tooling, and no provider can exempt you from them.

Is the free WhatsApp Business app enough?

For low volume handled by a person, frequently yes — quick replies and labels cover a lot of small-business need. It does not automate, and automating it is the unofficial route under another name.

Can I move my existing WhatsApp number to the platform?

Yes, and the move deletes the Business App's local chat history, which is not recoverable afterwards. Export anything you need first, clear two-step verification on the old registration, and plan the move for a quiet period since the number is unavailable during it.

Will customers notice the migration?

They should not — same number, same thread. What changes is on your side. Avoid migrating during a promotion, when both volume and the cost of a problem are at their highest.

Related reading

• WhatsApp messaging limits and how tiers work
• Why WhatsApp bots get banned
• WhatsApp webhooks explained