Update the authenticated user's profile.
Update the authenticated user’s writable profile attributes.
Authorizations
Bearer and DPoP tokens are supported depending on the API configuration
Headers
A client-provided unique identifier for a single operation, used to correlate the request across Auth0 systems. The value is surfaced under references.correlation_id in tenant logs and echoed back on the response's x-correlation-id header. Invalid or oversized values are silently dropped and replaced by a generated UUID v4. Avoid including personally identifiable information (PII).
A W3C Trace Context header used to correlate the request across distributed traces. When supplied, the inbound trace is continued and a fresh child span is echoed back on the response's traceparent header; the trace ID is also surfaced under references.trace_id in tenant logs. Malformed values are ignored.
Body
Response
Profile updated successfully.
The authenticated user's updated profile attributes, with a per-field access policy indicating read/write eligibility.
Given name/first name/forename of this user.
Family name/last name/surname of this user.
Name of this user.
Preferred nickname or alias of this user.
URL to picture, photo, or avatar of this user.
Read-only. To manage email, use /me/v1/identifiers.
Read-only. To manage phone number, use /me/v1/identifiers.
Read-only. To manage username, use /me/v1/identifiers.
Read-only in this version. user_metadata write support is available in a future release.
Date and time when this user was created.
Date and time when this user was last updated/modified.
Per-field write-eligibility keyed by RFC 6901 JSON Pointer (e.g. /email).