POST /v3/initialize, from your server, with a secret key.
Link your own record with external_id
Pass external_id to associate the session with a record on your side. Duplicates are reported against it, so one person claiming to be two of your records surfaces as duplicate_account when you confirm.
Bind an identity with phone / email
Pass a phone or email to bind the person to a verified identifier. The identity becomes their claim to their face record, so their verified uniqueness travels across devices, browsers, and every product you run on VerifyYou. The flow challenges the identifier you supply with a one-time code, and the person can’t swap it for a different one.
Reading it back
Confirm the token as usual; findings against your linked record arrive inreasons:
All of these parameters are secret key only: send them from your server.
See the full list on
POST /v3/initialize.