API returning status code 406

Answered

Comments

11 comments

  • Avatar
    Jake Holman

    Christian, XML or JSON?

  • Avatar
    Christian Holm

    JSON

  • Avatar
    Christian Holm

    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.

  • Avatar
    Chris Burns

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

  • Avatar
    Chris Burns

    FYI, I'm also using JSON.

  • Avatar
    Jake Holman

    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!

  • Avatar
    Jari Turkia

    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?

  • Avatar
    Jari Turkia

    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.

  • Avatar
    Jake Holman

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

  • Avatar
    Jari Turkia

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

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

  • Avatar
    Steven Yan

    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.

Powered by Zendesk