The MyProof partner API creates sessions for assigned identity policies and provides verification and asset status through polling. Review document compatibility, result fields and retention before a pilot.
Frequently asked questions
What is an identity verification API?
An identity verification API lets a business ask for supported facts from a government ID, such as age, residency, document validity, nationality, or identity match, and receive a documented result for its product flow.
Which raw fields are excluded from the partner result?
Current partner-result documentation describes the customer's phone reading a supported document and evaluating the policy locally. It lists the ID image, document number, birthdate, address, and biometric data as omitted; confirm the target path and retention.
Is MyProof only for age checks?
No. Age is one supported predicate. The identity verification API can support residency, document validity, nationality, and identity-match checks when those facts are present on a supported document and allowed by the policy.
Can one verification combine multiple facts?
A supported policy can require age, residency, and document validity together. The documented flow evaluates supported predicates on the device and returns a bounded result; confirm the exact payload and retention for the target path.
What does the server receive?
The documented polling response includes verification status, separate asset status, the assigned policy and an opaque partner reference. Review the API contract and retention requirements for your integration.