Start uploading a picture
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`.
/v1/profile/picture/uploadsAnswers 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.
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/problem+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/profile/picture/uploads" \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "content_type": "image/jpeg", "content_length": 482113 }'{ "file_id": "fil_01h455vb4pex5vsknk084sn02q", "url": "https://app.acme.example", "headers": { "content-type": "image/jpeg" }, "expires_at": "2026-10-21T12:00:00.000Z"}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`.
Choose a picture PUT
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`.