List the ways to sign in the person can add
The ways they can add, in the brand's order: a wallet, an email address while they have none, and each provider the brand offers, one they sign in with already included, since another account there can be added too. Adding one can still be refused: at 20 ways to sign in (`identity_limit_reached`), or while their address isn't proved (`email_unverified`). Passkeys are listed when offered, and are added at `/v1/passkeys`, or on the hosted pages with `synq_intent=add-passkey`. Needs `me:read`.
/v1/link-methodsThe ways they can add, in the brand's order: a wallet, an email address while they have none, and each provider the brand offers, one they sign in with already included, since another account there can be added too. Adding one can still be refused: at 20 ways to sign in (identity_limit_reached), or while their address isn't proved (email_unverified). Passkeys are listed when offered, and are added at /v1/passkeys, or on the hosted pages with synq_intent=add-passkey. Needs me:read.
Authorization
bearer An access token from this issuer for its account API (resource=<issuer>/me).
In: header
Query Parameters
At most this many items, 200 at the most.
1 <= value <= 20050The previous page's next_cursor, for the page after it.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.auth.synq.build/me/v1/link-methods" \ -H "Authorization: Bearer $ACCESS_TOKEN"{ "data": [ { "method": "discord", "name": "Discord", "confirmation": { "needed": true, "by": "recent_sign_in", "with": "telegram", "with_name": "Telegram" } } ], "next_cursor": "string"}Start linking an account your app verifies POST
A link code for the person at one of the brand's “your app verifies it” providers (409 `sign_in_method_unavailable` for any other, or one turned off): put it in your service's deep link (`t.me/acmeguildbot?start=<code>`), and your server redeems it once it knows who opened that. The identity then waits, pending (`GET /v1/pending-identities`), until this same session of the app confirms it (`POST /v1/identities/{identity}/confirm`) or turns it down. The code works once, for 10 minutes, for this person, provider and session alone; a newer one drops their oldest waiting there past three. Where the provider makes sign-in links, the account becomes a way to sign in: then it wants a sign-in Synq proved within the brand's `link_reauth_window`, or the last 5 minutes when that is shorter (403 `fresh_sign_in_required`), and an account whose email address nobody proved yet takes none (403 `email_unverified`). A session a sign-in link made links nothing (403 `fresh_sign_in_required`). One person has at most 20 ways to sign in and linked accounts (409 `identity_limit_reached`). The answer is shown once, never replayed for an Idempotency-Key. Needs `me:write`.
Start adding a way to sign in POST
A link request for the person, through this app: send them to sign in from this app with its `authorization_params` added. They sign in again as themselves, then use the method being added (a wallet, an emailed code, a provider, `GET /v1/link-methods` lists them), and it joins their account; a way in another person has is never merged, unless the brand merges empty accounts (`merge_empty_accounts`) and that person's account holds nothing but it: then that account is merged into theirs at once and deleted, recorded as `user.merged` and `user.deleted`. Where that account keeps another way in and the brand moves a way in on its own proof (`move_proved_identities`, on by default), the hosted page offers “Move this wallet to this account” (or that provider's account): the proof they just made moves it, with no code, and that account keeps everything else, is emailed, and has its Discord roles and Telegram groups checked again; recorded as `user.identity_unlinked` and `user.identity_linked` (`by: moved`, `on_own_proof: true`). Signing in again is the fresh sign-in adding a way in wants, unless the browser signed in as them within the brand's `link_reauth_window` (a sign-in whose time Synq can't prove counts only for an account with no way in that can show one), so the method being added needs none of its own: a provider that can't show one (Apple, Facebook, X, Discord, GitHub, Telegram, Matrica) can be added too, and a provider is asked to show its own sign-in or authorize screen where it can, so the person sees which account they add. Methods the brand doesn't offer answer 409 `sign_in_method_unavailable`; so does an email address for an account that has one. One person has at most 20 ways to sign in (409 `identity_limit_reached`). Needs `me:write`. An account that signs in with an email address nobody proved yet takes no new way to sign in: 403 `email_unverified` until the person verifies it.