🌍

Phone Number Validator

Validate and parse a phone number with carrier and line type detection

GET 1 credit /v1/geo/phone-validate

curl "https://geo.toolkitapi.io/v1/geo/phone-validate?number=%2B14155552671&country=US"

import httpx

resp = httpx.get(
    "https://geo.toolkitapi.io/v1/geo/phone-validate?number=%2B14155552671&country=US",
)
print(resp.json())

const resp = await fetch("https://geo.toolkitapi.io/v1/geo/phone-validate?number=%2B14155552671&country=US", {
});
const data = await resp.json();
console.log(data);

# See curl example

Response 200 OK

{
  "input": "+14155552671",
  "valid": true,
  "e164": "+14155552671",
  "national": "(415) 555-2671",
  "international": "+1 415-555-2671",
  "country_code": 1,
  "country": "US",
  "region": "California",
  "carrier": "T-Mobile USA",
  "line_type": "mobile"
}

Try It Live

Description

Validate and parse a phone number with carrier and line type detection

How to Use

1

1. Pass the phone number in the `number` query parameter (any format: national, international, with or without country code).

2

2. Optionally set `country` to a 2-letter ISO code (default: `US`) as a fallback for numbers without a country prefix.

3

3. Inspect the `valid` field — if `true`, use the formatted fields (`e164`, `national`, `international`) for storage and display.

About This Tool

Use Phone Number Validator to parse any phone number string, validate it against E.164 rules, and return formatted versions along with country, carrier, and line type information. The endpoint accepts numbers in any common format and normalises them.

This is essential for CRM data cleaning, form validation, SMS delivery verification, and telecom analytics where you need to verify that a number is valid before sending messages or storing it.

Why Use This Tool

Form validation — Verify phone numbers at input time before saving
CRM data cleaning — Normalise phone numbers to E.164 format across your database
SMS delivery — Confirm a number is valid and identify the line type before sending
Fraud detection — Flag VoIP or toll-free numbers in contexts expecting mobile numbers
Carrier routing — Determine the carrier for number portability or routing decisions

Frequently Asked Questions

What phone number formats are accepted?

Any common format works: `+14155552671`, `(415) 555-2671`, `415-555-2671`, `4155552671`. The `country` parameter helps disambiguate numbers without a country prefix.

What line types can be detected?

The endpoint can identify: `mobile`, `fixed_line`, `fixed_line_or_mobile`, `toll_free`, `premium_rate`, `shared_cost`, `voip`, `personal_number`, `pager`, `uan`, `voicemail`, and `unknown`.

Is carrier information always available?

Carrier data depends on the country and number range. For some regions or number types, the carrier field may be null.

Start using Phone Number Validator now

Get your free API key and make your first request in under a minute.

Get Free API Key View Docs