Get Me
Account and platform
Get Me
Introspect the calling principal: org, user, scopes, subject default, plan.
GET
Get Me
subjectDefault is always the key owner’s user id (the identity a
request acts as when no subject selector is sent). It is deliberately not
the resolved X-Exo-Subject selector: internal subject user ids are an
isolation detail and never leave the API.
Authorization
This route accepts any authenticated Exo API key and checks no additional scope. A missing or invalid credential returns 401authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.
Headers
These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.Success responses
Errors
Every error is an RFC 9457
application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.
Notes
- This works before any data exists. It is the call to make first when you are checking a key.
subjectDefaultis always the key owner. It is never the resolvedX-Exo-Subjectselector: internal subject user ids are an isolation detail and do not leave the API.
Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Response
Successful Response