Get current user's profile
GET
/v1/users/me/profile
const url = 'https://example.com/v1/users/me/profile';const options = { method: 'GET', headers: { 'X-Tenant-ID': '2489E9AD-2EE2-8E00-8EC9-32D5F69181C0', Authorization: 'Bearer <token>' }};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/v1/users/me/profile \ --header 'Authorization: Bearer <token>' \ --header 'X-Tenant-ID: 2489E9AD-2EE2-8E00-8EC9-32D5F69181C0'Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters ” X-Tenant-ID
required
string format: uuid
Tenant identifier. Must match the tenant associated with the credential. Returns 403 tenant_mismatch if the credential and header belong to different tenants.
Responses
Section titled “ Responses ”OK
Media type application/json
object
id
required
string format: uuid
email
required
string
name
required
string
auth_provider
required
When oidc/saml, first_name/last_name/email are managed by IdP and read-only
string
first_name
string
last_name
string
display_name
string
avatar_base64
Base64-encoded image data with data URI prefix (max ~256KB)
string
Example
{ "auth_provider": "local"}Unauthenticated
Media type application/json
object
code
required
Machine-readable error code (e.g. “not_found”, “tenant_mismatch”).
string
message
required
Human-readable description of the error.
string
details
Optional additional context about the error.
object
key
additional properties
any
notices
Policy notices from determining Cedar rules, if applicable.
Array<string>
Example generated
{ "code": "example", "message": "example", "details": {}, "notices": [ "example" ]}