Read the signed-in person's profile
Needs `me:read`.
/v1/profileNeeds me:read.
Authorization
bearer An access token from this issuer for its account API (resource=<issuer>/me).
In: header
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/v1/profile"{ "sub": "string", "email": "string", "email_verified": true, "username": "string", "name": "string", "given_name": "string", "family_name": "string", "picture": "string", "locale": "string", "deletion_scheduled_for": "2019-08-24T14:15:22Z", "created_at": "2019-08-24T14:15:22Z"}Keep a new passkey POST
Checks what the browser made from the options of `POST /v1/passkeys/registration-options` (its challenge, origin, relying party and user verification) and keeps it, and emails the person's verified address that a passkey was added. Needs `me:write`, from a sign-in in the last 5 minutes whose time Synq proved (send the person to sign in with `max_age=300`; a provider that can't show when they signed in, such as Discord, never counts), else 403 `fresh_sign_in_required`. Send `max_age` only when you need a fresh sign-in: it asks someone signed in that way to sign in again. 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. Recorded as `user.passkey_added`.
Change the signed-in person's profile PATCH
Their username, names, picture and language; null clears one. Not their email, which a sign-in method proves. Needs `me:write`. Recorded as `user.updated`.