Feature Request: Support for Retrieving Historical Conversations without from enduser id

[TAXID911101087886396267]

Self Checks

• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [x] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

We are using the Dify chat interface embedded via iframe on our website. However, we have encountered an issue when trying to retrieve historical conversation records using the "Get Historical Conversations" API. In our case, the from enduser id is empty (as the user is interacting via the embedded chat widget), which causes the API request to fail.

The current API documentation specifies that the UserId (from the from enduser id) is required when requesting historical conversation records. However, since the UserId is not available in this scenario, we are unable to retrieve the desired historical data.

Request:

We would like to request a feature enhancement to support retrieving historical conversations even when the from enduser id is not provided or is empty. It would be helpful if the API could either:

Support requests without the UserId for historical data retrieval. Offer an alternative way to fetch conversation history based on other available identifiers (e.g., session ID, conversation ID). This functionality would significantly improve the user experience for those who are embedding the chat interface in scenarios where user IDs are not directly passed.

Thank you for considering this request. We look forward to your feedback and any potential solution.

2. Additional context or comments

No response

3. Can you help us with this feature?

• [ ] I am interested in contributing to this feature.

[dosubot[bot]]

Hi, @TAXID911101087886396267. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

• Enhancement request for the Dify chat interface API.
• Suggests allowing retrieval of historical conversations without "from enduser id."
• Proposes using alternative identifiers like session ID or conversation ID.
• No comments or additional activity on the issue.

Next Steps

• Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open.
• Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

[alterxyz]

You can set a constant user_id if not using the WebAPP.

[alterxyz]

The Service API does not share conversations created by the WebApp. This is part of the design for now.