Phone Validation & Verification API
Every number, traced to its carrier.
From the national format to the carrier that holds the range, each check runs with a method you can read and a reason you can audit — returned on every single lookup.
Phone validation checks
Six stages run against every number. Two of them resolve locally, and only the provider lookup leaves the building.
Normalize & format
Parsed to E.164 against the country's numbering plan. No network call. A number that will not parse stops here.
Country & dial code
The dial code resolves region and national format, so +1 415 555 0134, (415) 555-0134 and 4155550134 reach the same number.
Line type
mobile, landline, voip or toll-free as the carrier reports it. VoIP is flagged, never silently failed.
Carrier
The carrier the range is allocated to. Context for cost and reachability.
Risk & disposability
Provider risk score and disposable-range flags. Medium or high risk lands risky.
Verdict + score
deliverable / risky / undeliverable / unknown, mapped from the signals above, with every check and its reason attached.
Normalization runs locally; only the carrier lookup leaves the building.
E.164 — stage 01, drawn
Three parts, one string. The country code, the area code and the subscriber digits are separated once, then every form of the number — spaces, dashes, brackets — resolves to the same value.
Input to E.164 — stages 01–02, drawn
A raw number and its dial code go in. The dial code resolves the region and the national format, and one canonical string comes out — before a single byte leaves the process.
Carrier lookup — stage 04, drawn
One GET against the provider’s dataset answers with the line type, the carrier and a risk score. Three fields, each with its own reason string.
This is a data lookup, not a call to the handset. Nothing is ever dialled.
What is phone validation?
Phone validation is the process of checking whether a phone number follows a valid numbering format and identifying useful information about the number, such as its country, line type, and carrier. MultiValidator normalizes phone numbers to E.164 format and combines provider data with validation signals to return a clear phone verification result.
Instead of treating every correctly formatted number as valid, MultiValidator shows the individual checks behind the result, including format, line type, carrier, and risk.
what that covers
- A canonical E.164 number, normalized from the national format.
- Country, dial code and national number resolved locally.
- Line type, carrier and risk signals from the provider dataset.
How phone number validation works
Four steps, in order. The first two never leave the process; the provider answers the other two.
Normalize the phone number
MultiValidator parses the number according to the country's numbering plan and converts supported formats into a canonical E.164 representation.
Identify the country and dial code
The country and dial code help determine the expected national numbering format and provide geographic context for the number.
Detect line type and carrier
Provider data can identify whether a number is mobile, landline, VoIP, or toll-free and return the carrier associated with the number range.
Return a verdict and score
The available signals are mapped to a verdict such as deliverable, risky, undeliverable, or unknown, with the underlying checks and reasons included in the response.
One lookup, every reason.
Every verdict ships with the four checks that produced it — format, line type, carrier, risk — each carrying the reason string the engine returned. If you disagree with a verdict, you can see exactly which check moved it.
Phone number matches the expected national format and was normalized to E.164.
reason · Phone format is valid.
Phone number verification API
Integrate phone number validation directly into your application with the MultiValidator API. Send a phone number to the verification endpoint and receive structured information about its format, country, line type, carrier, risk signals, verdict, and quality score.
Use phone verification in signup forms, lead generation, CRM workflows, customer onboarding, contact-data cleaning, and other applications where reliable phone-number data matters.
For the whole contract — rate limits, error codes and bulk — read the API documentation. For lists, see bulk phone validation.
A phone lookup is charged at the current per-lookup rate configured by the administrator. A request that fails at the provider is refunded, never charged.
$ curl -X POST https://api.multivalidator.io/api/v1/verify \ -H "Authorization: Bearer mv_<64 hex>" \ -H "Content-Type: application/json" \ -d '{"kind": "phone", "phone": "+14155550134"}'{ "success": true, "data": { "kind": "phone", "target": "+14155550134", "status": "risky", "classification": "risky", "score": 62, "is_valid": false }, "credits": { "used": 1, "remaining": 418, "quality": "standard" }, "kind": "phone", "target": "+14155550134", "state": "risky", "qualityScore": 62, "latencyMs": 168, "checks": [ { "key": "format", "label": "Format", "outcome": "pass", "reason": "Phone format is valid." }, { "key": "line_type", "label": "Line type", "outcome": "warn", "reason": "Line type is voip; this is treated as risky." }, { "key": "carrier", "label": "Carrier", "outcome": "pass", "reason": "Carrier identified as Twilio." }, { "key": "risk", "label": "Risk", "outcome": "warn", "reason": "Provider risk score: 58." } ], "provider": "multivalidator", "details": { "provider": "multivalidator", "classification": "risky", "phone": "+14155550134", "rawInput": "415 555 0134", "lineType": "voip", "carrier": "Twilio", "countryCode": "US", "countryName": "United States", "nationalNumber": "4155550134", "valid": true, "isDisposable": false, "riskScore": 58, "timezones": ["America/Los_Angeles"] }, "creditsRemaining": 417.75, "creditsConsumed": 0.25}
| Status | Code | When |
|---|---|---|
| 400 | INVALID_REQUEST | kind must be one of: email, phone, whatsapp, bin. |
| 400 | INVALID_REQUEST | phone must be 6-20 characters using digits and optional + - ( ) separators. |
| 401 | AUTH_REQUIRED | API key required. Send Authorization: Bearer mv_... to use this endpoint. |
| 402 | INSUFFICIENT_CREDITS | Insufficient credits; creditsRemaining comes back in details. |
| 429 | RATE_LIMIT_EXCEEDED | Carries an X-RateLimit-Reset header. |
| 429 | DAILY_LIMIT_EXCEEDED | Your plan's daily phone cap is reached. Details carry limit, used, remaining and resetsAt; the response carries an X-DailyLimit-Reset header. |
| 502 / 503 | VERIFICATION_FAILED | Provider rejected the key, provider billing is inactive, or the provider rate-limited us. |
Four verdicts, in practice.
Illustrative rows — the shape of what comes back, with the check that decided each one.
| Number | Line type | State | Score | Reason |
|---|---|---|---|---|
| +14155550134 | mobile | deliverable | 92 | format |
| +442071838750 | landline | deliverable | 92 | line_type |
| +14155550199 | voip | risky | 62 | line_type |
| +14155550120 | mobile | risky | 62 | risk |
| +19990000000 | — | undeliverable | 12 | format |
| +14155550177 | — | unknown | 35 | — |
Sample rows for illustration — the shape is real, the rows are not. The score is the band the provider’s signals landed in, never a guarantee that a message will arrive.
Where that number comes from
Four fixed bands, mapped straight from the provider’s signals: 12 undeliverable, 35 unknown, 62 risky, 92 deliverable. There is no weighted sum to reverse-engineer — the marker sits exactly where the voip row above landed.
Four fixed bands mapped from the provider’s signals — not a weighted sum.
The four checks on that row
- Formatpass
- Line typewarn
- Carrierpass
- Riskwarn
Phone number validation use cases
The same lookup, pointed at the places numbers enter your systems — and at the records you already hold.
Validate signup phone numbers
Check phone numbers during registration and onboarding before storing them in your user database.
Clean customer data
Validate existing phone-number records and normalize different formats into a consistent representation.
Improve CRM data quality
Identify line types, carriers, and risk signals before phone numbers enter sales and customer-management workflows.
Verify leads
Check phone numbers before sales outreach and identify numbers that may require additional review.
Detect VoIP numbers
Identify VoIP numbers and expose them as a risk signal rather than automatically treating them as invalid.
Normalize international numbers
Convert supported phone-number formats into a consistent E.164 representation for applications and databases.
Pairs naturally with email validation when you collect both, and with the API documentation when you are ready to wire it up. Pricing, if you want to know what a lookup costs first.
What information can phone validation provide?
Everything below comes back on one lookup. The field names are the API’s, so you can map them straight onto your own model.
- E.164 formatted number
- Country code
- Country / region
- National number
- Line type
- Carrier
- Disposable and risk signals when available
- Time zones when provided by the provider
- Verification status
- Quality score
- Reason codes
A skip in the response means the provider returned nothing for that field — not that it passed. Nothing here probes the handset.
Phone validation vs. phone lookup
Phone lookup and phone validation answer related but different questions. A phone lookup retrieves information associated with a number, such as its carrier or line type. Phone validation focuses on whether the number follows the expected numbering format and combines available signals into a verification result.
MultiValidator combines these capabilities so developers can inspect the number and understand the reason behind its verdict from one API response.
Phone lookup
Retrieves information associated with a number, such as its line type or the carrier the range belongs to.
- Line type
- Carrier
- Country
- Time zones
Phone validation
Checks that the number follows the expected numbering format and maps the available signals to a verdict.
- Format
- Country and dial code
- Provider risk signals
- Verdict and score
Neither proves the number is currently active or that a particular person owns it. Both are dataset answers about the number itself.
If the question is specifically whether a number is registered on WhatsApp, the free WhatsApp Checker answers that one question without identifying the owner.
Known limits
A valid format is not a live subscriber. Carriers recycle numbers, so a range that parses today can be reassigned tomorrow.
VoIP and virtual ranges are flagged risky, not invalid — plenty of legitimate businesses run on them.
We cannot see SMS deliverability. Line type and carrier are provider data, not a probe of the handset.
Risk scores are the provider’s, and they differ between providers. We show the number and its band rather than laundering it into a promise.
Phone validation FAQ.
The questions this lookup gets asked most — answered the same way the API answers them.
Phone number validation checks whether a phone number follows the expected numbering format and can provide additional information such as country, line type, carrier, and risk signals.
Stop mailing ghosts.
Start with free credits. No card, no call, no “book a demo”.