There Is No Unofficial WhatsApp Business API: Free Tiers, Personal Numbers, and What Actually Works

Is There a Free Unofficial WhatsApp Business API?

No. There is no unofficial tier of the WhatsApp Business API. Meta operates one Business API, reached through a WhatsApp Business Account. What people call the unofficial route is self-hosted software that automates an ordinary WhatsApp account over the linked-device protocol, the same mechanism the WhatsApp Web client uses. The phrase hides three questions, each with its own answer.

1. Is there an unofficial WhatsApp Business API? No. Nothing sits beside Meta's API as an approval-free edition of it. “Unofficial” names unrelated software that pairs with a normal WhatsApp account the way WhatsApp Web does.
2. What is actually free? Different things in each path. Meta's Cloud API is free to host and bills you once you send; Meta publishes the current allowances and per-country rates and revises them, so read those figures on Meta's own pricing page. Open-source libraries are free to download and cost you a server plus engineering time. SocialMate's Free tier is $0 forever: 200 messages a day on one account, no card.
3. Can I automate the number in my pocket? Not through Meta's API — a Cloud API number is registered to a WhatsApp Business Account, not to the consumer app. Through self-hosted software, yes, with real terms-of-service exposure and real ban risk.

Where the free-tier confusion starts. Free to host is not free to use. Meta publishes free allowances alongside the rates it charges for outbound sends. Both change. Confirm them on Meta's own page before you build a budget on them.

One boundary this guide does not blur: SocialMate is independent software, not affiliated with, endorsed by, or partnered with WhatsApp or Meta. Read the licence and disclaimers of any project you consider, including SocialMate's.

What Does “Unofficial WhatsApp API” Actually Mean?

It means software that automates a normal WhatsApp account over the multi-device protocol — the mechanism behind WhatsApp Web — rather than calling Meta's API. It is a paired device, not a privileged integration. There is no back door, no hidden endpoint, and no approval-free edition of Meta's own API.

The named projects are Baileys (WhiskeySockets), WAHA, Evolution API and open-wa. Baileys is a library that speaks the WhatsApp Web protocol directly. WAHA wraps a Baileys-style engine in a Docker-first HTTP API. Evolution API ships a wider feature set on the same foundation. open-wa is a Node toolkit in the same family. Each carries its own licence and disclaimers, so read them before you commit code to one.

Why the category keeps growing. WhatsApp is where the customers already are. Where they are, a route to a number they already own keeps attracting founders, marketers and agencies.

The risk profile is why the distinction matters. These tools touch a consumer account, and WhatsApp can act on a consumer account. Treat the mechanism as a real integration with real exposure, not a clever workaround.

For the build-effort comparison, see Baileys vs WAHA. For the whole category on one page, see the self-hosted comparison.

What Does the Official Cloud API's Free Tier Actually Cover?

The Cloud API is free to host. It is not free to send. Meta publishes the free allowances it grants and the per-country rates it charges for outbound sends, and it revises both, so treat any figure you read second-hand as stale until you have seen it on Meta's own pricing page.

What is free. A defined set of inbound conversation types, plus a development test number.

Where the meter starts. Outbound sends. Marketing, utility and authentication template categories are billed per message at per-country rates Meta publishes.

What else costs you. The gating. A Cloud API test number is deliberately limited in who it can message, so it proves your plumbing rather than your business — see Meta's Cloud API documentation for the current restrictions. Scaling past the sandbox requires a WhatsApp Business Account, business verification and display-name review, per Meta's own documentation.

Volume is tiered before it is billed. Meta documents sending limits that scale with an account's standing rather than arriving all at once. Read the current tables before planning a rollout; the figures change.

The honest summary, and the point most vendor blogs skip: free hosting, a narrow band of free inbound traffic, and a meter that starts the moment you send.

Full side-by-side: SocialMate vs the Cloud API.

Can You Automate Your Personal WhatsApp Number?

