Conversation Variables are not working through API call (v1/chat-messages)

[QBitMindset]

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).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

I've developed a simple chat flow that uses Conversation Variables, everything works fine with web app chat bot, but when I using Postman Conversation Variables will not fill with user's data!
I don't know its a bug or I'm missing something!

Thanks

[dosubot[bot]]

Based on the codebase, Conversation Variables are tightly linked to the app configuration and require correct setup and usage in API calls. When using the API (like v1/chat-messages), make sure you are passing all required variables in the request payload, matching the structure defined in your app's user_input_form. The API expects these variables to be present and properly named; otherwise, they won't be filled or processed as they are in the web app. Also, ensure you are including a valid conversation_id and using the correct app mode (CHAT, AGENT_CHAT, or ADVANCED_CHAT) for Conversation Variables to work as expected [source 1].

If you are already doing this and still see issues, double-check that your Postman request body matches the expected schema and that all required headers (like authentication tokens) are present. If possible, compare the network request from the web app (using browser dev tools) to your Postman request to spot any differences.

There are no known issues or documentation gaps found about Conversation Variables not working via API, so if the above checks don't resolve it, sharing your exact API request (minus sensitive info) could help pinpoint the problem.

To reply, just mention @dosu.

---

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

[QBitMindset]

Missin "conversation_id" cause the problem