Developers
Bring your users with you.
Moving sign-in is two steps: your users come over through the management API, and your apps change their issuer, client id and secret to your brand’s.
Users through the API
Make each user with their email address, whether you already verified it, their username, name, picture, locale and up to 16 KB of your own metadata. Every user you make needs an email address. Idempotency keys make a rerun safe.
No passwords to move
Synq doesn’t take another system’s password hashes today. People sign in with a code Synq emails them, or set a new password from an emailed link.
Wallet users
Someone with an email address is imported with it, signs in with an emailed code, then adds their wallet. Someone who signed in with a wallet alone can’t be imported yet: their first wallet sign-in makes a new Synq user, with a new id that matches nothing in your records, so your app links it to its own user by the wallet’s address. A bulk import that brings them is coming later, with no date yet.
New ids, your old ones kept
Every user gets Synq’s own id, the subject your apps see in their tokens from then on. Keep your old id in each user’s metadata, and Synq’s id with your own records.
Your apps, pointed at Synq
Your apps keep their OpenID Connect library and change its issuer, client id and secret to your brand’s and its app’s at Synq.
Social accounts that stay yours
On Pro and up, bring the Google, Apple or Microsoft app you use today as your own credentials, once your brand’s callback is added to it, so the consent screens people already know stay the same.
Read next
Ready to try it in your app?
Tell us what you are building and which sign-in your users need.