Not through the official Cloud API. Meta's phone-number documentation requires the number to be registered to a WhatsApp Business Account before it can send, after which it behaves as a business number rather than the consumer account your contacts already message. Self-hosted software can automate the personal number on your phone by pairing as a linked device, with real terms exposure and genuine ban risk.

Official Cloud API: no. You can migrate a number across, but you cannot keep it active in both places at once. Once registered, the account your contacts already know stops working the way they expect.

Self-hosted: yes, with a cost. Baileys, WAHA, Evolution API and SocialMate all pair with an ordinary WhatsApp account over the linked-device protocol. No WhatsApp Business Account, no business verification, no display-name review, and you keep the consumer app on your phone. This is a structural difference in where the software runs and which account it drives, not a way around any Meta rule or limit.

Now the part sales pages omit. Automation can violate WhatsApp's terms, and Meta has tightened terms language repeatedly — a change dated 18 October 2025 was reported by WABetaInfo and is not confirmed until it appears in Meta's own published terms. Unsolicited bulk messaging is the fastest route to a ban, and a number carrying live customer relationships is a bad thing to lose. SocialMate's own terms are explicit that it is “not a bulk-messaging, broadcast, or spam platform” — a constraint we treat as product design, not marketing copy.

What consent looks like in practice. Message the people who ordered, booked, or asked you something. One batch means many individual, personalised messages, each paced by the anti-ban pipeline. Identical text sent to many contacts is blocked by the duplicate-content guard, by design.

The policy side deserves its own read: WhatsApp Automation Compliance Rules 2026 and the knowledge base answer to will I get banned?.

How Much Does Each WhatsApp Automation Route Actually Cost?

Each route costs something different, and only one is free in the sense a buyer means. The Cloud API is free to host and billed per outbound send. BSP resellers add a subscription on top of that same meter. Open-source self-hosting is free software plus a VPS and your own engineering. SocialMate is a flat licence with a real $0 tier: 200 messages a day on one account, no card.

The table below prices every route on the same axes, including the two columns most roundups omit — pricing model and ban risk — plus the question buyers decide on first: who each path is actually for. Bans are possible in every path, and the table says so rather than implying otherwise.

Three things the table makes visible.

• Cloud API and BSP resellers share one meter. Twilio, 360dialog, WATI, AiSensy and Interakt sit on the same per-message billing underneath, then add a vendor subscription and hold conversations in their own cloud.
• Open-source self-hosting is free software with a bill attached. Docker is an obligation rather than an option, and the anti-ban layer, GUI, risk scoring and message storage are yours to build and maintain.
• Flat licensing removes the meter entirely. SocialMate charges per device, not per message, because sending runs on your own machine. One licence includes one device; extra seats are $4 per month each, about $40 per year each on Annual, added from the account portal rather than sold separately.

Deeper breakdowns live on the Cloud API comparison and the pricing page.

How Many Messages Per Day Can a New Number Send Safely?

There is no universal safe daily number, and any figure presented as guaranteed is misleading. A gradual ramp is the safe default, and both architectures agree on the shape of the curve. In SocialMate, Free carries up to 200 messages a day on one account, Pro starts at a deliberately conservative 500 a day per account, and only after a 72-hour warming protocol does High-Volume Mode unlock scaling toward 5,000 a day per account.

Warming exists because a number with no history that suddenly sends hundreds of messages looks nothing like a person. Meta applies the same logic on the official side, documenting sending limits that scale with an account's standing rather than arriving all at once. Different mechanisms, same conclusion: capacity is earned, not provisioned.

The mechanics behind the number matter as much as the number.

• Pacing profiles. Safe, Balanced and Fast set the rhythm rather than a fixed interval.
• Per-account rate limits. A ceiling stops one busy queue draining in a single burst.
• Burst caps. 3 messages per 10-second window on Free, 5 on Pro.
• Read, then type, then send. SocialMate marks the chat read and shows a real typing indicator scaled to message length before a reply leaves.

