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.

📊 Sample Output

input	e164	international	national	lineType	location
+14155552671	+14155552671	+1 415-555-2671	(415) 555-2671	fixed_line_or_mobile	San Francisco, CA
+442071838750	+442071838750	+44 20 7183 8750	020 7183 8750	fixed_line	London
2025550143	+12025550143	+1 202-555-0143	(202) 555-0143	fixed_line_or_mobile	Washington D.C.
+8613800138000	+8613800138000	+86 138 0013 8000	138 0013 8000	mobile	Beijing
+61 2 9374 4000	+61293744000	+61 2 9374 4000	(02) 9374 4000	fixed_line	Australia

Real rows from run ztPHxd7WIbnmD0qM9 on build 0.0.2 (2026-09-24), unedited apart from masked emails/phones and shortened long text; fields the source does not publish are empty.

🔧 Input reference

Field	Type	Default	What it does
phoneNumbers (required)	array	["+14155552671", "+442071838750", "2025550143", "+861380013…	List of phone numbers to validate (E.164 or national format). Non-E.164 numbers are parsed using Default country.
defaultCountry	string	"US"	ISO 3166-1 alpha-2 country used to parse numbers given without a country code.
hlrCheck	boolean	false	Opt-in live carrier (HLR) check. Requires a configured carrier API key; when unset the actor returns offline validation only and says so per record.

🧾 JSON sample record

One real record from run ztPHxd7WIbnmD0qM9 (emails/phones masked, long text shortened):

{
  "input": "+14155552671",
  "defaultCountry": "US",
  "valid": true,
  "possible": true,
  "e164": "+14155552671",
  "international": "+1 415-555-2671",
  "national": "(415) 555-2671",
  "countryCode": 1,
  "region": "US",
  "lineType": "fixed_line_or_mobile",
  "carrier": null,
  "location": "San Francisco, CA",
  "timezones": [
    "America/Los_Angeles"
  ],
  "hlrChecked": false
}

💰 Pricing

Event	Price (USD)	When it is charged
Actor Start (apify-actor-start)	$0.005	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Phone number validated (phone-validated)	$0.02	Charged for each phone number validated and returned.

Pay-per-event: you pay only for what the run delivers. A run that delivers nothing bills no result events (only the actor-start event, when the actor defines one). Example: a run that delivers 100 results costs 100 × $0.02 = $2.00 plus the start fee.

🔗 Related Actors

More from the NexGenData Leads, contacts & enrichment family:

• Website Tech & Contact Audit — Tech Stack + Emails API
• Person Email Finder — Name + Company to Verified Email API
• Person Enrichment API — Name & Company to Public Profile
• Restaurant & Food Business Leads — Local Prospect Lists API
• Shopify Revenue Estimator — Store Intel API
• Shopify App Merchant Finder — Competitor App User Leads API

30 more in this family on the NexGenData Store page.

⏰ Run this as a weekly list-hygiene job (recommended)

{ "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.