Phone Number Validation API — Format, Carrier & Line Type avatar

Phone Number Validation API — Format, Carrier & Line Type

Pricing

from $20.00 / 1,000 phone number validateds

Go to Apify Store
Phone Number Validation API — Format, Carrier & Line Type

Phone Number Validation API — Format, Carrier & Line Type

Validate phone numbers at scale — format, line type, carrier and country — from offline libphonenumber. No paid key needed. B2B lead hygiene.

Pricing

from $20.00 / 1,000 phone number validateds

Rating

0.0

(0)

Developer

NexGenData

NexGenData

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Phone Number Validation API

Validate phone numbers at scale — format, line type, carrier and country — from offline libphonenumber data. No paid key required for the base tier. Built for sales-ops and B2B lead hygiene.

Factual validation from offline telephony metadata (Google's libphonenumber). Not an owner-identity or WhatsApp lookup.

{ "phoneNumbers": ["+14155552671", "+442071838750"], "defaultCountry": "US" }

Weekly cron (0 8 * * 1) keeps a lead list's phone column clean and dialable.

📊 What you get

Clean JSON, one record per number (fields from a live test run):

  • input — the number as supplied
  • valid — passes full validation for its region
  • possible — plausible length/shape
  • e164 — normalized E.164 (+14155552671)
  • international / national — formatted variants
  • countryCode — numeric country calling code
  • region — ISO-2 region (US, GB, …)
  • lineType — mobile / fixed_line / voip / toll_free / …
  • carrier — carrier name where derivable from prefix
  • location — geographic description where available
  • timezones — likely time zones

Pricing: $0.02 per phone number validated (Pay-Per-Event, success-billed) — about 50 numbers per $1. Plus a $0.005 actor-start.

🤖 Use with AI agents

Point Claude, the OpenAI Agents SDK, an n8n flow or any MCP-aware client at it.

Sample agent prompt:

Validate these phone numbers and return only the mobile, valid ones in E.164 with carrier.

Agentic payments (x402): Supports agentic payment via x402 — agents can call this actor with USDC, no API key required.

🔗 B2B verifier chain

Validate the whole record, not just the phone: Email Verification · Bulk Email Validator · Lead List Cleaner · Website Contact Scraper

Note on the HLR opt-in

The base tier is fully offline (format, line type, carrier prefix, region) and needs no paid key. A live HLR/carrier check is an opt-in that requires a configured carrier API key; when unset, each record is returned with offline validation and says so. No WhatsApp checking.


Offline telephony metadata (libphonenumber). Assembled for B2B list hygiene.