The uncomfortable sentence, said once: none of this makes a number safe. Monitoring plus a gradual ramp is the safe default, not a guarantee, and bans remain possible at any volume. For the volume-versus-safety trade at scale, see High-Volume WhatsApp Messaging at Flat Rate, and for where to run it, Desktop vs VPS: which is safer for your number?.

If You Automate Your Own Number, What Actually Reduces Risk?

Risk reduction is a stack of small mechanics, not one setting. Each item below exists because a specific pattern looks automated, and together they make ordinary traffic look ordinary. None of them makes a number safe, and no tool can promise that — bans are always possible on any WhatsApp account, official or self-hosted.

• Randomised delays and jitter. Uniform timing is a fingerprint. Variation is not.
• Per-account rate limits. A ceiling per number stops one busy queue draining in a single burst.
• Session warming for new numbers. New accounts start quiet and build history across their first 72 hours.
• Read before reply, then a real typing indicator. The chat is marked read and typing shows before the message leaves, scaled to message length, the way a person composes.
• Adaptive throttle. Sending slows as the risk score climbs, instead of continuing at full speed.
• Duplicate-content guard. Identical text or images sent to many contacts are blocked. Personalised batches are the supported shape.
• Live 8-factor risk scoring with cold-outreach detection. A running score that surfaces cold-outreach patterns and slows sending in response. It reports how your traffic looks; it does not predict what WhatsApp will do.
• Risk-based auto-resume. Accounts that cooled come back under a controlled ramp rather than all at once.

Network matters as much as pacing. The desktop app connects from your own residential IP, ideally the same home network as the phone that owns the account, which removes a risk factor rather than eliminating risk. A VPS runs from a datacenter IP, which carries lower network reputation. Pro's per-account proxy routing lets a server egress through your own residential or mobile SOCKS5 or HTTP proxy to reclaim a residential path, and it changes only the network path — never the rate limits or the warming schedule.

Baileys Anti Ban goes deeper on the mechanics, the WAHA comparison shows what you would otherwise build yourself, and the Evolution API comparison covers the other major contender.

Are Read Receipts, Typing Indicators and Reactions Free?

Yes. Mark-as-read, the typing indicator and emoji reactions are free on every SocialMate tier, including Free. They produce no chat bubble, so they consume no message send budget and do not raise the anti-ban risk score. They can only target a chat you are already in, and they run on a separate signal rate limit: 20 per minute on Free, 60 per minute on Pro.

That separation is the whole point. Quoted replies, reactions, mark-as-read and the typing indicator sit outside the message pipeline on every tier, which is why an automated account can read as a person answering rather than a machine firing. A reply that appears after a typing indicator, inside a thread that already shows as read, is the ordinary shape of a human conversation — the same cadence the AI-agent system prompt teaches.

Where free stops. Polls, location pins, contact cards and media sending are Pro. Interactive buttons and list menus are deliberately not shipped, because they are deprecated on the WhatsApp Web protocol; polls are the supported alternative.

One caveat worth stating plainly: polls, locations and contact cards are not auto-queued when the anti-ban engine blocks them, so those sends return a 429 with queueable:false on every tier. Text and link media still auto-queue on Pro.

What Can Developers Build With the Local API?

Developers get a real local HTTP API, and it starts on the Free tier. The local HTTP API runs on Free with read endpoints and plain text send, plus 9 of the 35 webhook events. Pro adds media send, groups, polls, scheduled messages, the smart queue and the full message history surface behind localMessageCache. The API itself is never Pro-only.

Runs on Free: the local HTTP API with read endpoints and plain text send, 9 of 35 webhook events, plus quoted replies (replyTo), emoji reactions, mark-as-read and the typing indicator — none of which consume message budget.

Adds on Pro: media send, group operations, polls, location and contact cards, the smart queue with priority retries, scheduled messages and batches, a stable named tunnel, unlimited webhooks (all 35 events), message history with unlimited full-text search, per-account proxy routing, Agent Memory, and the AI conversation-context export — a role-mapped, token-windowed transcript your own model reads.

