Skip to main content
PATCH
Update chat
Retired: the Chat and Message API was retired on 21 August 2026, and these endpoints no longer exist. Use Direct Responses if your app owns safety, or the guarded Responses API for built-in guardrails and tradition; if you need model_family, auto-routing or grounded completions, use Completions V2. The Chat migration guide walks through the move.

Authorizations

Authorization
string
header
default:Bearer <api-key>
required

Bearer authentication header of the form Bearer <api-key>, where <api-key> is your API key.

Path Parameters

v
enum<string>
required
Available options:
v1

Query Parameters

chat_id
string
required
chat_field
enum<string>
required

Select a field

Available options:
pin,
title,
summary
Maximum string length: 7

Body

application/json
new_value
any
default:""

The new value for the field.

Response

Successful response