WhatsApp API without your own number or business verification

Everything below is the official WhatsApp Cloud API. What you do not need is a number, a business portfolio, a verification or a template of your own — because they are ours. What that cannot do is message your customers, and this page says so before it says anything else.

The short answer

You can send WhatsApp messages to your own people — alerts, approvals, check-ins — through a provider whose number and message templates Meta has already approved. No number of yours, no legal entity, no verification, no template review. You cannot message your customers that way: reaching them means a number registered to your business, and Meta's verification with it.

What Meta actually requires, stated fairly

Three things, and it is worth being exact about them because most pages on this question are not:

A registered legal entity. A WhatsApp Business Account belongs to a business, not a person. This is the wall a side project hits first, and no amount of patience gets round it.
A dedicated phone number that is not already on WhatsApp — not on the normal app and not on WhatsApp Business. Once it is on the API it stops being a phone you can text from.
Message templates, reviewed by Meta, for anything sent outside a 24-hour window that a person opened by writing to you first.

One correction, because it is the thing most of these pages get wrong in the other direction: Meta does let you start sending while verification is still pending, under hard limits on how many people you can reach and how many templates you can hold. It is a starting state rather than a loophole — the limits lift when the verification completes, and the entity is still required. "You cannot send without verification" is not true, and we would rather say that than win an argument with a false claim.

What is needed instead

An API key, and a phone that says hello.

Make a key in the dashboard. It begins jak_.
Whoever is to be messaged taps a link and sends one message from their own phone. That message is both the verification and the consent — and it is an ordinary phone, already on WhatsApp, not a spare line.
Send.

curl -X POST https://api.jabee.ai/api/v1/alerts \
  -H "Authorization: Bearer $JABEE_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"title":"Deploy failed","body":"api #1043 on main"}'

That is the whole setup. There is nothing to register because the number, the Meta portfolio and the approved template are ours, and the message arrives from a number that cannot be banned for being yours.

Three things you can send this way

What	Shape	Where
Alerts	A notice with nothing to answer: a build failed, a payment bounced.	/docs/alerts/
Approvals	A question with buttons, and an Edit button that returns free text. Your code waits for the answer.	/docs/approvals/
Heartbeats	A URL your job pings; silence past the deadline is what raises the alert.	/docs/heartbeat/

And they come back the other way: a reply typed on that phone reaches your own server as a signed webhook, so a message from a phone can be an instruction to your system. That is here.

What this cannot do

The limits are the product, not a footnote, and all of them come from one fact: the number is shared.

It cannot message your customers. Not a sign-up confirmation, not an order update, not a one-time code. A shared number messaging strangers is exactly what gets numbers banned, so it is refused by design rather than discouraged.
One destination per business. Alerts and approvals go to the handset you verified, or the account owner's phone. There is no rota and no second person: to reach several people you connect your own WhatsApp number and send from there, which is also where the quality rating you spend should sit.
Our template's shape, not yours. The wording around your message is a template Meta approved for us. You fill the parameters.
A daily cap, and a platform-wide brake. One business can create 200 requests in 24 hours, and if the whole platform's sending or its share of ignored messages passes a threshold, alerts are held for everybody while approvals keep going. One number's standing with Meta is everybody's.

If any of those is a problem, the answer is not a workaround: it is your own number, and then it is your number, your templates and your relationship with Meta.

The other route, and why it ends the way it does

Search this question and most of what comes back is a bridge that scans a QR code and drives a personal WhatsApp account. It works, it is quick, and it is against WhatsApp's terms — the libraries behind it say so in their own documentation. Accounts driven that way get banned in waves, with no warning and no appeal, including accounts that had run quietly for years.

The cost is not the ban, it is what the number was carrying: the conversation history, the contacts, and the thing your customers have saved under your name. A borrowed official sender exists precisely so that the number at risk is not yours.

The same question, asked the other ways

Without a Meta business account? Yes, for your own people. The portfolio is ours.
Without a company, as an individual? Yes, the same way. You cannot hold your own WhatsApp Business Account without a registered entity.
Without business registration or a GST number? Yes — nothing here asks for either, because you are not registering anything.
Without a website? Yes. A website matters to Meta's review of your business; there is no review here.
Without a phone number? Yes to send; the phone that receives is a real phone you already use.
For personal use, on my own projects? That is the ordinary case: a cron job, a home server, a deploy, an agent that needs a decision. The messages go to you.
Without an approved template? Yes. Template review is the slowest step in the official route and it has already happened.

Questions

Can I use the WhatsApp API without business verification?

You can send to your own verified people through a provider whose number and message template are already approved, which is what Jabee does: you need no number, no Meta business portfolio, no verification and no template of your own. What you cannot do that way is message your customers — that needs a number registered to your business, and Meta's verification with it.

Does Meta let you send with verification still pending?

Yes, on your own Cloud API account, under hard-coded limits on how many people you can message and how many templates you can have. It is a starting state, not a way around verification: the limits lift when the verification completes. That is a different thing from needing no account at all.

Can I get the WhatsApp API as an individual, with no company?

Not your own. Meta requires a registered legal entity for a WhatsApp Business Account, which is the wall most side projects hit. Sending through a provider's number does not need one, because the entity, the number and the template belong to the provider.

Do I need a spare phone number?

Not to receive. The phone that gets the messages is an ordinary phone that is already on WhatsApp — it verifies itself by sending one message. A number of your own is only needed to send as yourself, and then it must be a number not already registered on WhatsApp.

Is this an unofficial gateway or a QR-code bridge?

No. Messages go over Meta's official Cloud API on a registered number with Meta-approved templates. Bridges that drive a personal account by scanning a QR code are against WhatsApp's terms, and the account they are linked to can be banned without warning — which is the thing a borrowed sender exists to avoid.