Native integrations, named precisely. The n8n community node n8n-nodes-socialmate is first-class: MIT licensed, version 2.7.0, with a scope-aware credential, an action node and a trigger node, and every operation exposed to n8n's AI Agent as a callable tool. Its standout operation is Get AI Context, which returns a whole conversation in one call, replacing the fragile n8n memory node. The MCP server socialmate-mcp exposes 44 WhatsApp tools to Claude Desktop, Claude Code, Cursor, Cline and any MCP client. MCP is an open protocol surface, like the REST API and webhooks, not a per-service connector. Make, Zapier, Shopify, WooCommerce and the rest connect through the HTTP API plus outbound webhooks — there is no native connector for them, so do not expect one.

The setup detail that costs people an afternoon. The local API server is off by default. Switch it on in the app under API & Integrations, then create an API key (a real key looks like sm_<random> and is shown once). It is the number-one reason MCP tools do not appear: the server starts fine, has nothing to talk to, and every call fails with a connection error. Nothing installs globally — npx -y socialmate-mcp fetches the package on first run, and the -y matters because an MCP client has no terminal to answer an install prompt. Keep Node.js 18.17 or newer.

Two honest notes. MCP is request and response with no inbound push, so an agent that reacts to incoming messages needs polling or the n8n trigger as its event source — the trigger is the event source, MCP is the acting surface. And AI replies, summaries and triage are coming soon, not shipped. Agent Memory stores what your own model produced; SocialMate runs no model. SocialMate is the hands and the memory; your model is the brain.

Start with the API and webhook docs, the n8n hub, the MCP server guide, and the AI agent system prompt.

Path	What is free	Pricing model	Ban / account risk	Best for	Where your data lives
Meta Cloud API (official)	Free hosting; Meta publishes free allowances for some inbound conversation types and a limited development test number	Metered per outbound template message at per-country rates Meta publishes; WhatsApp Business Account and verification required to scale	Business accounts face Meta policy enforcement and can be restricted or suspended. Bans are possible	Brands that need official status and template compliance	Meta's cloud
BSP resellers: Twilio, 360dialog, WATI, AiSensy, Interakt	Vendor trials and sandboxes vary by vendor	The official per-message meter underneath, plus a vendor subscription	The same official enforcement, plus possible vendor-level account suspension. Bans are possible	Teams that want the official API without building against Meta directly	Vendor cloud
Self-hosted OSS: Baileys, WAHA, Evolution API, open-wa	The software itself	Free licence; you pay for a VPS, treat Docker as an obligation, and build your own safety layer	Real ban risk. No vendor safety layer: pacing, warming, duplicate guards and monitoring are yours to build	Developers who want full control and will own the maintenance	Your server, if you build storage
SocialMate Free	$0 forever, no card: up to 200 messages/day on one account, 9 of 35 webhook events, read endpoints and plain text send via the local API, and free reactions, typing and read receipts	Flat licence, no per-message fee	Bans are always possible. The anti-ban engine reduces risk; it cannot remove it	Operators testing their own number on a real daily allowance	Local storage on your own machine
SocialMate Pro	7-day opt-in trial, started in-app with an email, no card	$10/month or $99/year flat; no per-message fee. One licence includes one device; extra seats $4/month or about $40/year each. Unlimited WhatsApp accounts	Bans are always possible. Warming, pacing, the duplicate-content guard and optional residential proxy routing reduce risk	Always-on operators, developers and agencies sending personalised batches at volume	Local storage on your own machine, or your own VPS

Frequently asked questions

Is there a free unofficial WhatsApp Business API?

No. There is no unofficial tier of the WhatsApp Business API. The official Cloud API is free to host but bills outbound sends and requires a WhatsApp Business Account. What people call the unofficial route is self-hosted software such as Baileys, WAHA, Evolution API or SocialMate, which automates a normal WhatsApp account over the multi-device protocol instead of using Meta's API at all.

