Official API
Run by Meta. Stable and supported, with per-message fees and rules on what you can send.
Official WhatsApp API or Linked Devices: which should you use?
A plain comparison of Meta's official WhatsApp API and the linked-device route: cost, message rules, groups, setup and risk, with sources.
Written by a company that sells one of the two. We say where the other one is the better choice.Linked Devices
Your normal WhatsApp number, paired like WhatsApp Web. Flat price and few rules, but unofficial.
The short answer
Need guarantees or work in a regulated field: go official. Need your existing number, groups or low-cost alerts: linked devices can fit.
The two routes
There are two ways to send WhatsApp messages from code. The official route is Meta's WhatsApp Business Platform. The other pairs a normal WhatsApp account as a linked device, the same way WhatsApp Web does, and sends through that session. ChatRail uses the second route. Both work, and they suit different jobs.
Side by side
| Official API | Linked Devices | |
|---|---|---|
| Who runs it | Meta, through the WhatsApp Business Platform. | A linked-device session on a normal WhatsApp account. It is not an official Meta integration. |
| Your number | A business number registered on the platform. | Your existing number. It keeps working on the phone. |
| Setup | Meta's business onboarding applies. | Scan a QR code or type a pairing code. |
| Starting a conversation | Template messages only, in three categories: marketing, utility and authentication (Meta pricing docs). | Any message. No templates. |
| Replying | Free-form replies only inside a 24-hour window that resets with each customer message (Meta pricing docs). | Free-form at any time. |
| Groups | The Groups API is for Official Business Accounts. Groups are invite-only, with at most 8 participants (Meta Groups docs). | Send to the groups the number is already in, and create and manage groups. |
| Cost | Per delivered message, priced by country and category. The first 1,000 service messages a month per number are free (Meta pricing docs). | A flat price per number with no per-message fee. ChatRail starts at $15 a month. |
| Keeping it connected | Managed by Meta. | Sessions can drop. WhatsApp unlinks a device after 30 days without activity, or 14 days without the primary phone (WhatsApp help). |
| Enforcement risk | You operate inside Meta's published rules. | WhatsApp says unofficial apps can get an account banned (WhatsApp help). |
Checked against Meta's and WhatsApp's own pages on 10 October 2026. These rules change, so read the linked source before you decide.
What it costs in practice
The official API charges for each delivered message, so the bill depends on where your customers are. At Meta's list rates from 1 October 2026, 10,000 order updates a month cost about $150 in Pakistan, $67 in Nigeria and $14 in India. A flat-fee linked-device plan costs the same in every country.
So the cheaper route depends on the market. In India the official API can cost less at that volume. In Pakistan a flat fee wins above roughly 1,000 messages a month. The pricing breakdown has the full rate tables.
Choose the official API when
- You need formal Meta support or have to pass a compliance or procurement review.
- You send one-time passcodes or marketing at high volume.
- Losing a number for a day would stop your business.
- You work in a regulated field such as banking or healthcare.
Choose Linked Devices when
- You must keep your existing number, and keep using it on the phone.
- You send alerts and updates to people who expect them.
- You need to send into groups you are already in, or groups larger than 8.
- You want a fixed monthly cost that does not grow with every message.
- You can handle a session dropping and being re-paired.
The risks of Linked Devices, plainly
A linked-device session is not an official integration, and WhatsApp can restrict a number that looks abusive. Two different things can go wrong, and they need different fixes:
- The session expires. Re-pairing fixes it. See how to reconnect a dropped session.
- The number is restricted. Re-pairing does not fix it. See how to tell a ban from an expired session.
To lower the risk, message only people who expect to hear from you, send at a steady pace, and watch the connection.requires_repair event. ChatRail also refuses more than 10 messages to one person in 5 minutes and keeps an opt-out list.
Using both
You can run both. A common split is the official API for passcodes and marketing, and a linked device for group messages and operational alerts on a number your team already uses. ChatRail only provides the linked-device route, so the official side would come from Meta or one of its partners.
Frequently asked questions
Is a linked-device API allowed by WhatsApp?
It is not an official integration. WhatsApp's help pages say unofficial apps can get an account banned, so treat that as a real risk.
Will my number get banned?
Numbers are restricted for behaviour, such as unwanted bulk messages and people reporting you. Messaging people who expect to hear from you lowers the risk, but nothing removes it.
Does ChatRail offer the official API?
No. ChatRail only uses WhatsApp Linked Devices.
Can I switch routes later?
Yes. Keep your own records of recipients, consent and message history so a move does not depend on either provider.
Which is cheaper?
It depends on the country and volume. Per-message fees are low in some markets and high in others, while a flat fee stays the same.
BUILD A CONTROLLED TEST
Start with one number and one real workflow.
Validate the connection, delivery state and reply path before increasing traffic.
Start free