WhatsApp Business API vs unofficial API: which should you use?

If you're building a WhatsApp bot, you'll hit this question early: use the official WhatsApp Business API, or connect your own personal number? The two approaches are fundamentally different — in how they work, what they let you do, and how much risk they carry.

This guide cuts through the confusion. Here's exactly what each option means, when to use which, and how CodeWords handles both.

TL;DR

• Official Business API: messages come from a dedicated business number, Meta-approved, with template requirements and daily send limits. Safest for customer-facing bots.
• Personal Device (unofficial): you connect your own WhatsApp number. More flexible, no templates, no send caps from the platform — but higher account risk if you send cold outreach.
• CodeWords supports both. Pick the right one for your use case; CodeWords handles the technical setup either way.

What is the WhatsApp Business API?

The WhatsApp Business API is Meta's official, approved channel for businesses to send and receive WhatsApp messages at scale. It's what large companies, BSPs (Business Solution Providers), and platforms like CodeWords use to power customer-facing bots.

When you use the Business API through CodeWords, messages are sent from CodeWords' official WhatsApp Business number. Your customers message that number, your bot replies — all fully Meta-compliant.

Key characteristics:

• Meta-approved templates required for the first outbound message to a new contact
• 24-hour service window: after a customer replies, you can send free-form messages for 24 hours. After that, only templates work until they reply again
• Daily send limits apply: 5 DMs per day on the CodeWords Free plan, up to 50/day on Max
• Low account ban risk — you're operating within Meta's official framework
• US marketing template restriction: since April 2025, marketing templates can't be sent to US phone numbers

Best for: Customer-facing support bots, lead qualification, appointment booking, order notifications — anything where customers initiate contact or you need to send compliant outbound messages.

What is the unofficial API (Personal Device)?

The "unofficial API" refers to connecting your own personal WhatsApp number to an automation tool. Rather than using Meta's official Business API, it works by linking your number as a connected device (the same way you'd link WhatsApp Web or a tablet).

In CodeWords, this is called Personal Device integration. You connect your own number via a pairing code: WhatsApp → Settings → Linked Devices → Link a Device. The bot then sends and receives messages as you, from your own number.

Key characteristics:

• No template requirements — send any message, in any format, at any time
• No 24-hour service window — reply freely regardless of when the customer last messaged
• No platform-level daily send caps — your own number can send as many messages as you want
• Access to your own contacts and groups
• Higher account ban risk if used for cold outreach or bulk messaging to strangers

Best for: Personal AI assistants, high-volume inbound bots where you want to respond from your own number, group automation, and situations where template restrictions would limit the use case.

The ban risk difference — and why it matters

This is the most important thing to understand about the unofficial/Personal Device approach.

The WhatsApp Business API has built-in guardrails. Because Meta controls the channel, they can enforce rate limits, require template approval, and monitor message quality. This makes it harder to abuse — and safer to operate within.

When you connect your own personal number, those guardrails don't exist at the platform level. The risk isn't in the connection method itself — it's in how you use it. Sending cold messages to people who haven't contacted you, blasting identical messages to hundreds of contacts, or messaging scraped lead lists will get your personal number flagged and banned.

The golden rule is the same either way: start inbound-first. If customers message you first, you're inside a reciprocal conversation and the ban risk is very low, regardless of which connection method you use. The ban risk spikes the moment you start sending to people who didn't reach out.

Feature comparison

Feature	Business API	Personal Device
Sender	CodeWords business number	Your own number
Templates required?	Yes, for first contact	No
24-hour service window?	Yes	No
Daily send limits	5–50/day (by plan)	No platform limit
Group messaging	No	Yes
Your own contacts	No	Yes
Ban risk (inbound-first)	Very low	Low
Ban risk (cold outreach)	Low–medium	High
Setup time	Automatic	~30 seconds (pairing code)

Which should you choose?

Choose Business API if:

• You're building a customer-facing bot (support, FAQ, lead qualification, booking)
• Customers will initiate contact from your website, social bio, or a CTA
• You want the lowest possible account risk
• You're fine with the 5–50 DM/day limit for the Business API number

Choose Personal Device if:

• You want a personal AI assistant on your own number
• You need to respond from your own number (clients know it, expect it)
• You need group chat automation
• Your inbound volume would exceed the Business API daily limits
• You want to send messages to your existing contacts without template approval

Both is fine too. Some CodeWords users run a Business API bot for inbound customer queries, and a Personal Device bot for their own productivity or team communications.

How CodeWords handles the setup

With Business API, CodeWords handles everything automatically. Tell Cody what you want to build, and it sets up the webhook, message routing, and template handling for you. No API keys, no Meta developer portal.

With Personal Device, the setup takes about 30 seconds. Cody generates a pairing code; you open WhatsApp → Settings → Linked Devices → Link a Device and enter it. That's it. Your number is connected and the bot is live.

Either way, you describe what you want the bot to do in plain English. Cody, the AI automation assistant, writes the workflow and deploys it. The connection method is a setup choice, not a technical hurdle.

Get started with CodeWords and have your first WhatsApp bot live today.

Related reading: How to build a WhatsApp AI agent, WhatsApp anti-ban playbook, WhatsApp message limits explained, WhatsApp agents by industry.