Bulk Phone Verification & Number Validation
Every number, traced.
Multiple numbers go in on one submission. Each row is normalized to E.164, resolved against its country’s numbering plan, and looked up for line type, carrier and risk signals — then mapped to a verdict and a score for that row.
returns inline · no queue · flat per row
What is bulk phone verification?
Bulk phone verification processes many phone numbers together instead of looking up each number individually. MultiValidator normalizes the numbers, resolves country and numbering information, identifies line type and carrier, evaluates the available risk and disposable signals, and maps those signals to a verdict and a score for each row.
It is a lookup and data-verification workflow, not a phone call or an SMS test. Nothing is dialled, and no message is sent to any number in the file.
what it is, and what it is not
- A dataset read, run once per row, returned on the submission.
- Not a call, a ping or an SMS — the handset is never contacted.
- Not proof of ownership, and not a statement about who holds the phone.
- Not a fraud verdict — risk signals are inputs, not conclusions.
six steps, one charge
What the phone verification checks mean
Format and region resolve locally; the carrier data comes from the provider dataset. Nothing leaves the process until the lookup, and the lookup is the only paid part.
Normalize & format
Parsed to E.164 against the country's numbering plan. No network call. A number that will not parse stops here.
not proof of an active line — a parsed format is not a subscriber
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.
not proof of who uses the number, only which region it belongs to
Line type
mobile, landline, voip or toll-free as the carrier reports it. VoIP is flagged, never silently failed.
not proof of how the handset behaves — it is the carrier's classification
Carrier
The carrier the range is allocated to. Context for cost and reachability.
not proof of who holds the phone, only which range the carrier allocated
Risk & disposability
Provider risk score and disposable-range flags. Medium or high risk lands risky.
not proof of fraud — a risk score is a provider signal, not proof
Verdict + score
deliverable / risky / undeliverable / unknown, mapped from the signals above, with every check and its reason attached.
not proof of the state of the handset, only the verdict the data supports
how the job runs
Inline bulk phone verification.
Phone rows come back completed on the submission itself — inline, not queued. There is no job id to poll and no download step; the response carries the verdicts.
a finished run
Four pills, one of them rarely filled.
The count is rows, not retries: a submission is processed once and comes back complete.
What information does bulk phone verification provide?
Every row carries the same fields, whether the file holds ten numbers or a thousand. The names below are the API's, so you can map them onto your own model.
Normalized phone number
Every row is parsed to E.164, so the same number written three different ways comes back as one comparable value.
Country & dial code
The dial code resolves the region and the expected national format, which is what lets the number be parsed at all.
Line type
Mobile, landline, VoIP or toll-free, as the provider dataset reports it. VoIP is a risk signal, never an automatic failure.
Carrier
The organization the number range is allocated to according to the provider dataset — context for reachability and cost, not an identification of the person using the number.
Risk & disposability
The provider's risk score and disposable-range flags. Medium or high risk lands the row risky; neither signal proves fraud.
Verdict & score
The row's verdict — deliverable, risky, undeliverable or unknown — with the score that band maps to, plus every check and its reason.
A field the provider returns nothing for comes back empty rather than guessed — and nothing here probes the handset.
four verdicts, unknown included
Bulk phone verification results
The fourth state is real. A number whose provider returns no definitive validity flag is unknown, and reporting it as valid would be a guess. Risky is not a softer word for invalid either: a VoIP or disposable range is still a reachable number.
the four states
what the signals mean
- line type
mobile, landline, voip or toll-free, as the carrier reports it. VoIP is flagged risky — never silently failed.
- carrier
the carrier the range is allocated to. Context for cost and reachability, not a judgment about the number.
- risk
the provider's score and disposable-range flags. Medium or high lands risky rather than undeliverable.
What bulk phone verification cannot tell you
A lookup reads provider data about a range. It never touches the handset, so these are the things it cannot establish — and we would rather say so than let a verdict imply them.
- no callThe number is never dialled, and no call is placed to it.
- no handset pingNothing is sent to the device in either direction.
- no SMSNo message is sent to the number.
- no ownershipA carrier range is not a person. Ownership cannot be read from provider data.
- no live statusWhether the handset is on, reachable or switched off right now is not in the dataset.
- no deliverabilityWhether a message would actually arrive is not something this lookup can determine.
Provider data vs. live phone verification
The distinction matters more than any single verdict: one reads a dataset about a range, the other contacts the handset. Only the first one runs here.
Provider data — what runs here
MultiValidator reads the provider and carrier dataset: the numbering plan, the line-type classification, the carrier allocation, and the risk and disposable flags.
- Country and dial code
- Line type
- Carrier allocation
- Risk and disposable flags
Live handset verification — not performed
A live check contacts the handset, usually with an SMS or a code, to prove possession. That is a different product, and it is not what this workflow does.
- Message delivery to the handset
- Handset response
- Proof of possession
- Not performed by MultiValidator
A valid format is not a live subscriber. Those are two different claims, and this workflow only makes the first one.
Bulk phone verification use cases
The same workflow, pointed at the places phone numbers enter your systems — and at the records you already hold.
CRM data validation
Validate phone-number data before using it in customer records.
Lead list cleaning
Review phone numbers in prospect datasets.
Contact database maintenance
Normalize and classify existing phone-number data.
Customer data imports
Process phone numbers before adding them to internal systems.
Regional number processing
Normalize numbers across different country and numbering formats.
Risk-aware data review
Identify VoIP, disposable-range, or elevated-risk signals where available.
Pairs with bulk email and bulk BIN when a file carries more than numbers, and with domain and IP lookup for the infrastructure behind an address.
Bulk phone verification vs. single phone lookup
Neither is better in the abstract — the split is the shape of your input. One number or a file of them.
Single phone lookup
One number per request, which suits a form that submits a value and waits for its verdict.
- One number per request
- Verdict in the response
- The same checks and reasons
Bulk phone verification
Many numbers in one submission, each with its own verdict and signals — completed inline, with no job to poll.
- Many numbers per submission
- Completed on the submission
- Row-level verdicts
- Row-level signals
The single-number path is the phone validation product page, and it runs the same checks against one value.
Bulk phone verification credits
Six steps run per row and one of them is paid. There is no quality selector on this product — nothing to choose, and nothing that changes the price of a lookup.
1 row
One processed phone row is charged at the current phone rate configured by the administrator.
780 rows
780 credits, flat. The count is rows, not requests, and no row is charged twice.
no picker
Format and region resolve locally; the lookup is the only paid part. There is no depth or quality tier to select.
See the current per-credit rates on pricing.
known limits
Bulk phone verification coverage & limitations
Carrier and line type are provider data, not a probe of the handset.
Coverage varies by region: the dataset is strongest in countries the provider covers well, and thinner elsewhere.
Carriers recycle and reassign ranges, so a range that parses today can belong to someone else tomorrow.
A match describes an allocation, not the person holding the phone.
The listing above is the honest shape of it: strong where the provider covers well, thinner elsewhere, and never a claim about who holds the handset.
how it works
How bulk phone verification works.
Every number in the file is resolved against its numbering plan and looked up for the signals that decide its verdict.
- 01
Each number is normalized
Every extracted value is parsed to E.164, the format that survives country and formatting differences.
- 02
Then resolved, signal by signal
Country and dial code, line type, carrier, and the provider's risk and disposable flags — each read separately.
- 03
The verdict is mapped from those signals
Deliverable, risky, undeliverable, or unknown when the provider returns no definitive validity flag. VoIP ranges and elevated risk land risky, not invalid.
- 04
Results return inline
The same submission returns completed results. There is no job to watch and nothing to poll — unlike bulk email.
Bulk phone, drawn
- Formatpass
- Line typewarn
- Carrierpass
- Riskwarn
A skipped check means the provider returned nothing for it — not that it passed.
Carrier and line type are provider data, not a probe of the handset; nothing is ever dialled; we cannot see SMS deliverability; and coverage varies by region.
Bulk phone verification API
Bulk phone lookup is available over the API, not just the dashboard. Submit a list of numbers to POST /api/v1/bulk with kind: "phone" and the request comes back completed — no 202, no job id, and no status endpoint to poll.
Authenticate with the same API keys the dashboard issues: Authorization: Bearer mv_<64 hex>. Each row in results carries its own verdict, classification, score and details, so a file can be reconciled row by row. The response also carries the state totals and the credits consumed.
The full contract — request limits, error codes and the status shape — lives in the API documentation.
$ curl -X POST https://api.multivalidator.io/api/v1/bulk \ -H "Authorization: Bearer mv_<64 hex>" \ -H "Content-Type: application/json" \ -d '{"kind": "phone", "phones": ["+14155550134", "+14155550199"]}'{ "success": true, "data": { "kind": "phone", "status": "completed", "total": 2, "deliverable": 1, "risky": 1, "undeliverable": 0, "unknown": 0, "results": [ { "kind": "phone", "target": "+14155550134", "status": "deliverable", "classification": "safe", "score": 92, "is_valid": true, "details": { "provider": "multivalidator", "lineType": "mobile", "carrier": "Twilio", "countryCode": "US", "countryName": "United States", "nationalNumber": "4155550134", "valid": true, "isDisposable": false, "riskScore": 8 } }, { "kind": "phone", "target": "+14155550199", "status": "risky", "classification": "risky", "score": 62, "is_valid": false, "details": { "provider": "multivalidator", "lineType": "voip", "carrier": "Twilio", "countryCode": "US", "countryName": "United States", "nationalNumber": "4155550199", "valid": true, "isDisposable": false, "riskScore": 58 } } ] }, "credits": { "used": 0.5, "remaining": 416.5, "quality": "standard" }, "creditsRemaining": 416.5, "creditsConsumed": 0.5}
Bulk phone verification FAQ.
The questions this workflow gets asked most — answered the same way the API answers them.
Bulk phone verification processes many phone numbers in one submission instead of looking them up one at a time. Each row is normalized to E.164, resolved against its country's numbering plan, looked up for line type, carrier and provider risk signals, and mapped to a verdict and a score.
Stop mailing ghosts.
Start with free credits. No card, no call, no “book a demo”.