Skip to main content
PATCH
Update current user profile

Authorizations

X-API-Key
string
header
required

API key authentication. Include your API key in the X-API-Key header as: X-API-Key YOUR_API_KEY

Example:

Authorization
string
header
required

JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOUR_ACCESS_TOKEN

Example:

Body

application/json

Request model for updating the authenticated user's profile information.

All fields are optional. Only provided fields will be updated, allowing partial updates without affecting other user attributes. Omitted fields remain unchanged in the database.

first_name
string | null

User's first name. Used for display in the UI and in email communications. Must be at least 1 character if provided. Set to null or omit to leave unchanged.

Required string length: 1 - 100
Example:

"John"

last_name
string | null

User's last name or family name. Combined with first_name for full name display. Must be at least 1 character if provided. Set to null or omit to leave unchanged.

Required string length: 1 - 100
Example:

"Doe"

password
string | null

New password for the user account. Note: Password updates are currently not implemented in the API. This field is reserved for future functionality. Password changes should be handled through the authentication service.

Required string length: 8 - 128
Example:

"MySecureP@ssw0rd123"

Response

User profile updated successfully with new values

User model

email
string
required
first_name
string
required
last_name
string
required
organization_id
string<uuid>
required
created_at
string<date-time>
id
string<uuid>
modified_by
string
role
enum<string>
default:app_user
Available options:
org_admin,
backoffice,
app_user,
reviewer,
publisher,
integration
status
enum<string>
default:pending
Available options:
pending,
active,
inactive
updated_at
string<date-time>
user_auth_id
string<uuid> | null