Confirmed that yes_no does not appear to be an actual question type. Sent a PUT request through the API to change the questions labeled as “multiple choice” to “yes_no” type. Request was successful, but all types remained “multiple choice”

This appears to be an issue with yes/no questions. According to the documentation, you should be able to send a response of “yes” or “no” for yes/no type questions. However this is not the case. You must send the “choice” ID as the response for it to be accepted, which is supposed to apply on to “multiple choice” type questions. I’m inclined to believe this is because there isn’t an actual yes/no type question for surveys. You can choose yes/no as a type when creating a new survey question through the interface, but it shows up as “multiple choice” (with “yes” and “no” as options).

Hopefully the NB team see this. Please update the documentation or, preferably, update yes/no type questions to accept “yes” or “no” as responses. It’s painful to have to store the unique id of each “yes” or “no” to send over with each response.

Just got this, too.

Based on the error message I would assume I had the wrong survey ID, but I know that’s not the case because I queried the survey and its questions with the API. Anyone have an idea of what’s really going on here?

Documentation really sucks on here. I am getting the same error but it is for events. This is not very descriptive. What code is it referring to? I passed it the generated token but this is not what it apparently needs. I too am running this in PHP.

Matt, I was able to solve this. Can you elaborate on your code and maybe I can help while we are waiting? I am running in PHP.

I’m having this problem as well.