Phone Number Validation API - Bulk Validator & Formatter avatar

Phone Number Validation API - Bulk Validator & Formatter

Pricing

$1.00 / 1,000 results

Go to Apify Store
Phone Number Validation API - Bulk Validator & Formatter

Phone Number Validation API - Bulk Validator & Formatter

Bulk phone number validation and formatting for lead lists in any country: E.164, valid/possible checks, line type (mobile/landline), carrier metadata, location and time zone. Numbering-plan validation, not live HLR. $0.001/number.

Pricing

$1.00 / 1,000 results

Rating

0.0

(0)

Developer

Ava Torres

Ava Torres

Maintained by Community

Actor stats

1

Bookmarked

165

Total users

6

Monthly active users

16 hours ago

Last modified

Features

Limited permissions

Share

Phone Number Validation API – Bulk Phone Validator, Formatter & Carrier Lookup

Validate and normalize phone numbers in bulk for any country. Paste a list in any format ((415) 555-2671, +44 20 7946 0958, 5551234567) and get the E.164 number, international and national formats, valid and possible checks, line type (mobile, fixed line, toll-free and so on), carrier where known, location and time zone. $0.001 per number. No API key, no start fee.

Why use this actor?

  • Clean a lead list in one run. Thousands of numbers, any format, any country.
  • E.164 output. Ready for CRMs, dialers, SMS tools and dedupe.
  • Line type. Separate mobiles from landlines before an SMS or call campaign.
  • Time zone. Call people during their own business hours.
  • Cheap. $1 per 1,000 numbers, with no run start fee.

Who uses it

Use caseWhat you get
Sales & lead genDrop invalid numbers and normalize the rest before importing to a CRM or dialer.
SMS marketingKeep mobile numbers and remove landlines and invalid entries.
Data cleaning & dedupeE.164 keys make duplicate detection reliable.
Call centersTime zones for compliant calling windows.
Form & signup QACatch malformed numbers in bulk exports.

Quick start

  1. Click Try for free.
  2. Paste numbers into Phone Numbers, one per line.
  3. Set Default Region for numbers without a country code (for example US, GB or DE).
  4. Press Start, then export to CSV, Excel or JSON.

Copy to your AI assistant

Use the Apify actor pink_comic/phone-number-validation to validate these numbers with default region US: (415) 555-2671, 212 555 0100, +44 20 7946 0958. Return E.164, valid yes or no, line type and time zone as a table.

Input example

{
"phoneNumbers": ["(415) 555-2671", "+44 20 7946 0958", "+49 30 123456", "+81 3-1234-5678"],
"defaultRegion": "US",
"maxResults": 1000,
"includeCarrier": true,
"includeGeocoding": true,
"includeTimezone": true
}

What data you get

FieldExample
input+1-202-555-0173
validtrue
isPossibleNumbertrue
phoneNumberE164+12025550173
international+1 202-555-0173
national(202) 555-0173
countryCode / regionCode1 / US
numberTypeFIXED_LINE_OR_MOBILE, MOBILE, FIXED_LINE, TOLL_FREE, VOIP…
carrierOriginal carrier, when the numbering plan includes it
geocodingWashington D.C.
timezonesAmerica/New_York

Pricing

EventPrice
Each validated number$0.001

Scheduled price change: from November 26, 2026, the price becomes $0.0015 per validated number, still with no start fee Apify notifies existing users and shows the new price in the pricing tab ahead of time.

10,000 numbers cost $10. There's no start fee.

Integrations

  • API: use the Apify API or the Python and JavaScript clients, including synchronous run-and-get-results calls.
  • No-code: Zapier, Make, n8n, Google Sheets and webhooks, for example to validate each new form signup.
  • AI agents (MCP): connect Claude, ChatGPT or Cursor to https://mcp.apify.com and call this actor as a tool.

FAQ

Does this check whether a number is live or reachable? No. It validates against Google's libphonenumber numbering-plan metadata, so it tells you whether a number is correctly formed and assigned to a valid range for its country and line type. It doesn't ping the network, send an OTP or confirm who owns the number.

Is the carrier the current carrier? It's the carrier the number range was originally assigned to. Ported numbers can show the original carrier, and the field can be empty.

Why is a US number "FIXED_LINE_OR_MOBILE"? In the US and Canada, landlines and mobiles share number ranges, so the metadata can't tell them apart.

Which countries are supported? Every country in libphonenumber, which covers all ITU country codes.

Support

Open an issue on the Issues tab. Bug reports and feature requests are welcome.

⌂ 换网址