Looking for:
- Xero api rate limits |
- Handling Xero's rate limits · Issue #5 · minimul/xero-api · GitHub
Do you recognize a good idea when you see one? We want to hear from you! View our full list of features requested for our API and make your vote count. Started by Chris Hearn - in Getting Started. Mike Edwards. Chris Hearn. Xero Developer Community. We are in the process of making improvements to the rate limiting support for our Xero integration and wondered if there is anyway of getting the Xero API to simulate returning the various rate limit exceeded headers without blasting the API with calls artificially to trigger them?
It would make development and testing of our backoff strategy much simpler if this was possible. It would be great to hear of any alternatives people have come up with for testing this efficiently in the event the above is not currently possible.
Thanks in advance. I wondered the same thing during my recent attempts to do the same thing, and Xero told me that there is no way to simulate it. I was trying to make it throw the response so I could test how to extract the "Retry-after" value if I exceed the daily connection limit.
In the end I just made calls one after another, which will cause a albeit for a different rate limit and give me enough information in the headers to extract that value. My code then sleeps for that number of seconds before continuing. In reality I doubt that it will hit that limit in my case. I also keep track of the various "limit-remaining" values that are returned in the headers of a successful call so I could reduce the chances of hitting a limit, but that only tells me it's OK to try, it doesn't tell me how long to wait if I do hit one.
Show all 2 replies. Thanks for your detailed reply Mike, it's much appreciated. Hopefully this is something they will address in future to improve developer experience, reduce unnecessary load on their API infrastructure and improve the chance of applications respecting the imposed limits.
No comments:
Post a Comment