Phone Number Validator

Overview

A phone validation API that answers in JSON from one REST call. Send a number in +E.164 form on its own, or a national number with its two-letter country code. Validation runs on Google's libphonenumber numbering-plan data, so each number is checked against the real number ranges of its country rather than a generic pattern. Location, carrier and time zones come from libphonenumber's offline geocoding and carrier maps. The carrier is the operator the number range was first allocated to, so a ported number still shows its original network, and US and Canadian numbers carry no carrier data. The disposable flag checks the number against numbers published on temporary SMS-receiving sites.

Live Test Phone Number Validator API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

1
2

curl "https://api.apiverve.com/v1/phonenumbervalidator?number=816-555-1017&country=us" \
  -H "x-api-key: your_api_key_here"

1
2
3
4
5
6
7
8

const res = await fetch('https://api.apiverve.com/v1/phonenumbervalidator?number=816-555-1017&country=us', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

1
2
3
4
5
6
7
8
9
10

import requests

res = requests.get(
    "https://api.apiverve.com/v1/phonenumbervalidator?number=816-555-1017&country=us",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/phonenumbervalidator?number=816-555-1017&country=us", nil)
	req.Header.Set("x-api-key", "your_api_key_here")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

{
  "status": "ok",
  "error": null,
  "data": {
    "country": "US",
    "detectedCountry": "US",
    "countryName": "United States",
    "countrycode": 1,
    "numberNational": 8165551017,
    "extension": null,
    "isValid": true,
    "isMobile": true,
    "isVoip": false,
    "isDisposable": false,
    "type": "fixed_line_or_mobile",
    "isValidNumber": true,
    "nationalSignificantNumber": "8165551017",
    "location": "Missouri",
    "carrier": null,
    "timezones": [
      "America/Chicago"
    ],
    "formatted": {
      "international": "+1 816-555-1017",
      "national": "(816) 555-1017",
      "rfc": "tel:+1-816-555-1017",
      "e164": "+18165551017"
    },
    "riskScore": 0,
    "riskLevel": "low"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

Start from a template

A working app built on this API, ready to deploy with your own key. Vercel asks for the key when you deploy; the code is on GitHub to change first.

Lead Validator

Score a lead from its email and phone number: throwaway inboxes, typos, VoIP and temporary numbers.

• Next.js
• React

Also uses Email Validator

Deploy to VercelSee the template →

Use cases

Account Signup Verification

When users register, check validity and flag disposable or VoIP lines before sending one-time verification SMS codes.

CRM Lead Scrubbing

Sales platforms inspect incoming prospect numbers and standardize them into E.164 format to keep contact records clean and dialable.

Outbound SMS Routing

To prevent wasted spend on unroutable text messages, delivery systems verify that recipient numbers are mobile lines rather than landlines.

Checkout Risk Screening

Payment gateways identify virtual and disposable phone numbers during checkout to detect suspicious buyer profiles before processing charges.

Contact Time Windows

Contact centers read the returned time zone and area so calls and texts go out during the recipient's local business hours.

Other ways to use Phone Number Validator

Set up Phone Number Validator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Related

Pages that use this API:

• Block fake signupsGuides

More in Data Validation: