Skip to main content
By default a person you verify is anonymous, recognized only by the device ID in their browser. Account linking ties the verification to your own record and, optionally, binds a durable identity: a claim to their own face record, portable across devices and browsers. You link at POST /v3/initialize, from your server, with a secret key. 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.
An identity is one human. If the phone or email you bind is already claimed by a different face, the run settles denied with the finding in reasons (for example identity_mismatch or duplicate_account). Route the person to sign in and re-assert their existing claim rather than creating a duplicate.

Reading it back

Confirm the token as usual; findings against your linked record arrive in reasons:
All of these parameters are secret key only: send them from your server. See the full list on POST /v3/initialize.