Move thread scope

patch https://api.intelig.ai/api/v1/intelig/cognis/threads/{threadId}/scope

Auth: Authorization: ApiKey <key> (an API key sent as Bearer is rejected) or Authorization: Bearer <jwt> for a dashboard session. operationId: moveThread

Moves an existing Cognis thread to a different visibility scope (e.g., from personal to organization).

Example request

curl -X PATCH "https://api.intelig.ai/api/v1/intelig/cognis/threads/1/scope" \
  -H "Authorization: ApiKey $INTELIG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "scopeType": "TEAM",
    "scopeId": 15,
    "scopeName": "intelig-frontend"
  }'

Path parameters

Name	Type	Required	Description
`threadId`	integer (int64)	yes	—

Request body

application/json

Field	Type	Required	Description
`scopeType`	string	yes	New scope type One of: CONTRIBUTOR, TEAM, ORGANIZATION, PERSONAL Example: TEAM
`scopeId`	integer (int64)	no	Identifier of the new scoped entity Example: 15
`scopeName`	string	no	Display name of the new scoped entity Example: intelig-frontend

Response 200

application/json · CognisThreadDto

Field	Type	Description
`id`	string	Unique thread identifier
`scope`	CognisScopeDto	Scope context for a Cognis thread
`title`	string	Thread title
`createdAt`	string (date-time)	Timestamp when thread was created
`updatedAt`	string (date-time)	Timestamp when thread was last updated
`messageCount`	integer (int32)	Total number of messages in the thread
`lastMessage`	string	Preview of the last message content
`messages`	CognisMessageDto[]	All messages in the thread

Status codes

200 — Thread moved successfully
400 — Invalid scope type or request body
401 — Not authenticated
403 — Insufficient permissions for Cognis pillar
404 — Thread not found
429 — —

Every response is wrapped in { success, message, data }. A 4xx means the request is wrong — do not retry it unchanged. A 429 carries Retry-After in seconds.