Conversations
/v1/conversations· Cross-device conversation sync (used by the chat site)
A lightweight conversation cloud sync API: stores conversation titles, message arrays, and arbitrary client metadata. It is not a model endpoint and incurs no generation charges; conversation content is visible only to the owning user.
Object#
{
"id": "0f3c2f3a-8a0e-4c1e-9f0a-2b7c9d1e4a11",
"user_id": 24,
"title": "关于向量数据库",
"messages": [
{
"role": "user",
"content": "什么是向量数据库?",
"timestamp": "2026-11-19T02:00:00Z",
"id": "msg_local_1",
"reasoning": "",
"sources": []
}
],
"metadata": {"model": "nexith-core"},
"created_at": "2026-11-19T02:00:00Z",
"updated_at": "2026-11-19T02:05:00Z"
}Client-supplied extra fields on messages[].extra (message id, reasoning, citations, artifacts, …)
are stored and returned verbatim; the server does not parse them.
GET /v1/conversations#
Lists the current user's conversations in descending updated_at order, up to 100.
{"data": [ /* Conversation */ ], "total": 1}POST /v1/conversations#
{
"title": "新会话",
"messages": [],
"metadata": {"model": "nexith-core"}
}Returns the complete object after creation.
GET /v1/conversations/:id#
Returns a single conversation; returns 404 not_found if it does not belong to the current user.
PATCH /v1/conversations/:id#
Updatable fields (all optional): title, messages, metadata.
{"title": "改名后的标题"}DELETE /v1/conversations/:id#
Returns 204 No Content on success; returns 404 if it does not exist.
Authentication and errors#
- Requires authentication (JWT or
nx-key); isolated byuser_id. - See Errors and rate limiting for the unified error format.