Conversations
A conversation is identified by its convid. The /api/user/ group lists, reads, renames, pins and deletes the caller's conversations.
Reading a conversation
POST /api/user/getConversation with a convid returns the turns so far. Each turn has the query, the response (the agent's name and its output parts), the resultCode, success or ask, and respondedAt in epoch milliseconds. The agent server decrypts the state for this call; the cloud holds only the ciphertext.
Listing conversations
getPinnedConversations returns the caller's pinned conversations in one call. getUnpinnedConversations returns the recent ones, most recently used first, in pages: send limit (1 to 25) and pass the nextCursor from one response into the next request until the cursor is null. Each entry carries the convid, the title and the time of the last run.
Changing a conversation
| Endpoint | Body | Effect |
|---|---|---|
/api/user/setConversationTitle | convid, title | Renames the conversation. The title is the first query until renamed. |
/api/user/setPinned | convid, pinned | Pins or unpins. A pinned conversation is kept indefinitely; an unpinned one expires 7 days after its last use. The paid service has no such limit. A user may pin at most 25 conversations. |
/api/user/deleteConversation | convid | Deletes the conversation and its stored state. This cannot be undone. |
Every call here acts on the caller's own conversations. A convid that belongs to another user, or that has expired, is reported as unknown.