Revoke one of the caller's own sessions.
Changed onKills it MID-FLIGHT: the next request re-resolves the row in its own transaction, so a revoked session stops working immediately rather than at some cache horizon.
The principal conjunct lives in the SQL, so one caller is structurally unable to reach another's session by guessing an id — and an id that is not the caller's is a 404, not a 403.
Request
- Base URL: / (relative, and the document was published on a file host, not at the API’s origin)
- URL: /api/v1/me/sessions/{session}
- Auth: HTTP bearer
Response
Revoked.
Changes
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- info
- warning
added the new
payload_too_largeenum value to the/response property for the response status - warning
added the new
payload_too_largeenum value to the/response property for the response status - warning
added the new
payload_too_largeenum value to the/response property for the response status - warning
added the new
payload_too_largeenum value to the/response property for the response status - warning
added the new
payload_too_largeenum value to the/response property for the response status - warning
added the new
unprocessableenum value to the/response property for the response status - warning
added the new
unprocessableenum value to the/response property for the response status - warning
added the new
unprocessableenum value to the/response property for the response status - warning
added the new
unprocessableenum value to the/response property for the response status - warning
added the new
unprocessableenum value to the/response property for the response status
- warning