Most articles on this question answer it backwards. They treat Meta verification as a gate you either clear or sneak around, and they sell you the sneaking. The document trail says something duller and more useful: Meta's own API runs unverified, at published ceilings, and the real question is whether those ceilings fit you.
Yes. Meta's own Cloud API runs without business verification, capped at 250 unique customers per 24 hours, 250 templates and 2 phone numbers. Verification lifts those ceilings. It does not grant access.
- Cloud API, unverified - Meta's official API at starting ceilings.
- Cloud API through a BSP, verified - full scale, template broadcast, badge eligibility.
- Own-number API over WhatsApp Web - the number you already use, no Meta onboarding.
Can you use the WhatsApp API without Meta Business verification?
Yes, on Meta's own platform. Meta's messaging limits documentation states that "newly created business portfolios have a messaging limit of 250." That is an allowance, not a block. A brand-new portfolio, verified by nobody, can deliver business-initiated messages to 250 unique WhatsApp numbers in a rolling 24-hour window on day one.
The word "limit" is doing precise work there, and Meta's own definition is worth reading rather than the paraphrase:
"Messaging limits are the maximum number of unique WhatsApp user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period."
Three things follow. It counts unique recipients, not messages. It counts only business-initiated sends outside an open service window, so replies to people who messaged you first do not count against it. And it is a ceiling on reach, not a switch on capability.
That leaves three real routes, and only the third avoids Meta entirely. The next section saves the most time, because for a meaningful share of readers the answer is to close this page.
Who should stop reading here and get verified anyway?
Five situations make Meta verification and a Business Solution Provider the correct answer, not the expensive one. If any of these describes you, the rest of this article is a distraction: the blue checkmark, template broadcast at Meta scale, official Business Platform support, a regulated-sector paper trail, or three or more agents working one shared queue.
You need the blue checkmark. Official Business Account status is granted by Meta and there is no route to it outside the WhatsApp Business Platform. Per Meta's Official Business Accounts documentation, the badge requires five things together: policy compliance, 30 days registered on the platform, a business portfolio "verified through Business Verification," two-step verification enabled on the number, and an approved display name. Own-number tools cannot supply any of them.
You broadcast templated messages at scale. Above a couple of thousand unique recipients a day, you belong on the ladder Meta built for it, with the throughput commitments that come with the platform.
You need someone to escalate to when a number or a template is rejected. That escalation path is a property of the BSP relationship. Nobody outside the platform has it.
You are in finance, healthcare, insurance or anything with an audit trail. Use the sanctioned channel. A regulator asking which approved system you messaged a customer on is not a conversation to have about a paired browser session.
Three or more people work the same WhatsApp queue. Assignment, handoff, roles. Blueticks does not have a multi-agent shared inbox, and saying otherwise would be a lie you would discover in week one.
If two or more of those fit, the tools worth pricing are Wati, Interakt, TimelinesAI and Periskope, or a BSP bought directly through Meta's partner flow. Our WhatsApp Business API alternatives comparison prices thirteen of them from each vendor's own page and points three of its seven recommendation rows straight back at the official API. That is the honest shape of this market, and this page is not going to pretend otherwise.
What does Meta Business Verification actually unlock?
Business verification is an identity check on your company, not a licence to send. Meta describes it as a process for confirming your company's identity. Clearing it raises four published ceilings and makes you eligible for a fifth thing. It changes no message type, no API endpoint and no feature.
| What changes | Unverified | After verification | Meta's own source |
|---|---|---|---|
| Unique customers messaged outside a service window, per rolling 24h | 250 | 2,000, then automatic scaling to 10,000, 100,000 and unlimited | Messaging limits |
| Message templates per WhatsApp Business Account | 250 | Up to 6,000, if a number also has an approved display name | Template fundamentals |
| Registered business phone numbers | 2 | 20 | Business phone numbers |
| Official Business Account eligibility | Not eligible | One of five requirements satisfied | Official Business Accounts |
Two details in that table are routinely reported wrong, including in places you would expect better. Verification is not the only path to either raised ceiling. Meta's messaging limits page lists three routes to 2,000: verify your business, have your onboarding partner verify it, or deliver 2,000 template messages to unique numbers over a 30-day moving period at a high quality rating. And the phone number cap moves to 20 "if your business becomes verified, or if you have reached a messaging limit of 2,000," so volume alone gets you there.
While we are correcting things, three separate concepts get flattened into the phrase "green tick," and they are not interchangeable:
- Business Verification - free document review of your company, lifts the ceilings above.
- Official Business Account - the badge, blue, five requirements, verification is one.
- Meta Verified - a paid monthly subscription, sold separately by Meta from $14.99 per month.
Whether you belong on the platform at all is a prior question, answered in our readiness test for the WhatsApp Business API.
Does the Cloud API really work unverified, and what is the catch?
It really works. There are three catches, and none of them is verification. Templates are still mandatory outside the 24-hour window, you still need a phone number that is not already on WhatsApp, and registering the number you already use has consequences that are easy to trigger and hard to reverse.
Templates apply at every tier. Meta's template fundamentals page is unambiguous: "Template messages are the only type of message that can be sent to WhatsApp users outside of a customer service window." That window opens for 24 hours when a user messages you, per Meta's service messages documentation. Unverified does not mean unstructured. You will write templates and wait for approval on day one.
The number is the real friction. Meta's business phone numbers documentation states plainly that "numbers already in use with WhatsApp cannot be registered unless they are deleted first." The number your customers have saved is not automatically available to you.
Migrating your existing number is conditional, not free. This is where the popular advice goes wrong. If you delete your WhatsApp Business app account and register that number to the Cloud API directly, Meta's migration documentation says "your existing messaging history will be lost, and you will be unable to use that number with the WhatsApp Business app again." Reversing it means deleting the number from the platform first. The important nuance most summaries drop: onboarding through a partner that supports business-app numbers preserves your history and lets you keep using both. So the loss is a consequence of the direct path, not of the platform.
Be fair to this route. If you are building something new, can dedicate a number, and 250 unique recipients a day is more than you need, the Cloud API unverified is the right answer and it costs nothing to verify later. Skip the rest of this page.
What do you keep by running on your own number instead?
You keep the number itself, with its history and its saved-contact status, and you skip the template approval queue and the per-message meter. What you take on is a connection problem: the Cloud API is hosted by Meta, and an own-number API is not, so something has to keep a WhatsApp session alive.
An own-number API pairs with the WhatsApp account you already have, the way WhatsApp Web does, and sends through that session. No Meta portfolio, no display name review, no dedicated number, no per-message charge, because Meta is not in the path. The tradeoff is that a paired session has to be running somewhere.
Two answers exist to that. Either your machine stays on with WhatsApp Web open, or something runs the session server-side for you. In Blueticks that second option is a hosted gateway: each connected account gets its own Kubernetes workload, in one of two engine flavours, so sends continue with your laptop shut. It is not free capability. Verified in the product's own code today, creating a hosted engine on the Chrome/wa-js gateway flavour requires an active subscription carrying the offline-socket entitlement, and that entitlement allows one such engine. Without it the sends still work, but only while a browser session is open.
If your reason for looking is that the WhatsApp Business app ran out of room rather than that Meta did, those ceilings are catalogued in WhatsApp Business app limitations.
Skip the Meta onboarding queue entirely and send from the number your customers already have. Start free with Blueticks: no business verification, no template approval, no per-message fee, first scheduled message in about five minutes.
What can an own-number WhatsApp API never do?
Four hard limits, and three of them are WhatsApp's rather than any vendor's. No badge, ever. No button, list or template sends. Personal-account scale, not platform throughput. And no guarantee about your account's standing, from us or from anyone selling this mechanism.
No badge. Official Business Account status flows from Meta's five criteria above, all of which live inside the WhatsApp Business Platform. There is no unofficial route, and any vendor implying otherwise is selling something they cannot deliver. WhatsApp documents what the consumer-facing badge means in its help centre article on verified business accounts.
No interactive or template message types. This one is checkable in our code rather than our marketing. Blueticks's Baileys engine explicitly refuses sendButtonsMessage, sendListMessage and sendTemplateMessage, returning a feature_not_supported_on_baileys error before any handler runs. The engineering note in that file explains why: WhatsApp's servers deprecated those sends for standard, non-Cloud-API senders, so the engine can encode the message but WhatsApp either rejects it or the recipient's client renders nothing.
Personal-account scale. A paired session sends at the pace a person sends. There is no published throughput figure because there is no throughput commitment. If your plan depends on sustained machine-speed throughput, you need the platform.
No no-ban promise. State it plainly rather than in a footnote. The WhatsApp Business Terms of Service prohibit developing or using "any applications that interact with our Business Services without our prior written consent," and the WhatsApp Business Messaging Policy reserves Meta's right to "limit or remove your access" from anyone "messaging people at scale in an unauthorized manner." Sending through a paired session sits outside the WhatsApp Business Platform, so none of Meta's platform commitments on delivery, throughput or account standing apply. That is a statement about the mechanism, and it applies to Blueticks exactly as it applies to every other tool using it.
Consent is yours either way, and this is not an own-number caveat. The same Messaging Policy governs the WhatsApp Business app too, and requires that people "have given you their mobile phone number" and that "you have received opt-in permission from the recipient." No tool on any route collects that for you.
How do you choose? Three questions that settle it
Three questions resolve almost every version of this decision, and each one routes to exactly one of the three options. Answer them in order and stop at the first that gives you a hard yes.
1. Do you need to reach people who have not messaged you, at more than a couple of thousand a day? If yes, you need Meta's ladder and templates, which means the Cloud API and eventually verification. Nothing outside the platform scales into that. If no, keep going.
2. Do you need the blue checkmark, official support, or a regulated-sector audit trail? If yes, you need verification and a BSP, and you needed it before you started reading. If no, keep going.
3. Is the number you want to send from already saved in your customers' phones? If yes, the own-number route is the only one that keeps it, because registering that number to the Cloud API directly costs you its history and its Business app. If no, and you can dedicate a fresh number, the unverified Cloud API is a perfectly good place to start.
The comparison at the level of app versus platform, rather than tool versus tool, is laid out in WhatsApp Business app vs API.
How do you ship an own-number WhatsApp API today?
Connect the WhatsApp account you already have, then send with one HTTP call per message. The recipient is the path parameter, the body carries the message, and an optional timestamp turns the same call into a scheduled send.
POST /v1/scheduled-messages/{chatId}
{ "type": "text", "text": "Your order shipped.", "sendAt": "2026-08-20T09:00:00+03:00" }
That is the whole shape. type is one of text, media or poll. Omit sendAt and it sends now; include it and the message is queued, validated to land at least 10 seconds ahead and no more than 365 days out. From there a message moves through pending, confirmed, received, read and played, or failed.
This page is the decision, not the build. The full walkthrough, with working code, delivery status, campaigns and the pacing discipline that goes with sending on your own number, lives in the WhatsApp REST API on your own number guide. Start there once you have decided this is your route.
Frequently asked questions
Can you use the WhatsApp Business API without verification?
Yes. Meta's messaging limits documentation states that newly created business portfolios have a messaging limit of 250, meaning you can deliver business-initiated messages to 250 unique WhatsApp numbers in a rolling 24-hour window before verifying anything. Verification is one of three routes to raise that to 2,000. It gates scale, not access.
Does Meta business verification give me the green tick?
No, and three different things get called that. Business Verification is a free document review that lifts your ceilings. Official Business Account status is the badge, now blue, and Meta's documentation lists verification as one of five requirements alongside 30 days on the platform, two-step verification and an approved display name. Meta Verified is a separate paid subscription starting at $14.99 per month.
What are the limits if I skip verification on the Cloud API?
Four published ones. 250 unique customers messaged outside a service window per rolling 24 hours, 250 message templates per WhatsApp Business Account, 2 registered business phone numbers, and no eligibility for Official Business Account status. Templates and the 24-hour window apply identically whether you are verified or not.
Can I use my existing WhatsApp number with the Cloud API?
Not without cost. Meta's documentation states that numbers already in use with WhatsApp cannot be registered unless deleted first, and that deleting your WhatsApp Business app account to register directly loses your messaging history and locks you out of the app for that number. Onboarding through a partner that supports business-app numbers is the exception that preserves both. Own-number tools avoid the question by pairing with the account as it is.
Is an unofficial WhatsApp API safe to use?
"Unofficial" describes a mechanism, not a verdict, and the checkable consequence is this: a paired session runs outside the WhatsApp Business Platform, so Meta's commitments on delivery, throughput and account standing do not apply, and the WhatsApp Business Terms prohibit applications that interact with the Business Services without prior written consent. Nobody can promise you an outcome there. Recipient opt-in is required on every route and is yours to obtain.
Notes: every Meta and WhatsApp figure above was read from the linked primary source on 2026-08-16 and re-verified on 2026-08-18, and platform limits change without notice. Product behaviour described here was verified against the Blueticks production branch on 2026-08-18. Prices and ceilings quoted from Meta are Meta's, not ours.
