A more interesting one to solve will be the xero api rate limits Limit: 5 calls in progress at one time”. You signed out in another tab or window. Sign in to comment. Http://replace.me/21857.txt make it even more complicated, the limkts after x seconds” plan gets hairier in some cases, e.
 
 

– Xero api rate limits

 

However I don’t have any way of testing. I am assuming I need at least items in a test company to trigger this rate limit paged docs x 60 calls , which is a lot more than is in the test organisation. Is there a recommended way to test this? Do I use the API to quickly populate the test organisation? Maybe we don’t wait enough, how long should we wait before making another request once we hit the limit? While working on this rate limit problem, suddenly the access keys were invalidated and refreshing them didn’t work, so our client had to reauthorize our application.

Was this because we were pushing the rate limit? Is there some mechanism in place which invalidates keys automatically in case of such problems? Hi Lunar, thanks for your questions. It sounds like you are experiencing throttling from our API. We have two rate limits that may affect your application. The first is our minute rate limit. Xeroizer allows us to sleep for a number of seconds if the request fails in response to the OAuth::RateLimitExceeded error.

Are you open to adding something similar in? Am I correct there’s something similar in terms of retrying in your qbo-api? The text was updated successfully, but these errors were encountered:. Thanks rikkipitt for contributing this scenario. Sorry, something went wrong. Skip to content. 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.

 

– Xero Community – API rate limit

 

Connect With Us. NET Python Delphi. Chat This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media.

Skip to content. Star New issue. Jump to bottom. Projects xero-ruby Roadmap. Copy link. All reactions. You can set this option when initializing an application: Sleep for 2 seconds every time the rate limit is exceeded. SerKnight self-assigned this Oct 20, Here’s a first pass at implementing a rate limiter for the minute limit. RettBehrens unassigned SerKnight Feb 9, Sign up for free to join this conversation on GitHub.

Already have an account? Sign in to comment. All reactions. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. One of these invoices requires lots of requests to be made, which eventually causes us to hit the rate limit. Now we have a retry logic in place but for some reason waiting and retrying doesn’t work.

I have two questions: 1. Maybe we don’t wait enough, how long should we wait before making another request once we hit the limit? While working on this rate limit problem, suddenly the access keys were invalidated and refreshing them didn’t work, so our client had to reauthorize our application.

Was this because we were pushing the rate limit? Is there some mechanism in place which invalidates keys automatically in case of such problems? Hi Lunar, thanks for your questions.

 
 

Xero: HTTP Rate Limit Exceeded. – Rate Limit Simulation

 
 

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. Daniel Tzabar. Richard Cross. Xero Developer Community. Hi there, I am about to add throttling for the ’60 calls in a rolling 60 second window’ limit. However I don’t have any way of testing. I am assuming I need at least items in a test company to trigger this rate limit paged docs x 60 calls , which is a lot more than is in the test organisation.

Is there a recommended way to test this? Do I use the API to quickly populate the test organisation? Or is there some way to throttle my test API? This post of mine might be helpful, the Xero support team were able to make an app with a lower rate limit we could use for testing that we were handling the rate limit reponses from the API correctly.

Thanks Daniel. I might try this. I ended up using the API explorer to upload 6k invoices in batches of about over 30 mins.

Definitely not as elegant solution as getting the rate limited :.