/v1/auth/sessionsList the caller's sessions or all sessions
operation ID: get_v1_auth_sessions
Overview
List the caller's sessions or all sessions. The authentication API establishes identity and manages the roles, grants, sessions, and service credentials used for authorization.
When to use it
- Use it when an application needs to list the caller's sessions or all sessions.
- Use it when a client needs to sign in, inspect its identity, or an administrator needs to manage access.
Quick example
Set the base URL and replace generated identifiers or credentials with values from your installation.
cURL
curl --request GET \
--url "$ORDINATE_URL/v1/auth/sessions" \
--header "Authorization: Bearer $ORDINATE_TOKEN"Expected output · 200
Sessions
Example 200 output
{
"entries": [
{
"id": "string",
"principal_id": "00000000-0000-4000-8000-000000000001",
"created_at_ns": 0,
"last_seen_ns": 0,
"absolute_expiry_ns": 0
}
]
}The cURL request supplies the documented path and query values and asks OrdinateDB to list the caller's sessions or all sessions. The documented 200 response is sessions.
How it works
OrdinateDB resolves a session or bearer credential to a principal, then evaluates roles, capabilities, and resource scope for each protected operation.
Reference
- Required capability
- authenticated
- Authorization scope
- self, or all sessions with admin when all=true
Parameters
| Name | In | Required | Type and constraints |
|---|---|---|---|
all | query | no | boolean |
Request body
This operation has no request body.
Responses
200Sessions
application/json
entriesarrayrequiredarray
absolute_expiry_nsintegerrequiredUTC Unix timestamp in nanoseconds
format: int64created_at_nsintegerrequiredUTC Unix timestamp in nanoseconds
format: int64idstringrequiredlast_seen_nsintegerrequiredUTC Unix timestamp in nanoseconds
format: int64principal_idstringrequired- format: uuid
Example 200 output
{
"entries": [
{
"id": "string",
"principal_id": "00000000-0000-4000-8000-000000000001",
"created_at_ns": 0,
"last_seen_ns": 0,
"absolute_expiry_ns": 0
}
]
}400Sessions are only available for human principals
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 400 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}401Authentication required
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 401 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}403Admin capability required for all sessions
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 403 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}503Model database is not configured
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 503 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}Code examples
These examples are generated from the source contract. Replace the base URL, credentials, identifiers, and minimal generated values for your instance.
JavaScript
const ordinateUrl = "http://localhost:8080";
const token = "<bearer-token>";
const response = await fetch(`${ordinateUrl}/v1/auth/sessions`, {
method: "GET",
headers: {
Authorization: `Bearer ${token}`
}
});
if (!response.ok) {
throw new Error(`OrdinateDB returned ${response.status}: ${await response.text()}`);
}
const data = await response.json();
console.log(data);Related topics
- Authentication guide — Understand the prerequisite concepts and transport behavior for this operation.
- REST endpoint index — Find other operations in Authentication.