Looking for:
Xero api limits - xero api limits.Xero API Usage Limit |
Xero api limits - xero api limits.Testing the Limits of Xero for Businesses With Higher Transaction Volumes
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Hi minimul ,. Xero has API rate limiting. 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? Typically this limit is not an issue because the driver will automatically retry the current request if this occurs.
Per-Minute Limit. At most 60 API calls per minute may be made from the application to the same organization. This limit is also not an issue as Xero reports a recommended delay time that the driver will use to avoid hitting the limit again. Per-Day Limit. The tests run on a MacBook with Firefox and Chrome browsers. We also perform some uploads via the API mainly to load Xero for testing.
The back ends of modern computer systems can handle massive amounts of data very easily, so it is actually surprising to hear that cloud systems hit performance problems at fairly low levels of transactions. The first phase of testing looks at how the size of data in a Xero file affects reporting.
Because we loaded the data in a flat-file before testing began, the testing activities described below only reflect the use of the file at that time. This is like a business doing reporting after hours when there are no orders being entered, for example.
Therefore, this testing looks for the impact of historical data on reporting and searching performance. Testing showed that performance problems will come more from simultaneous load on the system rather than the volume of historical transactions. Even with transaction volumes 10 times what Xero indicates as the upper limit, Xero shows no ill-effects due to transaction history. However, the performance impact of transaction entry is greater. Note that this is different to MYOB AccountRight desktop software, which suffers serious performance problems with high volumes of historical data.
The transaction volume entered here would severely stress MYOB. Xero has no limit on the number of users. However, we discovered in our testing that simultaneous entry of invoices causes problems. Xero assigns a next invoice number when a user starts entering an invoice.
This number is not reserved, so if another user starts a new invoice, it will get the same number. In fact, five users keying in invoices would all get the same number; a number is only reserved when an invoice is saved including saving as a draft, as well as sending it straight to approval. Our testing shows that with more than two users entering invoices at the same time, Xero overwrites invoices.
This is actually the first real problem our testing showed while investigating Xero at higher loads. We did not find a workaround for this. It is possible to manually enter invoice numbers but it would require each user to have a pool of numbers to use. Each user would need to manually keep track of the next number. A number is reserved when you save and continue editing, but this only works if you can guarantee that only one user does that at any given time.
In summary, Xero is not ready for multiple users doing order entry via the browser. Possibly it would be ok with two, but more than that is asking for trouble i. Period: three years No. Each month contains about transactions invoices lines and bank feed. In our test environment we did not include accounts payable and payroll so it misses transaction volume in these areas. However, a business which is scaling up is likely to more likely to see transaction volume growth in the area of sales.
There are no inventory transactions in this scenario because they are managed in the supply chain front end. If you are using Xero for detailed inventory transactions our test scenario may not be accurate. The files were loaded one per year so one file of invoices, and one bank statement.
Each file took only a few minutes to upload and approve the resulting draft invoices. The bank statements also loaded very quickly. The upload was designed so that Xero would immediately recognise matches each invoice totalled to a unique amount, matching receipts on the bank statement. However, there is no way to automatically approve the suggested matches as it is not done via the API.
No comments:
Post a Comment