API reference
Session
Contract and client context
Operation: session · HTTP: GET /v1/auth/session
Use an operator-supplied registry base URL. Request execution is disabled in this documentation explorer. Generated request snippets are templates, not signed or authorized submissions.
Exact operation definition
{
"operationId": "session",
"responses": {
"200": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/SiwsSessionResponse"
}
}
},
"description": "Current SIWS identity"
},
"401": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/ErrorResponse"
}
}
},
"description": "Session missing, expired, or unknown"
}
},
"security": [
{
"siwsSession": []
},
{
"siwsCookie": []
}
],
"tags": [
"auth"
]
}Resolve schema references against the complete OpenAPI document. Standalone schemas and hashes are generated from the same checked-in source.
GET
/v1/auth/sessionAuthorizationBearer <token>
Opaque capability-bearing MARS session issued by an enabled authentication profile.
In: header
Response Body
application/json
application/json
curl -X GET "https://example.com/v1/auth/session"{ "expiresAtMs": 0, "hmrDid": "string", "rootDid": "string", "rootKind": "string"}