Me
Get the current caller's account
Identity, active organization + membership role, and how the caller authenticated.
Extended profile fields (nmlsId, jobRole, the contact-card block) are resolved for every caller type — session-cookie, API-key, and OAuth-bearer alike. auth.profileResolved is true on any successful read; it is retained for compatibility and no longer varies by the credential the caller presented.
Authorization
Responses
200objectThe caller's accountShow attributesHide attributes
authobjectrequiredShow child attributesHide child attributes
clientIdstring | nullOAuth client that minted the token, when applicable
methodenumrequiredWhich credential the API resolved this caller from
api-keybearersessioninternalprofileResolvedbooleanrequiredAlways true on a successful read; retained for compatibility now that every caller type resolves the full profile
rolestringrequiredGlobal user role
scopesstring[] | nullOAuth scopes on the bearer token; null for API-key / session callers
organizationobject | nullrequiredShow child attributesHide child attributes
idstringrequiredrolestring | nullThe caller's MEMBERSHIP role in this org (owner/admin/member)
userobjectrequiredShow child attributesHide child attributes
addressLine1string | nullagentPhotoUrlstring | nullcitystring | nullcontactCardTypestring | nullcontactPhonestring | nullcreatedAtstring | nullemailstring | nullemailVerifiedboolean | nullheadlinestring | nullidstringrequiredAuth user id
imagestring | nulljobRolestring | nullnamestring | nullnmlsIdstring | nullpostalCodestring | nullqrBaseUrlstring | nullreLicenseNumberstring | nullreLicenseStatestring | nullsendNewLoginEmailboolean | nullsignatureImagestring | nullstatestring | nulltaglinestring | nullthemestring | null400objectValidation error401objectUnauthorized403objectForbidden (authenticated, but missing required context — e.g. no active organization)404objectNot found413objectResponse payload too large — detail endpoint capped to fit Lambda response limits502objectAccount service unavailable503objectSearch timed out or the cluster is overloaded — retry after `Retry-After` seconds.