Skip to main content
By default a person you verify is a guest, recognized only by the device ID in their browser. Account linking ties the verification to your own user record and, optionally, binds an identity that makes the person a member: a durable 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. It comes straight back when you confirm, so you can match the verified human to your user without a lookup table.

Bind an identity with phone / email

Pass a phone or email to bind the person to a verified identifier. This is what makes them a member: 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.
Binding fails if that phone or email is already claimed by another person: an identity is one human. Handle the 400 by routing the user to sign in and re-assert their existing claim rather than creating a duplicate.

Reading it back

The linked external_id is returned on the confirmation, so the result is self-describing:
All of these parameters are secret key only: send them from your server. See the full list on POST /v3/initialize.