Get the authenticated user's profile.
Retrieve the authenticated user’s profile attributes available for self-service management, with a per-field access policy indicating read/write eligibility.
承認
Bearer and DPoP tokens are supported depending on the API configuration
ヘッダー
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.
レスポンス
Successfully retrieved profile.
The authenticated user's profile attributes available for self-service management, 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.
Email address of this user.
Phone number for this user. Follows the E.164 recommendation.
Username of this user.
Data related to the user that does not affect the application's core functionality. Only the subset of keys accessible for self-service management is returned.
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).