Phone Number Validator — Bulk Format, Carrier & Location Lookup

Validate, format, and enrich phone numbers in bulk — then download clean results as Excel, CSV, or JSON.

This Actor is a practical phone number validation API for CRM cleanup, lead-list hygiene, and contact enrichment. Paste numbers from any country, optionally set a default region for local formats, and get standardized international numbers plus country, line type, carrier, location, and timezone metadata.

• Validate and normalize phone numbers to E.164, international, and national formats
• Detect line type (mobile, landline, VoIP, toll-free, premium, and more)
• Enrich with country / region, carrier, location, and timezone
• Process lists in bulk for CRM, outreach, and compliance workflows
• Export to Excel / CSV / JSON, or connect Make, n8n, Zapier, Python, or Apify MCP / API
• Pay per event — Actor start + each result; platform usage is included (you do not pay separate Apify usage)

Important: results are based on numbering-plan and format checks. This Actor does not prove live reachability, current ownership, or OTP verification, and carrier values reflect original range metadata (not necessarily today’s carrier after number portability).

---

What does the Phone Number Validator do?

It turns a list of raw phone strings into a clean Apify Dataset of structured phone intelligence rows.

You can:

1. Paste phone numbers in mixed formats (+1 202-555-0173, (415) 555-2671, 020 7946 0958, …)
2. Set a default region (e.g. US, GB) for numbers without a country prefix
3. Optionally include carrier, location, and timezone enrichment
4. Cap how many numbers to process with maxResults
5. Optionally dedupe by normalized E.164
6. Download results or send them into your automation stack

No local setup, browser, or third-party phone API key is required to run the Actor on Apify.

---

What data can you extract?

Data point	Included
Original input + row index	✅
Valid / possible format checks	✅
E.164 normalized number	✅
International & national display formats	✅
Country calling code & ISO region	✅
Line type (mobile, fixed, VoIP, …)	✅
Carrier metadata (optional)	✅
Geographic description (optional)	✅
Timezones (optional)	✅
Structured error for unparseable rows	✅

Every run also writes a RUN_SUMMARY (counts, limits, finish time). Failed input validation writes ERROR_SUMMARY.

---

What you can do with it

1. Clean CRM and customer databases

Standardize messy phone fields into E.164 so you can dedupe contacts, merge records, and keep dialable formats across markets.

2. Improve lead-list hygiene before outreach

Flag structurally invalid or incomplete numbers before SMS, calling, or enrichment workflows — reduce bounce and wasted dials.

3. Enrich contacts with region and line type

Add country, line type, location, and timezone context for routing, compliance review, and smarter follow-up timing.

4. Format international numbers consistently

Convert local/national formats into standardized international dialing formats for global teams and multi-country campaigns.

5. Power automations and AI agents

Schedule the Actor or call it from Make, n8n, Zapier, Sheets, CRM tools, or Apify MCP / API — then pass Dataset rows downstream.

---

How to validate phone numbers (no code required)

1. Click Try for free on this Actor page
2. Paste phone numbers into phoneNumbers (prefer + country code when you have it)
3. Set defaultRegion (e.g. US) if some numbers are local-only
4. Keep carrier / location / timezone toggles on (or turn off what you do not need)
5. Click Start — open the Dataset tab when the run finishes

Start with a small batch (maxResults: 5–20) to confirm formats, then scale up.

Download as Excel, CSV, or JSON. Or connect the Dataset to your tools via Apify integrations / API.

---

Example input

{
  "phoneNumbers": [
    "+1-202-555-0173",
    "+44 20 7946 0958",
    "(415) 555-2671",
    "+81 3-1234-5678"
  ],
  "defaultRegion": "US",
  "maxResults": 100,
  "includeCarrier": true,
  "includeGeocoding": true,
  "includeTimezone": true,
  "dedupe": false
}

---

How much does it cost?

This Actor uses pay-per-event pricing:

Event	Price
Actor Start (apify-actor-start)	$0.005 per start
Result (apify-default-dataset-item)	$0.50 / 1,000 numbers ($0.0005 each)

Platform usage costs are included — you do not pay separate Apify compute usage on top of the event prices above.

Example cost estimates

Numbers processed	Approx. event cost*
100	~$0.055
1,000	~$0.505
10,000	~$5.005

*Assumes one Actor start plus $0.0005 per Dataset item. Exact start billing can scale with allocated memory (one start event per GB, minimum one).

Free Apify credit can cover a small test run — try maxResults: 5 first.

Free Apify plan limits (set by this Actor's developer)

Limit	Free Apify plan	Paid Apify plan
Runs of this Actor	10 total	Unlimited
Results per run	1,000	Up to schema max (100,000)

These caps are set by the Actor developer, not Apify. If the free-run quota is reached, the run finishes successfully with a clear status message (FREE_TIER_LIMIT) instead of a cryptic platform error.

---

Tips for best results

• Prefer numbers with a + country code when possible
• Always set defaultRegion for local formats without a country prefix
• Use dedupe when cleaning large CRM exports
• Keep batches around 100–5,000 for comfortable Console runs; raise timeout/memory for very large jobs
• Treat valid=true as “structurally valid for the numbering plan,” not “this phone rings” or “this person opted in”

---

FAQ

Does this check if a phone is online or can receive SMS?

No. It checks format and numbering-plan validity and returns enrichment metadata. It does not perform live reachability, HLR, or OTP ownership verification.

Is the carrier always the current operator?

No. Carrier values come from original number-range metadata. After number portability, the current carrier may differ.

Is location the user’s real GPS position?

No. Location is a geographic description associated with the number range — useful for region context, not live tracking.

Can I use this for marketing consent / TCPA compliance?

No. Validation is not consent. Keep your own lawful basis, opt-in records, and do-not-contact processes.

Do I need an external phone API key?

No. You only need Apify to run the Actor.

---

Integrations

Use the Dataset with:

• Apify API / MCP
• Make, Zapier, n8n
• Google Sheets, Slack, CRM tools
• Any webhook or custom script that reads Apify Dataset items

---

Related searches

phone number validation · bulk phone validator · E.164 formatter · carrier lookup · line type detection · phone number enrichment · CRM phone cleanup · lead list hygiene · international phone formatting · phone parse API