Stop a chat's turn
/api/v1/chats/{chat_id}/stopStop the turn the chat is working on, as the app's Stop does. Messages still waiting stay, and the next one starts the chat's next turn.
run_ids lists the runs cancelled. It is empty when nothing was working: a turn that ended just before the request is not an error.
Required access
Credentials: delegated token, user session, user API key
User API keys use the owner’s current permissions, subject to any key restrictions. Capability scopes below apply to automation account keys and delegated tokens.
Scope: chats:edit, runs:edit
Only the member who started the chat, through their user API key or an integration acting for them: a chat is private to them. Another member's chat answers 404, also to a workspace owner or admin, who may only stop its turn or delete it, signed in to the app, and reads none of it. Automation accounts have no chats. Stopping cancels the turn's run, so it needs what cancelling that run needs.
A user-owned key prefixed gsmc_uk_, bound to one organization. It follows its owner's current membership, role and resource permissions, optionally restricted to read-only access. No X-Org-Id header is needed; a conflicting organization is rejected. Credential creation, personal connection setup and human attestations require a signed-in session. Runs are private to the calling user; sharing an agent grants access to your own personal memory of it, never to the agent's own memory.
In: header
Path Parameters
uuidHeader Parameters
Selects the active organization for a direct user session that has more than one membership. Automation account keys and delegated tokens are each bound to one organization and ignore it.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/v1/chats/497f6eca-6276-4993-bfeb-53cbbbba6f08/stop" \ -H "Authorization: Bearer $GUEST_MACHINES_API_KEY"{ "run_ids": [ 0 ]}