Synchronize a Conversation page
Operation boundary
- Caller: Trusted backend only
- Scope: limit bounds membership rows scanned, not the number of returned conversations; tombstones go to deletes. Previews use Leader-persisted data without runtime activation. Any read failure fails the whole page; retry the original request and cursor.
- Success: Only done=true completes a full pass and permits saving coverage; reset_required=true requires rebuilding the local Conversation directory.
- Recovery: Previews include the latest tail edit; preserve the cursor on 503 unavailable. Content edits do not change conversation order or unread.
/conversation/listReads Leader-persisted messages without runtime activation. Failed SENDs may appear. Any read error fails the page; retry the original cursor.
Request Body
application/json
Conversation-directory pagination and deletion-coverage inputs.
TypeScript Definitions
Use the request body type in TypeScript.
Conversation-directory pagination parameters.
Response Body
application/json
application/json
application/json
application/json
{ "conversations": [ { "channel_id": "string", "channel_type": 1, "active_at": 0, "read_seq": 0, "deleted_to_seq": 0, "unread": 0, "last_message": { "message_id": 0, "message_idstr": "string", "message_seq": 0, "from_uid": "string", "client_msg_no": "string", "server_timestamp_ms": 0, "payload": "string", "version": "string", "updated_at_ms": 0 } } ], "deletes": [ { "channel_id": "string", "channel_type": 1 } ], "next_cursor": "string", "done": true, "coverage": 0, "tombstones_retained_since": 0, "reset_required": true}