Change to Zendesk rate limiting behavior

Have more questions? Submit a request

8 Comments

  • Ryan Nguyen

    Just to confirm, what is the HTTP code upon receiving the JSON response above? Is it still 429 or is it 200?

    1
  • David Huttleston

    We're changing how the HTTP 429 response is delivered during an excessive burst, but it still remains a HTTP 429. Thanks for the good question, Ryan!

    1
  • Federico Jakimowicz

    does the response body still be a json?

    0
  • Bryan Flynn

    Hi Fedej -- yes, the response is JSON. If there's more info needed, please give more details. Have a great day!

    0
  • Daniel Ertman

    @bryan I recently received a 429, and the response was the plain text "Number of allowed API requests per minute exceeded" (without the quotes) - not a JSON body at all. Any idea why that would be?

    0
  • Joseph May

    Fedej-

    Is this at all replicable? Do you have the request/response data from when this occurred? We will not have captured the JSON, only the HTTP status code.
    In what way did this affect your application?

    0
  • Daniel Ertman

    Joseph,

    Yes, we're able to reproduce it always in our Sandbox account. The response body is never JSON in our testing.

    It affects us mostly in that our client code uses Jackson - a JSON parsing library for Java - and when the response is plaintext, Jackson blows up. So, we have reworked our client code to check the response code first and the response body second.  Mostly it just significantly disagrees with the doc you guys have posted.

    Dan

     

    0
  • Joseph May

    Hi Daniel-

    Would you please submit a ticket to us with request/response details for further investigation? Thanks for any and all help getting to the bottom of this.

    0

Please sign in to leave a comment.

Powered by Zendesk