DEV Community

NexGenData
NexGenData

Posted on • Originally published at thenextgennexus.com

New: Phone Number Validation API — validate phone numbers at scale — format, line type, carrier and country

What it does

Phone Number Validation checks numbers at scale using offline libphonenumber metadata — returning validity, line type, carrier, region and a normalized E.164 form. The base tier is fully offline and needs no paid key. It is factual telephony validation for list hygiene, not an owner-identity or WhatsApp lookup.

Who it's for

Sales-ops and B2B teams keeping a lead list's phone column clean and dialable, growth engineers normalizing numbers to E.164 before dialing or SMS, and AI agents or n8n flows filtering a list down to valid mobile numbers.

Sample fields / output

  • valid and possible — full validation vs plausible shape
  • e164, international, national — normalized and formatted variants
  • lineType — mobile / fixed_line / voip / toll_free / …
  • carrier — carrier name where derivable from prefix
  • countryCode, region, location, timezones

Example use cases

  • Weekly list-hygiene cron that keeps a lead list's phone column clean and dialable
  • Normalize a mixed international list to E.164 before dialing or SMS
  • Filter a list down to only valid mobile numbers with carrier, via an agent

Try Phone Number Validation API on Apify →

Related actors: Email Verification · Bulk Email Validator · Lead List Cleaner

FAQ

Do I need a paid API key?

No. The base tier is fully offline (format, line type, carrier prefix, region) and needs no paid key. A live HLR/carrier check is an optional opt-in that requires a configured carrier key.

What does it cost?

$0.02 per number validated (about 50 numbers per $1), success-billed, plus a $0.005 actor-start.

Does it check WhatsApp or the owner's identity?

No. It returns factual validation from offline telephony metadata — not owner identity or WhatsApp status.

Top comments (0)