Revoke Session
Request and response reference for POST /api/auth/logout.
/api/auth/logoutRequest
This interface uses an approved institutional session, not a financial API key. Session writes also need Origin and CSRF protection. Use the JavaScript sample within an authorized browser integration.
curl -X POST "$OSAI_CONSOLE_BASE_URL/api/auth/logout" \
-H "Content-Type: application/json" \
-H "Origin: $OSAI_APP_ORIGIN" \
-H "X-CSRF-Token: $OSAI_CSRF_TOKEN" \
--cookie "$OSAI_SESSION_COOKIE_FILE" \
--data '{}'Parameters
| Name | Location | Requirement | Description |
|---|---|---|---|
Origin | header · string | Required | Use the value defined for this resource. |
X-CSRF-Token | header · string | Required | Use the value defined for this resource. |
Request body
This operation does not define a JSON request body.
Responses
Inspect HTTP status before parsing a body. These tables describe client response fields rather than invented successful transaction payloads.
204 · Revoked or already invalid session; cookies cleared
No client body fields are defined for this response.
400 · Invalid bounded instruction
No client body fields are defined for this response.
401 · Authentication required
No client body fields are defined for this response.
403 · Permission, recent verified MFA or CSRF denied
No client body fields are defined for this response.
409 · Version, preview, instruction or capacity conflict
No client body fields are defined for this response.
503 · Unavailable or unknown commit outcome; query the original command before retrying
No client body fields are defined for this response.
Retries & recovery
Keep the original request identifiers and any required idempotency key. A timeout does not establish failure. Read the original resource or command before another financial write; use expected versions for concurrent changes.