Multi-Validation API

Run every check you need in one request and get each check's result back together: one call, every signal.

Try it free you pay the per-request rate for each check included in the call

What it checks

Multi-Validation runs several Provero checks in one API request, so you don't have to call each endpoint separately and stitch the responses together yourself. You include a block for each check you want, and the API runs them and returns each check's own result. The checks you can include are email, phone (HLR), UK postcode, TPS/CTPS, IP fraud, breach, IP geolocation and name. Only the blocks you supply are processed. The response gives you the individual signals together; it is not a single score or verdict. You read and weigh each check's result yourself, exactly as you would if you called them one at a time.

What it returns

  • One result block per check , each check you include returns its own standalone result, mirroring the response of the individual endpoint
  • Only what you ask for , supply a block for each check you want; only the blocks present in the request are run and returned
  • The individual signals, together , validity, reachability, fraud, breach and location signals side by side in one response, not combined into a single verdict
  • Supported checks , email, phone (HLR), UK postcode, TPS/CTPS, IP fraud, breach, IP geolocation and name

When to use it

  • At point of capture, when you want validity, reachability, fraud and location signals on a record in a single round-trip.
  • To simplify your integration, replacing several separate API calls and the code that orchestrates them with one request.
  • When cleaning or enriching a record and you want every relevant signal back together to feed your own scoring or rules.
  • To reduce latency, running checks together rather than chaining them sequentially.

When not to use it

  • When you only need one check, call that check's endpoint directly and keep the response simple.
  • As a single trust score or pass/fail verdict, Multi-Validation returns each check's individual result for you to weigh, not one combined decision.
  • To run checks on data you don't have, only include the blocks you can populate; empty blocks aren't processed.
  • Where checks have different cadences, some signals (like list cleaning) suit batch runs rather than a per-record multi-call.

How to read the result

Read each result block on its own terms, exactly as you would the individual check. Multi-Validation is about getting the signals together in one response, not about merging them into a verdict.

Each block stands alone
The email block reads like the Email Verification response, the phone block like the HLR response, and so on. Interpret each using that check's own guidance.
Missing blocks
If you didn't supply an input for a check, there's no result for it. Only the checks you include are run.
Weigh signals yourself
Combine the blocks into your own score or rules. The API deliberately does not return a single suitability verdict.

Pricing

you pay the per-request rate for each check included in the call

Prepaid balance, spent across any check. Each request is charged at the rate for the volume band reached, and earlier requests keep their lower rate. See full pricing.

Need custom pricing? pricing@provero.io

API & bulk usage

Send one request with a block for each check you want (email, phone, postcode, TPS, IP fraud, breach, geolocation or name) and get each check's result back in one response. Only the blocks you include are run, and you're charged the per-request rate for each check in the call. Each result block mirrors the standalone endpoint's response, so you read them exactly as you would individually.

Read the API reference →

Request

{
  "email": { "email": "test@example.com" },
  "phone": { "phone": "447700900123", "route": "standard" },
  "breach": { "type": "email", "value": "test@example.com" },
  "ip": { "ip": "8.8.8.8" }
}

Response

{
  "email": {
    "email": "test@example.com",
    "deliverable": true
  },
  "phone": {
    "results": [
      { "to": "+447700900123", "status": "Live", "currentNetwork": "EE" }
    ]
  },
  "breach": {
    "value": "test@example.com",
    "type": "email",
    "leaks": []
  },
  "ip": {
    "ip": "8.8.8.8",
    "fraudScore": 0
  }
}
Common Questions

Multi-Validation FAQ

Does Multi-Validation return a single trust score or verdict?

No. It runs each check you include and returns each check's own result block. You get the individual signals together in one response and weigh them yourself. It does not combine them into a single score, suitability verdict or pass/fail decision.

Which checks can I run in one request?

You can include email, phone (HLR), UK postcode, TPS/CTPS, IP fraud, breach, IP geolocation and name. Only the blocks you supply are processed, so you run as few or as many as you need.

How is it priced?

You pay the normal per-request rate for each check included in the call, drawn from your prepaid balance. Running checks together costs the same as running them individually; it just saves you the orchestration.

How do I read the response?

Each result block mirrors the standalone endpoint's response: the email block reads like Email Verification, the phone block like the HLR response, and so on. Interpret each using that check's own guidance.

What happens if I leave a check out?

Only the blocks present in your request are run and returned. If you don't include an input for a check, there's simply no result for it in the response.

Start with this check

Create a free account, claim your credits and run Multi-Validation as a real-time API or a bulk upload. No card required.

Sign up free