Skip to content
AiKYNETIX

Thread history

GET
/api/support/threads/{id}/messages/
curl --request GET \
  --url http://localhost:8000/api/support/threads/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/messages/ \
  --header 'Authorization: Bearer <token>'

GET returns the persisted conversation, oldest first.

POST sends one user turn ({content}) and streams the assistant answer as text/event-stream with the same frame contract as /api/support/ask/ (meta → token* → citations → done); both turns are persisted server-side, so history is never re-sent by the client. An invalid body yields a single event: error frame with HTTP 400. POST shares the paid-LLM rate limit with /ask/; exceeding it returns 429.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
id
required
string format: uuid

Responses

Section titled “Responses”

200

Section titled “200”
Media typeapplication/json
Array<object>
object
id
required
string format: uuid
role
required
string
<= 12 characters
content
required
string
citations
escalate
boolean
mode
string
<= 8 characters
tools
visuals
created_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
Examplegenerated
[
  {
    "role": "example",
    "content": "example",
    "citations": "example",
    "escalate": true,
    "mode": "example",
    "tools": "example",
    "visuals": "example"
  }
]

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"
}