Redeem a link the app finishes
Joins the way in a link request with `finish: app` proved in the browser (`synq_link_result` on the app's redirect URI) to the person's account: once, within 5 minutes, only for the app that started it, as the person it was started for, with the PKCE `code_verifier` of the authorization request the browser went through. Anything else, a result redeemed already or another app's, person's or verifier's included, is 400 `link_result_invalid`, one answer for all. A way in that is theirs already answers 200; one another account of the brand signs in with is never merged here: 409 `identity_in_use` (`wallet_in_use` for a wallet), and the app sends them through a `browser` link request, whose hosted page offers what the brand allows. One person has at most 20 ways to sign in (409 `identity_limit_reached`). Needs `me:write`, from a sign-in on this device within the brand's `link_reauth_window` (2 hours unless the tenant chose otherwise), whichever way it was made, or from the last 5 minutes whose time Synq proved, else 403 `fresh_sign_in_required`, whose `confirm_with` names the way it was made: show the person what happens and why, then send them to sign in with `max_age=0` and `synq_method` set to it. Recorded as `user.identity_linked`, with `confirmed_by: app_session` and the `new_device` and `new_ip` signals.
/v1/link-resultsJoins the way in a link request with finish: app proved in the browser (synq_link_result on the app's redirect URI) to the person's account: once, within 5 minutes, only for the app that started it, as the person it was started for, with the PKCE code_verifier of the authorization request the browser went through. Anything else, a result redeemed already or another app's, person's or verifier's included, is 400 link_result_invalid, one answer for all. A way in that is theirs already answers 200; one another account of the brand signs in with is never merged here: 409 identity_in_use (wallet_in_use for a wallet), and the app sends them through a browser link request, whose hosted page offers what the brand allows. One person has at most 20 ways to sign in (409 identity_limit_reached). Needs me:write, from a sign-in on this device within the brand's link_reauth_window (2 hours unless the tenant chose otherwise), whichever way it was made, or from the last 5 minutes whose time Synq proved, else 403 fresh_sign_in_required, whose confirm_with names the way it was made: show the person what happens and why, then send them to sign in with max_age=0 and synq_method set to it. Recorded as user.identity_linked, with confirmed_by: app_session and the new_device and new_ip signals.
Authorization
bearer An access token from this issuer for its account API (resource=<issuer>/me).
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.auth.synq.build/me/v1/link-results" \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "result": "string", "code_verifier": "string" }'{ "id": "idn_01h455vb4pex5vsknk084sn02q", "provider": "google", "subject": "string", "handle": "ada", "email": "ada@example.com", "password": true, "provider_user_id": "987654321", "scopes": [ "phone" ], "unconfirmed_scopes": [ "telegram:bot_access" ], "has_picture": true, "added_by": "person", "created_at": "2026-10-21T12:00:00.000Z", "last_used_at": "2026-10-21T12:00:00.000Z"}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.
Read what the brand keeps about the signed-in person GET
The tenant's own JSON for this user, read-only here. Needs `me:read`.