Phone Number Validator is a simple tool for validating if a phone number is valid or not. It checks the phone number format and the country code to see if the phone number is valid.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Phone Number Validator response payload
}
}
About the Phone Number Validator API
Phone Number Validator works by validating the phone number format and the country code to ensure that the phone number is valid. It uses predefined rules and algorithms to validate the phone number, then returns the validation result.
What people use it for
- User Registration
- Use the Phone Number Validator API to validate phone numbers for user registration. Use the data to verify user information and prevent fake accounts
- Contact Verification
- Verify contacts by using the Phone Number Validator API to validate phone numbers. Use the data to ensure accurate contact information and improve communication
- Lead Generation
- Generate leads by using the Phone Number Validator API to validate phone numbers. Use the data to qualify leads, improve data quality, and increase conversion rates
- Fraud Prevention
- Prevent fraud by using the Phone Number Validator API to validate phone numbers. Use the data to detect suspicious activities, verify identities, and protect against scams
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Phone Number Validator
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Phone Number Validator API do?
How do I authenticate Phone Number Validator API requests?
How much does the Phone Number Validator API cost?
How fast is the Phone Number Validator API?
What response formats does the Phone Number Validator API support?
What HTTP method does the Phone Number Validator API use?
Request parameters — GET /v1/phonenumbervalidator
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
numberRequired | string | 816-555-1017 | The phone number to validate |
countryRequired | string | us | The country code of the phone number (e.g., us, uk) length 2-2 |
curl "https://api.apiverve.com/v1/phonenumbervalidator?number=816-555-1017&country=us" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/phonenumbervalidator
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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",
"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.
| Field | Type | Example | Description |
|---|---|---|---|
country | string | "US" | The country code that was supplied with the request |
detectedCountry | string | "US" | The ISO country code detected from the number |
countryName | string | "United States" | Full name of the detected country |
countrycode | number | 1 | The international dialing/country calling code |
numberNational | number | 8165551017 | The national (significant) number without the country code |
extension | object | null | The phone extension if present, otherwise null |
isValid | boolean | true | Whether the number is valid for the given country/region |
isMobile | boolean | true | Whether the number is a mobile phone |
isVoip | boolean | false | Whether the number is a VOIP line (common in fraud) |
isDisposable | boolean | false | Whether the number is a known disposable/virtual number |
type | string | "fixed_line_or_mobile" | Line type: fixed_line, mobile, fixed_line_or_mobile, toll_free, premium_rate, shared_cost, voip, personal_number, pager, uan, or unknown |
formatted | object | {...} | |
international | string | "+1 816-555-1017" | The number in international format |
national | string | "(816) 555-1017" | The number in national format |
rfc | string | "tel:+1-816-555-1017" | The number in RFC3966 format |
e164 | string | "+18165551017" | The number in E.164 format |
riskScorePremium | number | 0 | Composite 0-100 risk score combining validity, disposable, VOIP and line-type signals (higher is riskier) |
riskLevelPremium | string | "low" | Risk band derived from the score: low, medium or high |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 10 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Phone Number Validator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/phonenumbervalidator
No SDK to install — this is a plain HTTPS call to /v1/phonenumbervalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/phonenumbervalidator" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/phonenumbervalidator
Install the Node.js SDK, then call the Phone Number Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/phonenumbervalidatorconst res = await fetch("https://api.apiverve.com/v1/phonenumbervalidator", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/phonenumbervalidator
Install the Python SDK, then call the Phone Number Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-phonenumbervalidatorimport requests
res = requests.get(
"https://api.apiverve.com/v1/phonenumbervalidator",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/phonenumbervalidator
Install the C# / .NET SDK, then call the Phone Number Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.PhoneNumberValidatorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/phonenumbervalidator");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/phonenumbervalidator
No SDK to install — this is a plain HTTPS call to /v1/phonenumbervalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/phonenumbervalidator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/phonenumbervalidator
No SDK to install — this is a plain HTTPS call to /v1/phonenumbervalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/phonenumbervalidator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/phonenumbervalidator
No SDK to install — this is a plain HTTPS call to /v1/phonenumbervalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/phonenumbervalidator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Phone Number Validator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Phone Number Validator API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Phone Number Validator API.
Data Validation
- Card Validator
- Disposable Email Checker
- Disposable Phone Number Checker
- Email Validator
- Password Strength
- Phone Number Validator
- SEO Quick Validator
- Spam Detector
- Username Profanity
Related articles
All articles →
Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read
The Phone Number Validation Rabbit HoleValidating phone numbers seems simple until you try it. Here's what makes it surprisingly complex.Read
KYC Verification API: Automate Identity ChecksBuild automated KYC checks with email validation, phone verification, IP geolocation, and BIN lookup. Here's the complete implementation.Read