API Reference / Cognis - Threads
Rename thread
patch
https://api.intelig.ai/api/v1/intelig/cognis/threads/{threadId}/title
Auth: Authorization: ApiKey <key> (an API key sent as
Bearer is rejected) or Authorization: Bearer <jwt>
for a dashboard session. operationId: renameThread
Updates the title of an existing Cognis thread.
Example request
curl -X PATCH "https://api.intelig.ai/api/v1/intelig/cognis/threads/1/title" \
-H "Authorization: ApiKey $INTELIG_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"title": "Q1 2026 Velocity Analysis"
}' Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
threadId | integer (int64) | yes | — |
Request body
application/json
| Field | Type | Required | Description |
|---|---|---|---|
title | string | yes | New thread title Example: Q1 2026 Velocity Analysis |
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 renamed successfully400— Invalid request body401— Not authenticated403— Insufficient permissions for Cognis pillar404— Thread not found429— —
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.