Introspect the caller's identity
Echo back the verified identity resolved from the bearer token: subject, account, workspace hint, scopes, the caller's account role and its advisory permissions, any delegated actor, the token's expiry, and whether this caller has been onboarded.
Standalone extensions call this to reconstruct the caller's identity without verifying the token themselves. The identity fields come from the verified token; role and permissions come from one authorization check against the caller's account: permissions lists the account capabilities the caller holds, and role is admin or member — absent for a human the account roster does not name, and for a machine or delegated caller, which also carries no permissions. permissions is advisory: every route decides its own capability fresh. On a deployment with no billing configured, billing_view and billing_manage are omitted for every role, so a client hides its billing surface when billing_view is absent. The raw token is never returned.
is_onboarded is a database read, not a claim: a caller can hold a valid token and have no personal workspace, and a client needs to tell those apart to know whether to send them through provisioning.
Request
- Base URL: https://api.atlan.com (the document declares no server; this is the origin it was published from)
- URL: https://api.atlan.com/registry/v1/auth/whoami
- Auth: HTTP bearer
Response
The verified caller's resolved identity and onboarding state.
Changes
No recorded changes to this operation across all 1 revision of this API.