SynqDocs
Account APIIdentities

Turn down an account your server verified

The person says a pending account (`GET /v1/pending-identities`) isn’t theirs, from the session of the app that made its code: it is gone, and nothing is linked. Recorded as `user.identity_rejected`. One that isn’t this session’s, or that expired, is 404. Needs `me:write`.

POST/v1/identities/{identity}/reject

The person says a pending account (GET /v1/pending-identities) isn’t theirs, from the session of the app that made its code: it is gone, and nothing is linked. Recorded as user.identity_rejected. One that isn’t this session’s, or that expired, is 404. Needs me:write.

Authorization

bearer
AuthorizationBearer <token>

An access token from this issuer for its account API (resource=<issuer>/me).

In: header

Path Parameters

identity*string

The pending identity's id

Match^idn_[0-9a-hjkmnp-tv-z]{26}$

Response Body

application/problem+json

application/problem+json

application/problem+json

application/problem+json

curl -X POST "https://example.auth.synq.build/me/v1/identities/idn_01h455vb4pex5vsknk084sn02q/reject" \  -H "Authorization: Bearer $ACCESS_TOKEN"
Empty

Confirm an account your server verified POST

Links a pending account (`GET /v1/pending-identities`) to the person, from the session of the app that made its code: it joins their account with the same id, as `GET /v1/identities` lists it, and is recorded as `user.identity_linked` with `by: app`. Where its provider makes sign-in links, the person is emailed that a way to sign in was added. One that isn't this session's, or that expired, is 404; a provider turned off since is 409 `sign_in_method_unavailable`; an account someone linked meanwhile is 409 `identity_in_use`; at 20 ways in and linked accounts, 409 `identity_limit_reached`. Needs `me:write`.

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`.