Create an empty chat and return itsDocumentation Index
Fetch the complete documentation index at: https://docs.trellis.sh/llms.txt
Use this file to discover all available pages before exploring further.
id. Every other chat surface — Send Message, WebSocket, and Upload Files — now requires an existing chat_id. Call this endpoint first.
This replaces the previous behavior where omitting
chat_id from POST /v1/chats or POST /v1/chats/uploads would lazily create one. Those surfaces now reject the request with a 400 MISSING_CHAT_ID error.Bearer token obtained from the authenticate endpoint.
Custom title for the chat. If omitted, a timestamp-based title is generated.
ID of the database integration this chat will query. When supplied, it is validated against the caller’s organization and stored on the chat’s metadata so subsequent messages don’t need to resend it.
Response
The newly created chat’s ID. Pass this as
chat_id on subsequent calls.Organization the chat belongs to.
Member the chat belongs to.
The chat’s title.
ISO 8601 timestamp when the chat was created.
Rate limits and caps
| Limit | Value | Response on breach |
|---|---|---|
| Creation rate | 20 requests per minute per JWT | 429 with Retry-After header |
| Open chats per member | 500 | 409 OPEN_CHAT_CAP |