You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature Description
I would like to request a feature that controls API requests by considering the rate limits imposed by the API provider. Specifically, I am looking for functionality similar to what is described in the Zenpy library documentation:
Currently, the existing throttle functionality in src/clients/throttle.js does not take the API's rate limits into account. It would be beneficial if the throttle mechanism could be enhanced to handle rate limiting as per the official API documentation:
Implementing this feature would allow the client to automatically adjust API request rates based on the rate limit headers provided by the API, preventing potential request throttling or denial due to exceeding rate limits. This would improve the robustness and reliability of applications using this client.
The text was updated successfully, but these errors were encountered:
Feature Description
I would like to request a feature that controls API requests by considering the rate limits imposed by the API provider. Specifically, I am looking for functionality similar to what is described in the Zenpy library documentation:
Zenpy Rate Limiting
Currently, the existing throttle functionality in src/clients/throttle.js does not take the API's rate limits into account. It would be beneficial if the throttle mechanism could be enhanced to handle rate limiting as per the official API documentation:
Zendesk API Rate Limits
Example Use Case
Implementing this feature would allow the client to automatically adjust API request rates based on the rate limit headers provided by the API, preventing potential request throttling or denial due to exceeding rate limits. This would improve the robustness and reliability of applications using this client.
The text was updated successfully, but these errors were encountered: