Model

Update a conversation

Replace a conversation's metadata.

Call Create conversation first, then replace conv_123 with the returned conv_ ID.

POST /model/v1/conversations/{conversation_id}● Supported

Official docs ↗

Request parameters

  • conversation_idstring必填

    path: Id of the conversation, the `id` of the object returned by createConversation (it looks like conv_...). Another tenant's conversation, an unknown id and a deleted conversation all answer 404 conversation_not_found.

  • metadataobject必填

    Replacement metadata. The whole object replaces the old one; it is not merged. Up to 16 pairs, keys at most 64 characters and values at most 512. Router support (supported): Verified to take effect.

    Verified to take effect.

Returns

200 conversation

Replaces a conversation's metadata wholesale — it does not merge with existing metadata.

Platform errors (auth, rate limits, validation) and OCR errors use problem+json; other model call errors follow the endpoint's own format (OpenAI or Anthropic) — see error codes

Response

HTTP 200

The updated conversation

application/json

NameTypeDescription
idstringId of the conversation, such as `conv_...`; use it as `conversation_id` in conversation calls and as `conversation` in createResponse.
objectstringObject type; always `conversation`.
created_atintegerUnix time in seconds at which the conversation was created.
metadataobjectUp to 16 string key/value pairs; keys at most 64 characters and values at most 512.