🔎 WhatsApp Number Lookup & Verification — Bulk Check, Profile Photo, Business Data

Normalize authorized phone lists and request available WhatsApp registration, profile and business information. Returned fields vary by source, cache age and privacy settings; complete profiles and current registration are not guaranteed.

Just need true/false validation? Use the lighter WhatsApp Number Validator (check its current tiered Pricing tab). This actor is for teams who need enrichment — profile photos, business email & website, about text and lead scoring — to prioritise outreach.

Phone-list research with explicit live and cached context

Use WhatsApp Number Lookup to normalize a permitted phone list and inspect available registration, profile and business observations. CRM teams can standardize E.164 records; an account owner can review their own business information; an analyst can compare available fields without treating missing data as a verified negative. The Actor does not send a WhatsApp message.

Question	Field/context	Boundary
Is the number structurally valid?	valid, e164 and region metadata	Numbering-rule validity is not active service or reachability
What registration answer is available?	onWhatsApp, whatsappStatus	A cached answer is historical; an unknown live answer stays unknown
What public details were returned?	Photo/status and business fields	Privacy settings, source support and missing data limit coverage
How should a worksheet be prioritized?	leadScore and available signals	An uncalibrated heuristic, not purchase intent or consent

Use numbers you are authorized to process. Keep lookup context and dates with the export; a profile photo, display name or business flag does not prove identity or permission to contact anyone.

What you get per number

Field	Description	Needs a token?
onWhatsApp	Is the number on WhatsApp right now (true/false)	No
profilePhotoUrl / hasProfilePhoto	Available public profile picture — rehosted under the relevant storage retention/access settings	No
profilePhotoStatus	Why no photo: ok / private (locked by privacy settings) / none (no photo set)	No
displayName	Public profile / business display name	No
isBusiness	Business-account flag	No
valid, e164, international, national	Validity + all phone formats	No
country, regionCode, carrier, lineType	Number intelligence	No
timezones, localTimeNow, bestTimeToMessage	When to reach them	No
leadScore (0–100), leadQuality	Ranked outreach priority	No
about	About / status text	No
businessName, businessCategory, businessEmail, businessWebsite, businessAddress, businessHours	Extended business details	No
verifiedName	Verified business name	No

No customer WhatsApp login or source API key is required. Your own Apify account and credentials are needed to run and read private outputs. Available profile and business fields are optional, not a complete-profile guarantee.

Why enrichment beats validation

Number validity, registration evidence and optional profile fields answer different research questions. Additional metadata can help manual review, but it does not establish a sales opportunity, consent or a reason to message someone.

Input

Paste numbers into Phone numbers (one per line), paste a list / CSV column into the text box, or upload a CSV/TXT file. Include the country code with a leading + (e.g. +14155552671), or set a Default country for local-format numbers.

Result caching (cheaper repeats)

Results are cached for 7 days in your own key-value store. Re-checking the same number within a week returns instantly and is billed via the cheaper result-cached event — handy for re-validating the same lists on a schedule.

{
  "phoneNumbers": ["+14155238886", "+442071838750"],
  "defaultCountry": "US",
  "businessEnrichment": true
}

Output

This is a fictional field illustration, not a verified person, business or current lookup result.

{
  "input": "+14155238886",
  "valid": true,
  "e164": "+14155238886",
  "country": "United States",
  "carrier": "",
  "lineType": "fixed-or-mobile",
  "onWhatsApp": true,
  "displayName": "Acme Plumbing",
  "profilePhotoUrl": "https://api.apify.com/v2/key-value-stores/.../photo-14155238886.jpg",
  "hasProfilePhoto": true,
  "about": "Available",
  "isBusiness": true,
  "businessName": "Acme",
  "leadScore": 88,
  "leadQuality": "hot",
  "bestTimeToMessage": "now",
  "localTimezone": "America/Los_Angeles"
}

Use the Ranked leads dataset view to sort by leadScore, or export CSV-friendly columns with exportFormat: "csv".

Every checked number is returned — each row carries its own valid / onWhatsApp / whatsappStatus flags, so you filter the results on your side (e.g. keep only registered).

