Skip to main content
DELETE
Delete a coding session
Scoped to the effective subject, so a call made for one subject can never remove another subject’s session of the same id. Idempotent: deleting a session that is already gone returns a deleted count of 0 rather than 404.

Authorization

This route requires the write 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

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

session_id
string
required

Response

The number of session nodes removed.

The response is of type Response Delete Session V1 Recall Sessions Session Id Delete · object.