Who the bearer token belongs to. [`Caller`] does the work: it demands a real session (not open in public-dashboard mode, since an anonymous visitor has no identity to report).
GET
/api/v1/auth/me
const url = 'https://example.com/api/v1/auth/me';const options = {method: 'GET', headers: {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/api/v1/auth/me \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The bearer holder’s role and username
Media typeapplication/json
The caller’s own identity.
object
Example
{ "role": "viewer", "scope": "All"}No valid bearer token — closed even on a public dashboard
Media typeapplication/json
The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI
document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies
undescribed — a client that has to guess the failure shape ends up parsing the success shape and
reading undefined.
object
error
required
object
code
required
Stable machine-readable code. Clients branch on this, never on the message.
string
message
required
Operator-facing sentence. Safe to display; never carries an internal error’s own text.
string
Examplegenerated
{ "error": { "code": "example", "message": "example" }}