Update User
User Endpoints
Update User
Update a user’s profile fields, including avatar and banner images
PATCH
Update User
Updates one or more profile fields for the specified user. The requesting user must own the account, or use a service or master token to update any user. Supports direct image uploads for the avatar and banner viaDocumentation Index
Fetch the complete documentation index at: https://docs.replyke.com/llms.txt
Use this file to discover all available pages before exploring further.
multipart/form-data. Uploaded images are processed, stored in Supabase, and the old files are automatically cleaned up after a successful update.
Send
application/json for text-only updates. Use multipart/form-data
when uploading image files.Authentication
Requires a valid user auth token. The authenticated user must match:userId, or the request must carry a service/master token.
Path Parameters
The Replyke user ID (UUID) to update.
Body Parameters
All fields are optional. Only the fields provided are updated.Display name.
New username. Automatically lowercased and sanitized. Returns 409 if already
taken by another user.
URL of the user’s avatar image. Ignored if
avatarFile is also provided.Short bio text.
ISO 8601 datetime string for the user’s date of birth (e.g.
"1990-06-15T00:00:00.000Z").Geographic location stored as a PostGIS point.
Public custom key-value data. Replaces the existing value.
Private custom key-value data. Not returned to other users. Replaces the
existing value.
Avatar image file (multipart). Maximum 50 MB. Must be a valid image.
Requires
avatarFile.options to be present in the same request.Banner image file (multipart). Maximum 50 MB. Must be a valid image.
Requires
bannerFile.options to be present in the same request.Response
On success, returns HTTP200 with the updated user’s authenticated profile:
Unique user ID (UUID).
External identifier from your system.
User role (e.g.,
"visitor").User’s email address.
Updated display name.
Updated username.
Avatar URL.
Bio text.
Public custom key-value data.
Reputation score.
Whether the user’s email has been verified.
Whether the user account is active.
ISO timestamp of the user’s last activity.
Active suspensions on the account.
Processed avatar image with variants.
Processed banner image with variants.
Active auth methods (e.g.,
["password", "google"]).ISO timestamp of account creation.
When
name, username, or bio changes, the user’s semantic search
embedding is automatically updated asynchronously.Error Responses
Not Authorized — 403
Not Authorized — 403
User Not Found — 404
User Not Found — 404
File Too Large — 413
File Too Large — 413
Invalid Image — 422
Invalid Image — 422
Missing Image Options — 400
Missing Image Options — 400
Validation Failed — 400
Validation Failed — 400
Invalid Params — 400
Invalid Params — 400
See Also
useUserActionshook —updateUser- Storage: Upload Image
- User data model

