Close Secure Session

POST/web/v1/system/secure-channel/session/close None

Required Gateway Headers

All API requests require gateway headers. See Required Headers for the complete list. In local/test environments, you must also include Cloudflare simulation headers (CF-Connecting-IP, Cf-Ray, cf-ipcountry).

Invalidates an existing secure channel session, immediately revoking access to the associated encryption keys. After closure, any requests using this session ID will be rejected.

Required Headers

Header	Example Value	Description
Content-Type	application/json	Request content type
Accept	application/json	Expected response type
X-Client-Hash		Client device fingerprint
Accept-Language	en, zh, zh-Hant, ja, vi	Response language (default: en)

Request Parameters

Name	Type	Required	In	Description
X-SC-Session-Id	string	Required	header	Session ID to invalidate

Success Response

200 OK 200

{
  "version": "2.0.0",
  "timestamp": 1709337600000,
  "success": true,
  "code": "2000",
  "message": "SUCCESS",
  "data": null
}

Error Responses

Bad Request 400

{
  "success": false,
  "code": "4000",
  "message": "Session ID header is required"
}

Notes

• Closing a session is idempotent; closing an already-closed or expired session does not produce an error.
• Sessions also expire automatically based on their configured TTL.
• Clients should close sessions explicitly when they are no longer needed to minimize the window of key exposure.