Skip to main content
PATCH
Update Profile
CLI:

Overview

The public Bearer-token API can update profile name fields (firstName, lastName) for the current user. email and password are browser-session-only fields. Bearer API keys and generated CLI commands cannot change login credentials; those attempts return 403. A signed-in human must make credential changes through the dashboard session. Email changes also require the human to confirm the verification message before the new login email takes effect.

AI agent notes

For public API use, send at least one of firstName or lastName. Read Get Profile after a successful update and confirm the returned profile value before reporting completion. Do not attempt email or password changes with an API key, even if the user asks. Direct the human to the signed-in dashboard. On 403, do not retry with the same Bearer credential; on 400 or 422, correct the profile payload only after surfacing the validation message.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
email
string<email>

New login email. Browser-session only; Bearer API keys receive 403.

password
string

New login password. Browser-session only; Bearer API keys receive 403.

Minimum string length: 8
firstName
string | null

Profile first name. Supported with browser sessions or Bearer API keys.

lastName
string | null

Profile last name. Supported with browser sessions or Bearer API keys.

Response

Successful response.