FREQUENTLY ASKED QUESTIONS
Good questions deserve clear answers.
Understand the examples, the evidence boundaries, and the scope before making an integration decision.
A little context
goes a long way.
These answers describe the website and its published examples. They are not service-level or coverage commitments for a live API.
Read the documentationWhat 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.
What should happen when a result is uncertain?
Use an explicit state such as needs_review, unsupported, or unavailable. Explain what is known and provide the appropriate correction, alternative, or review route. A timeout should not be displayed as evidence that the person’s information is false.
Where are the examples processed?
The example explorer switches between fixed JSON samples already included in the page. It does not send your information to an API, and it has no data-entry fields. Downloaded fixtures are also fictional.
Are production pricing, coverage, or service levels published?
No production pricing, jurisdiction coverage, uptime commitment, or verification-provider relationship is asserted on this site. Discuss operational requirements through Contact; do not interpret an example as a commercial commitment.
How do I get in touch without sending sensitive information?
Email [email protected] with the data types, geography, and high-level workflow you are considering. Do not send identity documents, personal records, API secrets, or one-time codes.
Does this site support reduced motion and keyboard navigation?
The site responds to your system’s reduced-motion preference, includes a pause control for animated strips, offers visible keyboard focus, and uses native expandable FAQ controls. See the accessibility page for details and feedback options.
YOUR NEXT INTEGRATION
Make your next check
more meaningful.
Start with the right question. Build toward a clearer answer.