Update Session

PATCH /sessions/{session_id}

Title, activity flag and attributes. The counters are the platform’s.

Role floor

Requires member or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
session_id	path	string (uuid)	required	—

Request body — SessionPatch

Field	Type		Notes
title	string | null	optional	max length 300
is_active	boolean | null	optional	—
attributes	object | null	optional	—

Responses

Status	Description	Body
200	Successful Response	SessionView
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X PATCH https://your-deployment.example.com/sessions/{session_id} \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — SessionView

Field	Type		Notes
id	string (uuid)	required	—
agent_id	string (uuid) | null	required, nullable	—
subject_kind	user | guest | null	required, nullable	—
subject_id	string | null	required, nullable	—
external_key	string | null	required, nullable	—
title	string | null	required, nullable	—
origin	api | schedule | event | channel | delegation | retry | replay | maintenance | system | null	required, nullable	—
message_count	integer	required	—
is_active	boolean	required	—
attributes	object	required	—
last_activity_at	string (date-time)	required	—
created_at	string (date-time)	required	—