dev.knotless.uploadAvatar

Uploads the body, a PNG, JPEG, WebP or GIF, as a blob of the account logged in to this appview's web pages, and names it as the picture of its dev.knotless.profile record, as `knotless account profile --avatar` does: one that is not a PNG or JPEG, or is over 1,000,000 bytes, is drawn again as a JPEG that fits, at most 2000 pixels on its longest side. Requires the session cookie the pages' login sets: the appview writes with the session it keeps for that account.

Details · procedure
Kindprocedure
Authorityknotless.dev
Indexed

Procedure

procedure · POST

Input

*/*

Output

application/json

Errors

InvalidRequest

No picture, or one that is not a PNG, JPEG, WebP or GIF.

AuthenticationRequired

No account is logged in to the pages, or its session has ended.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Uploads a picture to show in a pull, an issue or a comment, as the account logged in to this appview's pages.

  • An account's own picture.

  • Changes how the account logged in to this appview's pages shows on knotless.

  • Upload raw image bytes to the authenticated viewer's own PDS, mediated by the AppView using its server-held session (confidential OAuth client only). Mirrors com.atproto.repo.uploadBlob. The returned blob ref is passed into createPost, createComment, or putProfile to attach it to a record. This endpoint applies no per-context size limit beyond a generous ceiling — the PDS enforces the real limit (post/comment 5MB, avatar 1MB, banner 2MB) when the blob is actually attached to a record.

  • Upload an image for the profile avatar or banner. Requires group.configure. Binary input like com.atproto.repo.uploadBlob; the group is a parameter because the blob has to land in that group's repo for a profile record to reference it.