Skip to main content
PATCH
Update Thread

Authorizations

Authorization
string
header
required

Enter your MeshAPI key (rsk_...) — sent as Authorization: Bearer <key>.

Headers

X-Mesh-Version
enum<string>
default:2026-08

Dated version of the API contract to pin this request to. Omit it and the request is served under 2026-08 — the oldest supported version, so an existing integration is never moved by a release. A malformed or unsupported value is rejected with 400 invalid_api_version rather than falling back silently. The version actually served is echoed as X-Mesh-Version on every response, including errors.

Available options:
2026-08

Path Parameters

thread_id
string
required

Body

application/json

Every field optional; only what is sent is written.

messages replaces the whole list rather than appending. The client already holds the authoritative thread in memory (it is what the user is looking at), and an append endpoint would need to resolve conflicts between two tabs — a problem a last-writer-wins replace simply does not have.

title
string | null
Maximum string length: 200
surface
string | null
model
string | null
params
Params · object | null
messages
Messages · object[] | null

Response

Successful Response

id
string
required
title
string | null
required
surface
string
required
model
string | null
required
params
Params · object | null
required
messages
Messages · object[]
required
org_id
string | null
required
team_id
string | null
required
created_at
string
required
updated_at
string
required