dosubot[bot]
commented
1 month ago Hello, @edrizo! I'm here to help you with any bugs, questions, or contributions you have regarding DifY. Let's tackle this issue together!
I found a similar open issue that might be relevant to your problem: Custom API Chatbot with nodejs no history of the conversation Included. The suggested solution involves ensuring that the conversation_id is correctly managed in your API requests. Here is a brief overview of how to handle it:
- Retrieve the
conversation_idafter the initial chat request. - Use the same
conversation_idfor subsequent requests to maintain the context of the conversation.
Here is an example in JavaScript:
const axios = require('axios');
const API_URL = 'https://api.dify.ai/v1/chat-messages';
const API_KEY = 'YOUR_SECRET_KEY';
let conversationId = '';
async function sendMessage(query) {
try {
const response = await axios.post(API_URL, {
inputs: {},
query: query,
response_mode: 'streaming',
conversation_id: conversationId,
user: 'abc-123'
}, {
headers: {
'Authorization': `Bearer ${API_KEY}`,
'Content-Type': 'application/json'
}
});
// Update conversationId with the one from the response
if (response.data.conversation_id) {
conversationId = response.data.conversation_id;
}
console.log(response.data);
} catch (error) {
console.error('Error sending message:', error);
}
}
// Example usage
sendMessage('Hello, how are you?').then(() => {
sendMessage('Can you tell me more about that?');
});In this example:
- The
conversationIdis initially empty. - After the first message is sent, the
conversationIdis updated with the value from the response. - Subsequent messages use the updated
conversationIdto maintain the conversation context.
Make sure to replace YOUR_SECRET_KEY with your actual API secret key. This approach ensures that the chatbot remembers the previous conversation when handling follow-up questions [1].
Additionally, the Dify API returns specific error codes or messages when the conversation_id is missing or incorrect, such as 404, Conversation does not exists and 400, invalid_param, abnormal parameter input [2][3].
For securely managing and using API keys, it is recommended to call them through the backend rather than exposing them in plaintext within frontend code or requests. This helps prevent your application from being abused or attacked [4][5][6][7].
To continue talking to Dosu, mention @dosu.
edrizo
Then i get the conversation_id generated.
ramishi
cuongphamduc
fujita-h
eduardochaves1
braiaagency
xwineapplex
crazywoola
perzeuss
IsraelHenriquee
Self Checks
Dify version
0.8.3
Cloud or Self Hosted
Cloud
Steps to reproduce
When we click view through DiFy itself, the conversation is complete. The session is being considered in the conversation.
However, when using the API call, this does not happen.
✔️ Expected Behavior
API calls working with the conversation session being respected.
❌ Actual Behavior
All previous conversations do not appear in the session history.