Does the WhatsApp Cloud API free tier cover template messages?

Meta grants free allowances for some inbound conversation types and a development test number, and charges for outbound template sends in the marketing, utility and authentication categories at per-country rates. The published figures change, so confirm current rates and allowances on Meta's own pricing page rather than on a vendor blog.

Can I use my personal WhatsApp number with the Business API?

Not as a normal personal number. Meta's phone-number documentation requires the number to be registered to a WhatsApp Business Account, after which it behaves as a business number rather than the consumer account your contacts already message. You can migrate a number across, but you cannot keep it active in both places at once.

Can I automate WhatsApp without business verification?

Not on the official path. Scaling past the Cloud API's sandbox needs a WhatsApp Business Account, business verification and display-name review, per Meta's Cloud API documentation. Self-hosted software pairs with an ordinary WhatsApp account over the linked-device protocol, so there is no verification step and no Meta approval — real terms-of-service exposure stands in its place.

Will WhatsApp ban me for automating my own number?

Possibly. Bans are always possible, and no tool can guarantee otherwise. Risk factors reported by operators include sudden volume on a new number, identical text sent to many contacts, cold outreach to people who never opted in, and datacenter IP addresses. SocialMate's warming, pacing, duplicate-content guard and residential-IP default reduce that risk; they do not remove it.

How many messages per day can a new number send safely?

There is no universal safe number, and any figure presented as guaranteed is misleading. A gradual ramp is the safe default. In SocialMate, Free sends up to 200 messages a day on one account; Pro starts at a conservative 500 a day per account and unlocks scaling toward 5,000 a day per account through High-Volume Mode only after a 72-hour warming protocol. Volume should rise with monitoring, never jump.

Do I need Docker to self-host WhatsApp automation?

With most open-source options, yes: Evolution API and WAHA are Docker-first, so a container runtime is a prerequisite before anything works. SocialMate runs as a desktop app on Windows, macOS or Linux with no DevOps, and also ships a headless server build via Docker image or systemd installer for VPS deployments, managed from the same GUI in your browser at /admin. Docker is an option there, not a prerequisite.

What is the difference between the Cloud API, Baileys, WAHA and Evolution API?

The Cloud API is Meta's official, metered, template-based product requiring a WhatsApp Business Account and verification. Baileys is a library that speaks the WhatsApp Web protocol; WAHA wraps a Baileys-style engine in a Docker-first HTTP API; Evolution API offers a broader feature set on the same foundation. All three ship the transport. Pacing, warming, duplicate guards, risk scoring, a GUI and message storage are left for you to build.

How much does flat-rate WhatsApp automation cost per month?

SocialMate Free is $0 forever with no card, covering up to 200 messages a day on one account. Pro is $10 per month or $99 per year, covering 500 messages a day per account rising toward 5,000 after warming, unlimited WhatsApp accounts, media, groups, polls, scheduled sends and the full local API surface. There is no per-message fee at any tier. One licence includes one device; extra seats cost $4 per month each, about $40 per year each on Annual.

Is the SocialMate local API free or Pro-only?

It runs on Free. The local HTTP API on Free includes read endpoints and plain text send, plus 9 of the 35 webhook events. Pro adds media send, group operations, polls, locations, contact cards, the smart queue, scheduled messages, unlimited webhooks, a stable named tunnel, message history with full-text search and Agent Memory. One setup step trips most people up: the local API server is off by default and must be switched on in the app under API & Integrations before any MCP or n8n tool can connect.

Is SocialMate affiliated with WhatsApp or Meta?

No. SocialMate is independent software and is not affiliated with, endorsed by, or partnered with WhatsApp or Meta. WhatsApp and Meta are trademarks referenced for identification only. SocialMate is not the official WhatsApp Business API, and automating a WhatsApp account can violate WhatsApp's terms of service.