Forums/Community/Zendesk API

Answered

API returning status code 406

Christian Holm
asked this on June 01, 2011 01:11

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?

 

Comments

User photo
Jake Holman
Product Manager

Christian, XML or JSON?

June 01, 2011 08:32
User photo
Christian Holm
podio

JSON

June 03, 2011 01:01
User photo
Christian Holm
podio

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.

June 06, 2011 05:06
User photo
Chris Burns
pureapps

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

July 01, 2011 07:35
User photo
Chris Burns
pureapps

FYI, I'm also using JSON.

July 01, 2011 07:35
User photo
Jake Holman
Product Manager

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!

July 01, 2011 10:44
User photo
Jari Turkia
netvisor

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?

July 06, 2011 02:34
User photo
Jari Turkia
netvisor

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.

July 06, 2011 06:42
User photo
Jake Holman
Product Manager

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

July 06, 2011 09:23
User photo
Jari Turkia
netvisor

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

<!-- SECTION "Glossary" [9024-] -->]]></body></entry>
July 06, 2011 23:02
User photo
Steven Yan
Product Manager
Check Answer

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

April 26, 2012 13:58