CODEWITHSUNDEEP
ibm-watsonwatson-dialog
Alex P
Alex P

Reputation: 530

Watson Dialog does not recognize continuation of conversation

When trying to use the Dialog tool to get a feel for how the APIs work, I ran into a problem where a POST to /conversation creates a new conversation, instead of continuing an existing one. I am using the docs found at : http://www.ibm.com/smarterplanet/us/en/ibmwatson/developercloud/dialog/api/v1/

An initial POST returns a conversation and client id, but subsequent requests with those values added, along with an input value, just return information for a new conversation. Are these docs inaccurate?

Here is a screenshot from one of my many attempts at getting this to work. The client and connection IDs are from a previous POST to /conversation

https://i.sstatic.net/n6osi.jpg

Thanks for your help!

Upvotes: 1

Views: 238

Answers (2)

Alex P
Alex P

Reputation: 530

It turns out I was using the incorrect encoding for the conversation / client ID's and input. Watson expects the form values to be URL encoded. Once I made that change, the problem was resolved.

Thanks to everyone who offered their time and help!

Upvotes: 1

Simon O'Doherty
Simon O'Doherty

Reputation: 9359

Your first call to Converse you should not specify the conversation ID. Dialog will return a conversation ID with the first response.

You then use that ID going forward to maintain the conversation. It is unclear if you are doing this in the example above.

Upvotes: 2

Related Questions