Phone Number Validator — Format, Country & Line Type

Validate, parse, normalize, and format phone numbers in bulk with country, type, E.164, national format, and validity status.

What this actor does

Validate, parse, normalize, and format phone numbers in bulk with country, type, E.164, national format, and validity status. The actor is configured for public or user-supplied sources, evidence-backed output rows, capped runs, and KVS summaries for blocked, empty, duplicate, or capped work.

What you can use it for

• Build repeatable phone number validator datasets for analysis and automation.
• Export records with source URLs, evidence fields, and run summaries.
• Run buyer-ready tasks for: Normalize phone numbers to E.164; Validate phone numbers before CRM import; Parse international phone lists.

Search-intent terms: phone number validator, e164 formatter, phone parser, phone normalization, lead list cleaning, phone validation.

Inputs

The input schema supports the actor's source fields plus cost and quality controls. Important caps include phoneNumbers, defaultCountryCode, maxConcurrency. Public task examples below provide small, safe starting inputs.

Outputs

Paid dataset rows and paid KVS artifacts are written only after the configured PPE charge succeeds. Rows include source/evidence fields where the actor can determine them and avoid fabricated values.

Key-value store reports

Every run writes SUMMARY.md and SUMMARY.json. Diagnostic CSV or JSON reports are used for blocked pages, no-result pages, duplicates, unsupported inputs, and capped runs instead of paid dataset rows.

Pricing

This actor uses pay-per-event pricing with Apify platform usage included in the event prices. Store discount tiers are configured for FREE, BRONZE, SILVER, and GOLD users.

Event	Unit	FREE	BRONZE	SILVER	GOLD
actor-start	run	$0.00180	$0.00180	$0.00162	$0.00144
number-validated	record	$0.00195	$0.00195	$0.00176	$0.00156

Primary paid output event: number-validated. Runtime-paid dataset rows and runtime-paid artifacts use this active paid-output event unless a future pricing revision adds an actor-specific artifact boundary with matching code.

Cost controls and max-charge behavior

Default max charge: $2.00. When the run reaches the max charge or an event-charge limit, it stops gracefully and writes free summary diagnostics without adding unpaid dataset rows.

Platform usage / proxy / browser / API notes

The configured model is fixed-inclusive PPE: platform usage is included in event prices and the platform-usage pass-through toggle is off. Features that require browser rendering, proxies, provider APIs, or additional fetches are bounded by the input caps and priced through explicit events.

Reliability notes and limitations

The actor processes public or permissioned inputs only. Blocked pages, login walls, unsupported formats, empty results, and provider errors are recorded as diagnostics. The actor does not fabricate rankings, prices, reviews, sentiment, traffic, compliance status, or private contact data when source evidence is unavailable.

Example inputs

{
  "phoneNumbers": [
    "+14155552671",
    "+442079460958",
    "+81312345678"
  ],
  "defaultCountryCode": "US",
  "detectCarrier": true,
  "detectLineType": true,
  "includeTimezone": true,
  "includeGeocode": true,
  "strictValidation": false,
  "outputFormat": "all",
  "onlyValid": false,
  "onlyMobile": false,
  "maxConcurrency": 50
}

Public task examples

• Normalize phone numbers to E.164: Dataset rows matching the normalize phone numbers to e.164 use case, plus SUMMARY.md and SUMMARY.json reports in the key-value store.
• Validate phone numbers before CRM import: Dataset rows matching the validate phone numbers before crm import use case, plus SUMMARY.md and SUMMARY.json reports in the key-value store.
• Parse international phone lists: Dataset rows matching the parse international phone lists use case, plus SUMMARY.md and SUMMARY.json reports in the key-value store.

Ethical/allowed-use notes

Use this actor only for public data, owned files, or sources you have permission to process. Respect source terms, privacy expectations, robots guidance, and applicable laws. Do not use the actor to collect secrets, bypass access controls, or make unsupported legal, financial, medical, or compliance decisions.