[Question]: is it possible to (re-)connect to an ongoing chat session

[gdk-wekando]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (Language Policy).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

Describe your problem

as the title states, I am able to query chat sessions from the RAGFlow API but is it possible to specifically connect to a certain session through the API?

[dosubot]

Hi @gdk-wekando! I'm Dosu and I’m helping the ragflow team.

Yes, you can (re-)connect to an ongoing chat session in RAGFlow via the API by specifying the session ID in your requests. When you use the chat completion endpoint (POST /api/v1/chats/{chat_id}/completions), include the session_id in the request body to continue the conversation in that session. If you omit the session_id, a new session is created instead. You can list existing sessions and retrieve their IDs using GET /api/v1/chats/{chat_id}/sessions, which supports filtering by session ID, name, or user ID. There isn't a dedicated "reconnect" endpoint or persistent connection—session continuity is managed by passing the session_id with each request. This approach is supported in both the HTTP API and the SDK, though there are some known bugs in session listing in certain versions, so keep that in mind if you encounter issues with session management.
API reference | Example discussion

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Magicbook1108]

Try what dosu said.