Get authenticated caller
Returns information about the caller authenticated through one of the supported API auth mechanisms. API key callers receive API client metadata. Human callers receive their JWT payload from either the Endaoment browser session cookie or an OIDC bearer token. Browser sessions may receive a refreshed Set-Cookie header when referral-source metadata is updated.
Authorizations
Headers
API key used by server-side integrations. Bearer auth or the NdaoAuth cookie may also be used.
Response
Authenticated caller metadata
- Option 1
- Option 2
- Option 3
Human-readable name of the API key client.
"Authorization Server"
Roles granted to the API key client.
["keeper"]OIDC client ID associated with the API key, when the key is tied to a tech platform.
"partner-oidc-client"