Skip to content
AiKYNETIX

List my Kai threads

GET
/api/support/threads/
curl --request GET \
  --url http://localhost:8000/api/support/threads/ \
  --header 'Authorization: Bearer <token>'

Named, server-persisted Kai conversations, personal to the calling coach (never visible to teammates). A thread can be scoped to a subject — a session, one metric of a session, a video moment — and creating with the same subject_ref again RESUMES the existing thread (created: false) instead of duplicating it.

attachment_refs are typed references only: the server verifies the subject belongs to your team and builds an immutable data snapshot from the database — request bodies have no field for raw context content by design.

Feature-flagged: while support threads are disabled on the environment every route responds 404.

Authorizations

Section titled “Authorizations”

Responses

Section titled “Responses”

200

Section titled “200”
Media typeapplication/json
Array<object>
object
id
required
string format: uuid
title
required
string
<= 120 characters
kind
  • product - Platform help
  • performance - Performance
string
Allowed values: product performance
subject_kind
string
<= 32 characters
subject_id
string format: uuid
nullable
subject_params
required

The identity-bearing params, view-only ones stripped.

A thread’s subject is not always its subject_id: a dashboard is keyed by its activity and a page thread by its route, and neither has an id. Without this the client cannot tell two id-less threads apart — every page thread was {subject_kind: "page", subject_id: null} on the wire, so the drawer could not re-open the right one when the coach came back to a tab (#945).

Stripped server-side (threads.identity_params) so the rule for what counts as identity lives in ONE place: a client comparing raw params would fork on units and never match.

object
key
additional properties
created_at
required
string format: date-time
updated_at
required
string format: date-time
attachments
required
Array<object>

Context chip on a thread — label + kind. The snapshot content stays server-side (it is prompt material, not display material); user file attachments additionally expose a short-lived download URL + media type so the FE can render an image thumb.

object
id
required
string format: uuid
kind
required
string
<= 32 characters
label
required
string
<= 120 characters
subject_id
string format: uuid
nullable
captured_at
string format: date-time
url
required
string
nullable
media_type
required
string
nullable
Example
[
  {
    "kind": "product"
  }
]

401

Section titled “401”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}

404

Section titled “404”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}

429

Section titled “429”
Media typeapplication/json
object
detail
required

429 — rate limit exceeded. Honour the Retry-After response header (seconds to wait) before retrying; it is sent on every 429.

string
Examplegenerated
{
  "detail": "example"
}