users

Set the caller's own avatar

Store the picture a console renders for the caller, replacing any current one. Gateway-native: the registry holds the bytes and serves them; nothing is forwarded to the control plane, whose identity-provider default picture is unaffected. Send the raw image bytes as the request body: a PNG, JPEG, WebP or GIF, at most 2 MiB. The format is read from the bytes, so Content-Type is optional — send application/octet-stream, or omit it, and the type is detected; a specific type that disagrees with the bytes is rejected rather than corrected. SVG is not accepted. Self only: the owner is the verified caller, and a machine principal has no avatar.

Read it back with GET /users/{user_id}/avatar, whose path this response reports as avatar_url and which GET /users and GET /users/{user_id} carry for every user with a picture; the ?v= on it is the image's content digest, a client cache key the server ignores.

put/registry/v1/users/me/avatar

Request

  • Base URL: https://api.atlan.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.atlan.com/registry/v1/users/me/avatar
  • Auth: HTTP bearer

Headers

Content-Encoding'base64' | 'gzip, base64'

Codings applied to the request body, outermost last. Send base64, or gzip, base64 to compress first; the body is decoded before it is read and Content-Type still names the inner media type. Omit for an unencoded body.

Response

The avatar was set; avatar_url is where to read it.

avatar_urlstring required

The read route's path with the image's content digest as ?v=, so the address changes exactly when the picture does. Fetch it with the caller's bearer; it is not an <img src>.

Changes

No recorded changes to this operation across all 1 revision of this API.