2

API returning status code 406

Recently we have seen an increased number of status code 406 returned from the testcases on our Zendesk integration. The error occurs on roughly 10% of the API calls. Since we have not changed any code, this seems to be caused by a change on the Zendesk end. In plain HTTP 406 is used to signal that a valid response could not be generated based on the "Accept" header. The header is set to "application/json", but the 406 still occurs.

How can we figure out what is causing the 406 errors?

11 comments

  • 0

    Christian, XML or JSON?

  • 0

    JSON

  • 0

    Any news on how we can move forward on this? We are still seeing intermittent failures with status 406, even though the calls are the exact same all the time.

  • 0

    I am also getting this error on a script I use for external stat reporting.  This worked perfectly last month, what has changed?

  • 0

    FYI, I'm also using JSON.

  • 0

    It's extremeley hard to debug these issues without knowing what you're passing to Zendesk.

    Please log what you're giving to Zendesk, and post it in https://gist.github.com/

    Thanks!

  • 0

    Here is mine: https://gist.github.com/1066909

    I'm using the same code than two days ago. At that time I could populate our old wiki-articles into Zendesk. Now that I try to do the exact same thing, I'll get an HTTP/406. What's going on?

  • 0

    Zendesk does not accept UTF-8 characters anymore.

    I got mine working by converting the single character ... into three dots. This did work earlier, I don't know what they changed, but they just forgot to test with UTF-8.

  • 0

    @Jari: Going by the Gist example you posted, the XML is actually mal-formed. There is no closing body or entry tag. 

  • 0

    In the line 396 which of these won't do it?

    <!-- SECTION "Glossary" [9024-] -->]]></body></entry>

  • 0

    Hi Jari and Christian, I'm not sure if this ever got completely answered, but I wanted to let you know that we have new developer documentation as well as a new API:

    http://developer.zendesk.com

Please sign in to leave a comment.