Skip to main content
GET
Inspect a subject
Fetch one provisioned subject; 404 subject_not_found otherwise.

Authorization

This route requires the read scope. A missing or invalid credential returns 401 authentication_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

Beyond the shared statuses, this route can answer with subject_not_found. Every problem body names its own code, and the type URI always resolves to the matching page. 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.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Path Parameters

subject_id
string
required

Developer-supplied subject id: 1-128 chars of [A-Za-z0-9._:-].

Response

Successful Response

Public wire shape of a subject: {id, createdAt}.

id is the developer-supplied subject key (the selector value). The internal user id is deliberately NOT exposed: it is an isolation detail.

createdAt
string<date-time>
required
id
string
required