Choose a picture
Makes their picture an upload of theirs, `{ "file_id": … }`, once its bytes are there: Synq reads them back, knows them by their first bytes (PNG, JPEG, WebP or GIF, never SVG), and re-encodes them as a WebP square, so nothing of the original but its pixels is kept (`picture_source` `upload`). Or a linked account's picture, `{ "identity": … }`, copied into the brand's files from the provider's own picture hosts alone (`picture_source` `linked:<provider>`). Either way `picture` is on Synq's media host, never the provider's. Needs `me:write`. Recorded as `user.updated`.
/v1/profile/pictureMakes their picture an upload of theirs, { "file_id": … }, once its bytes are there: Synq reads them back, knows them by their first bytes (PNG, JPEG, WebP or GIF, never SVG), and re-encodes them as a WebP square, so nothing of the original but its pixels is kept (picture_source upload). Or a linked account's picture, { "identity": … }, copied into the brand's files from the provider's own picture hosts alone (picture_source linked:<provider>). Either way picture is on Synq's media host, never the provider's. Needs me:write. Recorded as user.updated.
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.
An upload to finish, { "file_id": … }, or a linked account, { "identity": … }
An upload to finish, { "file_id": … }, or a linked account, { "identity": … }
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X PUT "https://example.auth.synq.build/me/v1/profile/picture" \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "file_id": "fil_01h455vb4pex5vsknk084sn02q" }'{ "sub": "usr_01h455vb4pex5vsknk084sn02q", "email": "ana@acme.example", "email_verified": true, "username": "string", "name": "Acme", "given_name": "string", "family_name": "string", "picture": "string", "picture_source": "upload", "avatar_seed": "mJ3kT0a9yZVqC1x8fR4wLb", "default_picture": "string", "picture_choices": true, "locale": "string", "deletion_scheduled_for": "2026-10-21T12:00:00.000Z", "created_at": "2026-10-21T12:00:00.000Z"}Start uploading a picture POST
Answers where to PUT the picture's bytes: a URL signed for 5 minutes, for exactly this type and length, straight to Synq's storage, which takes PUTs from Synq's own origins alone, so send them from your server. Then call `PUT /v1/profile/picture` with the `file_id`. PNG, JPEG, WebP or GIF, at most 5 MiB and 8192 × 8192; kept as a WebP square of at most 256 × 256. A person has at most 2 uploads waiting and 20 kept, and starts at most 10 an hour. Needs `me:write`.
Sign out of one session DELETE
Ends it and every grant it made: its refresh tokens stop working. Each app the session had signed in to that registered a `backchannel_logout_uri` gets a logout token; one that turned `backchannel_logout_session_required` off gets it without `sid`, so it signs the person out of every session it has. Needs `me:write`. Recorded as `user.sessions_revoked`.