Header of the rate limit is not valid in the rest API | Community
Skip to main content

Header of the rate limit is not valid in the rest API

  • September 2, 2024
  • 1 reply
  • 0 views
A

 

Hi,
We are using the rest of the API of Zendesk.

If the rate limit surpasses, we get the invalid headers for the rate limits that are invalid as per Mozilla standards.
For example,
we are getting 429 status codes with the following headers.

 retryAfter: 29 

rateLimitReset: 29 

rateLimitRemaining: 277

In the above example, it suggests hitting the API after 29, however, it shows a rate limit remaining with 277 which is conflicting.



Thank you.

    1 reply

    A
    • Automation
    • Author
    • September 2, 2024
    • Is the above-mentioned behavior expected or not? 
      • If expected then should we consider "retryAfter" header only while handling the rate limit? 
        • If so then what is the significance of the “rateLimitRemaining” header?
    • If is not the expected behavior then Will it be corrected in the future? If so then in which release?
    Terms & ConditionsCookie settingsAccessibility statement