Xero: HTTP Rate Limit Exceeded..Xero Community – API rate limit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Already have an account? Xeroizer allows us to sleep for a number of seconds if the request fails in response to the OAuth::RateLimitExceeded error. 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.
 
 

– 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.

Vanessa Thornton Xero Staff. Dimitri Adamou. Lunar Farside. Xero Developer Community. We have an integration application which creates invoices on Xero using the API. 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. 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. This allows for an application to make a maximum of 60 calls within a given 60 second rolling window. Our second rate limit is our daily rate limit.

This will allow applications to make a maximum amount of calls over a 24 hour rolling window. Your retry logic is the right approach but may need to be tweaked to take into account the amount of calls you can make over a 60 second period.

In regards to refreshing your keys, What type of application have you signed up as? Public, Private, or Partner? Each of our application types requires using access keys differently. If you are a Public app then refreshing your keys will result in having to get your clients to re-auth your application every 30 mins.

Our Partner applications should be able to refresh access keys without the need for their clients to re-auth. If you are a Partner application and are still having issues with refreshing access tokens, we can investigate further to see why this is happening. Cheers Vanessa. Are you by any chance using the PHP Api?

We have a Partner Application. Refreshing the keys normally works, however while I was experimenting with the rate limit problem I have described above, I couldn’t refresh for that one time. Also are you checking for the header error ?

Missing Support for Rate Limit Handling · Issue #84 · XeroAPI/xero-ruby · 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. Robin B Community Manager. Philip Compton. Xero Developer Community.

Are there any additional details on how exactly the ‘per minute’ rate limit is calculated? We manage our call rate proactively and carefully to make sure we don’t exceed the limit, but we still do. We received a rate limit warning at ” Looking at the API call history log that is available and counting every call between ” When we introduced the OAuth 2. The previous behaviour was to check how many calls were made in the previous 60 seconds – it sounds like this is how you are calculating the limit.

Under OAuth 2. That said, this would typically allow more than 60 calls in the previous 60 seconds – as the reset would have occurred at some stage through the 60 seconds. In any case, we suggest that you use the response headers to see how far through the limit you are at any given time.

These are included on all calls and let your app see how many calls remain on each of the limits. Otherwise we will probably have to shift to being reactive as you suggest.

Xero Community – API rate limit.Xero: HTTP Rate Limit Exceeded.

 
 
As I understand it, the API endpoint issues HTTP errors and for retryable Here’s a first pass at implementing a rate limiter for the minute limit. Codes summary ; , Rate Limit Exceeded, The API rate limit for your organisation/application pairing has been exceeded. Learn more ; , Internal Error, An. It restricts the number of API calls that can be sent per minute to the Xero API server.