Honest limits

• Online / last-seen is not available. WhatsApp hides presence from non-contacts (even the official API does not expose last-seen to third parties), so we don't claim it. Registration and optional public photo/about/business observations remain source-dependent and best-effort.
• Profile photo and about text appear only when the user made them public — Inspect profilePhotoStatus and source status; missing fields need not establish the precise reason.

Notes

• No customer login, QR scan, or API key is required. Bulk processing is built in.
• Fresh lookups can check valid numbers including fixed lines; seven-day cached rows are previous observations, not new live checks.

Small lookup inputs before a bulk export

The numbers below are illustrative test inputs, not a list of verified prospects or a promise of registration. Replace them with your authorized input list and start with one number at concurrency 1.

{
  "phoneNumbers": [
    "+14155238886"
  ],
  "defaultCountry": "US",
  "businessEnrichment": true,
  "concurrency": 1,
  "timeoutSeconds": 20
}

For formatting and registration context without requesting optional business enrichment, make that setting explicit. Required metadata is still returned when a completed row is delivered.

{
  "phoneNumbers": [
    "+14155238886"
  ],
  "businessEnrichment": false,
  "concurrency": 1,
  "exportFormat": "default"
}

For a pasted column, use numbersText and the correct defaultCountry for entries without a plus sign. Use E.164 input when the country is known instead of inferring it from your current location.

{
  "numbersText": "+14155238886",
  "defaultCountry": "US",
  "concurrency": 1,
  "exportFormat": "csv"
}

For both nested and flat output views, select both only when your consumer needs them. Understand whether each exported representation refers to the same checked number before counting distinct contacts or joining rows.

{
  "phoneNumbers": [
    "+14155238886"
  ],
  "concurrency": 1,
  "exportFormat": "both"
}

Active lookup pricing and cache meaning

Fresh delivered rows use result: $0.004 per number on Free, $0.0025 on paid plans. A row served from the seven-day cache uses result-cached: $0.003 on Free, $0.0008 on paid plans. The memory-weighted start event is $0.00005 per GB, minimum one, and platform usage is separately paid by the user.

At 256 MB, one fresh paid-plan row is $0.00255 in events including startup; one cached paid-plan row is $0.00085. These examples exclude platform work. Inspect actual event counters: a repeated number may be cached, so a control run is not automatically a new live registration observation. Cache availability depends on retained account storage.

A cached answer is a dated previous observation, not proof of registration right now. A live lookup can also be inconclusive. Keep whatsappStatus alongside onWhatsApp and do not replace null/unknown with false. Missing photo/about/business fields do not prove a private setting, absence or unregistered account unless the source explicitly supports that interpretation.

WhatsApp enrichment questions

Are photos permanent? No. Rehosted result URLs depend on Apify storage retention/access settings. Retain authorized copies separately when needed; an exported URL is not an indefinite storage guarantee.

Do valid numbers mean reachable people? No. Numbering metadata and carrier/time-zone data do not verify an active subscription, current device, message delivery or a person's location. Business WhatsApp can also use some fixed lines.

Are full profiles and contacts guaranteed? No. Optional fields depend on source support and public availability. A business email, name or photo is an observation requiring review, not a verified identity or invitation to contact.

Does leadScore prove a hot lead? No. It summarizes available metadata with heuristic weights, not a calibrated conversion probability. bestTimeToMessage is a time-zone helper, not consent, actual presence or verified recipient availability.

Does the tool contact a number? The documented operation collects/validates available data and exports results. It does not send a message, enroll contacts in a campaign or verify legal outreach permission.

n8n and developer integrations

Use this Actor in your automation or application with the existing community integrations below. An Apify account and API token are required; Actor and platform charges follow the current pricing.

• n8n community node: n8n-nodes-apivault-whatsapp-lookup. Install package name n8n-nodes-apivault-whatsapp-lookup in a self-hosted n8n instance that permits community packages.
• Python client and examples: GitHub.
• n8n source and usage: GitHub.

These are community packages. Publication on npm does not establish n8n verification or availability in n8n Cloud. Review the linked package README for supported inputs and setup.