Can the official WhatsApp API check numbers?
The short answer
Not really. There is no official validation endpoint.
What Meta's documentation says
Meta's official WhatsApp Cloud API is built for business messaging: templates, customer-service windows and per-conversation pricing. A large part of what WhatsApp itself can do — groups, channels, status, presence, contact lookups — has no endpoint there at all, which is why so many teams end up looking past it. Everything below is checked against Meta's own published reference, with the link and the date we checked it.
Restricted on the Cloud API
Paraphrase (not a verbatim quote), checked against the Cloud API reference index and the error-code guide: the reference documents no endpoint that reports whether a phone number is registered on WhatsApp; invalid recipients surface as errors on a send attempt.
Wapito is an independent product. It is not affiliated with, endorsed by, sponsored by or certified by WhatsApp or Meta Platforms, Inc. WhatsApp is a trademark of Meta Platforms, Inc.
Why the Cloud API restricts it
Meta's Cloud API reference has no contact-check node. The only official way to discover that a number is not on WhatsApp is to send it a message - which for a business-initiated conversation means a pre-approved template that you are charged for - and then read the failure. Validation therefore exists, but only as a paid side effect of sending.
The official workaround, and what it costs
Send a template to the number and treat a delivery failure as an invalid result. It works, it is charged per message, and it puts a message in front of every valid number whether or not you meant to contact them yet.
What the official route costs is not only the per-message price. Every row below is quoted from Meta's own documentation, with a link to the page and the date it was read.
| What it costs | What Meta's documentation says | Source |
|---|---|---|
| Writing to someone first | A business may send free-form messages only inside a 24-hour customer service window that the user opens by messaging or calling. Once the window closes, only pre-approved template messages may be sent. | Meta's docs checked |
| Every message you send | Meta charges for the WhatsApp Business Platform per message rather than per conversation. The earlier per-conversation model was replaced on 1 July 2025, so any comparison written before that date is out of date; free entry point windows remain an exception. | Meta's docs checked |
| Getting onto the platform | Apps that need advanced access to Meta's permissions may have to complete Business Verification, a process in which Meta collects information to verify the business entity. It is a real onboarding step with a real elapsed time, and it has no equivalent when you link a number you already own. | Meta's docs checked |
How Wapito does it
POST /contacts/checkCheck numbers for WhatsApp registration
curl --request POST \
--url https://api.wapito.com/v1/contacts/check \
--header 'Authorization: Bearer wpt_YOUR_TOKEN' \
--header 'Content-Type: application/json' \
--data '{"phones":["+15551234567","+15559876543","+15550000000"]}'When you should still use the Cloud API
You need a verified business identity
The official platform is the only route to an Official Business Account: the verified name customers see in place of a phone number, and the badge beside it. A linked number can carry a WhatsApp Business profile, but Meta will never badge it, and no provider can get you one.
You are sending marketing at scale to people who never wrote to you
That is what approved templates are for. Meta charges per message for them and treats the volume as legitimate; the same volume from a linked number is the clearest automation signal there is, and it is how numbers get banned. If outbound campaigns are the whole product, the official platform is the cheaper mistake.
You need Meta's own support and an SLA
A Business Solution Provider gives you a contract, an escalation path and a human to call when delivery stops. Wapito will tell you the moment WhatsApp restricts your number and what it did; nobody outside Meta can make it undo that, and we do not pretend otherwise.
Frequently asked questions
How many numbers can I check per day?
Your plan sets an explicit daily allowance, and the API tells you how much is left through the usage endpoint. The harder limit is behavioural: even inside your allowance, checking a large list in a short burst is the pattern that draws attention, so spread it out.
Why is this riskier than sending a message?
Because a check involves no relationship at all. Sending a message to someone who wrote to you is normal behaviour; asking the network about thousands of numbers you have never contacted is what a scraper does. The abuse systems weight that difference heavily, and so does Wapito's metering.
Does a check tell me the person's name?
No. It tells you whether an account exists and gives you the identity you would address, nothing more. Profile details are a separate call with their own privacy rules, and a contact who has restricted their profile will not reveal a name or a photo to a stranger's number.
Related
Do it with Wapito
Other ways to do it
Try it on your own number
Create a channel, link a WhatsApp number by QR or pairing code, and call the API in a couple of minutes. The Sandbox plan is free and needs no card.