Onboarding validation without unnecessary friction
Place the right check at the right moment, with accessible feedback and real recovery routes.
Read the guideVALIDATION API · A CLEARER START
Good data.
Better journeys.
Bring clarity to driver’s license, passport, address, mobile number, and legal name data—with validation signals your team can actually explain.
Practical documentation. Fictional examples. No sign-up.
✳EXPLICIT SIGNALS. NO MYSTERY SCORES. / ILLUSTRATION
valid.signal
DOCUMENT DATA
Real-world namesOriginal value preserved
ADDRESS SIGNALS
A more useful kind of clarity.
structurepass ✓
residencenot_checked
response.json
{ "demo": true, "status": "needs_review", "next_action": "review" }
Five data types Consistent JSON patterns Clear evidence boundariesVALIDAPI / DATA CLARITY, BY DESIGN
Driver’s license validationPassport validationHome address validationMobile number validationLegal name validation
A CHECK FOR THE QUESTION AT HAND
Five data types.
One thoughtful approach.
Choose the data you’re working with. Understand the signals, the context, and what a result does—and doesn’t—mean.
01 / DOCUMENT DATA
Driver’s license
Separate document structure, field consistency, and source comparisons.
Explore driver’s license validation
02 / DOCUMENT DATA
Passport
Understand document fields and MRZ consistency without assuming authenticity.
Explore passport validation
03 / CONTACT DATA
Home address
Make address components clearer while preserving the destination that matters.
Explore home address validation
04 / CONTACT DATA
Mobile number
Keep formatting, number-type signals, and possession in their own lanes.
Explore mobile number validation
05 / PERSON DATA
Legal name
Respect real-world names. Make normalization and comparison transparent.
Explore legal name validation
BUILT AROUND CLARITY
One response.
No mystery scores.
A useful result tells a story: what was checked, what remains unknown, and what should happen next.
Say what actually passed.
Keep structure, source comparison, and identity separate.
Make room for “not checked.”
Missing evidence is not the same as a failed check.
Give the next step a name.
Correction, review, and retry need different routes.
address.response.json
{
"demo": true,
"request_id": "sample_address_001",
"status": "needs_review",
"checks": {
"structure": "pass",
"postal_reference": "not_checked",
"residence": "not_checked"
},
"reasons": [
{
"code": "example_only",
"message": "Fictional fixture; no real-world validation performed."
}
],
"next_action": "review_requirements"
}LOCAL EXAMPLE · NO NETWORK REQUESTJSON / UTF-8
Home address: fictional response example. These predefined signals illustrate a proposed contract, not a check of real data. View service scope.
FROM INPUT TO A USEFUL NEXT STEP
Better validation is a journey.
01 / FRAME
Start with the purpose.
Know which action the check supports. Collect only the context that action needs.
02 / INTERPRET
Keep the signals separate.
Read the individual observations. Do not turn a format check into an identity claim.
03 / GUIDE
Make the next step helpful.
Offer a correction, a review, or a real alternative—not another unexplained error.
Collect less.
Explain more.
Build a useful diagnostic trail without turning your logs into an identity-document archive.
Explore the security approachPeople aren’t
regular expressions.
Preserve real-world names and give unfamiliar inputs a respectful path forward.
Rethink name validationTHE VALIDATION JOURNAL
Good questions.
Practical answers.
Driver’s license validation: a developer’s guide to clear signals
Compare structure, field consistency, source checks, and jurisdiction coverage without overclaiming.
Read the guide
Validation API errors that developers and people can understand
Design stable reasons, useful next actions, and truthful messages for every incomplete outcome.
Read the guideA LITTLE MORE CONTEXT
Clarity starts
with questions.
Understand the scope before you start building. Here are a few good places to begin.
Read all FAQsWhat does a validation API actually validate?
That depends on the method. A format check, a consistency check, a comparison with a source, and a check linking evidence to a person answer different questions. Our validation overview keeps those distinctions explicit.
Can I use this website to verify a real document?
No. This website provides documentation, educational guides, and fictional JSON examples. It does not accept documents, issue API keys, send verification messages, or perform live identity checks. Read the service scope before planning a production integration.
Which validation areas does ValidAPI cover?
The guides cover driver’s license, passport, home address, mobile number, and legal name data. Each has a dedicated page with design considerations, example fields, limitations, and a deeper editorial guide.
Is a well-formed mobile number proof of identity?
No. Formatting is a limited observation. Delivery, possession of a number, and a person’s identity are different questions. The mobile number guide explains how to keep them separate.
YOUR NEXT INTEGRATION
Make your next check
more meaningful.
Start with the right question. Build toward a clearer answer.