Number Lookup API vs WhatsApp Check: What Each Returns

A comparison of generic phone number lookup APIs and WhatsApp registration checks, with guidance on when a list-cleaning workflow needs one, the other or both.

A number lookup API and a WhatsApp check answer different questions about the same phone number. A number lookup API describes the number on the telephone network, typically its format, country, carrier and line type such as mobile, landline or VoIP. A WhatsApp registration check describes a single platform: whether a WhatsApp account was present on that number at check time. Teams that send SMS or place calls need the lookup; teams deciding whether to use WhatsApp need the registration check; list-cleaning workflows that route across several channels usually run both, in that order.

Number lookup API vs WhatsApp check at a glance

Search results for this topic tend to show either vendor pages for carrier lookups or vendor pages for WhatsApp checkers, each describing only its own output. The table below puts the two side by side.

Neither result proves who holds the number or whether the person agreed to be contacted. Both are inputs to a routing decision, and both describe a moment in time.

What a number lookup API returns

"Number lookup" covers several layers, and vendors package them differently:

1. Format and numbering-plan validation. A parser such as libphonenumber checks whether a number has a valid length and prefix for its region and converts it to E.164. This runs offline and needs no network query.
2. Carrier and line type. A network lookup returns the current carrier and the type of line. Twilio's Line Type Intelligence, for example, returns a carrier name, mobile country and network codes, and a type such as mobile, landline, fixed VoIP, non-fixed VoIP or toll-free.
3. Additional risk or porting data. Some providers add porting history, SIM-swap or reassigned-number data as separate products.

These results answer telephony questions. A mobile line type suggests the number can usually receive SMS; a landline type usually cannot. A carrier lookup does not report whether the number has an account on WhatsApp or any other app, because that is not carrier data.

What a WhatsApp registration check returns

A WhatsApp check asks the platform-specific question directly. In WA Lookup, the realtime check takes one number in E.164 format and returns the result in the same response; the service_type value selects which signal you get.

ws: registration

Whether a WhatsApp account was registered on the number at check time. This is the core reachability signal for channel selection.

ws_avatar: registration plus avatar availability

Adds whether a profile photo is available and a link to it when present. A missing avatar does not mean the number is unregistered.

ws_business: registration plus business-account type

Adds whether the account is a WhatsApp Business account. It describes account type, not a verified legal company.

The check is available as a single-number API request, as a synchronous multi request of up to 100 numbers, in the dashboard, and through an MCP server for AI clients. A check that cannot be decided returns a non-zero business code and should be retried, not stored as not registered.

When to use a number lookup API, a WhatsApp check, or both

Match the tool to the decision your workflow is making:

Two patterns cause most wasted spend. The first is running carrier lookups on contacts who will only ever be messaged on WhatsApp, where line type does not change the decision. The second is using a line type as a proxy for WhatsApp: a mobile number may or may not have an account, and a number listed as VoIP or landline can still be registered on WhatsApp, so the registration check is the only direct answer.

A list-cleaning workflow that combines both

For a mixed list that will be routed across channels, this order keeps each step cheap and meaningful:

1. Normalize and validate format offline. Convert every number to E.164 with a numbering-plan library and remove duplicates. Numbers that fail parsing go to review; they are not worth a paid query.
2. Run the WhatsApp registration check on the remaining numbers. Use realtime checks for small sets, up to 100 numbers per synchronous API request for imports, or the dashboard's pasted Realtime Batch Check. For very large files, asynchronous bulk tasks accept a TXT or CSV upload and return a downloadable result file, with per-product limits listed in the documentation.
3. Run a carrier and line-type lookup only where SMS or voice is the planned channel, for example contacts that are not registered on WhatsApp but will receive an SMS fallback.
4. Store each result in its own field with its source and check date: line type and carrier from the lookup, registration and optional avatar or business-account signals from the WhatsApp check.
5. Hold undecided results apart and retry them, rather than merging them into either group.

Keeping the fields separate lets analysts see why a contact went to a given channel, and lets each signal be refreshed on its own schedule.

Evaluating providers for each step

When comparing vendors, ask questions specific to each category rather than one generic checklist.

For a number lookup API: which data packages are separate products, how line types are defined, which countries have carrier coverage, and whether batch requests exist or each number is one request.

For a WhatsApp check: whether results come back in the same response or through a task workflow, how undecided checks are reported, whether both registered and not-registered answers are charged, which regions are supported for which paths, and whether the service relies on your own WhatsApp session. WA Lookup, for instance, supports mainland China, Hong Kong and Macau numbers in small-volume realtime single checks, while its bulk file tasks do not accept those regions.

In both categories, read the current documentation for usage controls and data handling instead of relying on marketing pages, and keep consent records independent of any lookup result.

FAQ

How can teams tell whether a number has WhatsApp from a carrier lookup?

They cannot directly. Carrier and line-type data describe the telephone network, not app accounts. A WhatsApp registration check is the direct way to get that signal.

When does a team need both a number lookup API and a WhatsApp check?

When contacts are routed across channels, for example WhatsApp first with an SMS fallback. The WhatsApp check informs the first channel and the line-type lookup informs the fallback.

How should the two results be stored in a CRM?

In separate fields, each with its source and check date, so either signal can be refreshed independently and analysts can trace routing decisions.

Which step should run first in a list-cleaning workflow?

Offline format normalization and deduplication first, then the registration check, then carrier and line-type lookups only for contacts planned for SMS or voice.

Learn More

Choose the product information that fits the next step in your workflow.

• View the product documentation →
• Talk to the team →