For the moment maesn’s unified APIs do not implement any specific rate limits. However, it is important to notice that the systems made available through the API implement their own rate limits and that these limits apply to our tenants.
It is considered good practice to implement retry logic when encountering specific error codes and this is especially true for error code 429: Too many requests. This error code indicates that the API is receiving requests at a higher rate than it can handle and unless a retry mecahnism is implemented, the requests will be lost.The best practice for implementing retry logic is called “expontential backoff”. We recommend to retry the request after an initial one-minute delay and increasing the delay exponentially with each additional retry. I.e. if a request fails due toe a 429 error, the first retry is made after one minute, the next after two minutes, then 4 minutes, etc.For more information about handling various response codes and automatic retries, see our error handling guide.
The bexio API enforces a rate limit, that limits the number of requests per minute a client can make. Currently, the limit is not published.Source: bexio Developer Portal
For the Exact Online REST API, the following rate limits apply:
Minutely limit - your app can make 60 API calls, per company, per minute.
Daily limit - your app can make 5,000 API calls, per company, per day.
The following limits are effective as of 1 July 2021:
You must not request new access token more than once every 10 minutes. You can only request for a new access token after 570 seconds from the time you successfully received the previous access token.
No more than 10 errors per API key, per user, per company, per endpoint, and per hour. When you exceed this limit, your API key will be temporarily blocked from making further requests. The block will automatically be lifted after one hour and will gradually increase when you continue making these errors. Response code 400, 401, 403, and 404 are counted as errors.
Mandatory filtering on single and bulk endpoints where sync APIs are available.
Based on fair use policy, Exact will take corrective action by throttling your app if the limit has been exceeded excessively. Some examples of excessive actions are repeated download of unchanged data every day, log in attempts to inactive accounts, and overloading the token endpoint.Source: Exact Online Knowledge Base
There is no published limit on the number of API requests for FreshBooks. However, they state that requests will be rate-limited if too many calls are made within a short period of time. Additionally, a maximum of 100 results will be returned for list methods, regardless of the value sent with the per_page parameter.Source: FreshBooks API documentation
To ensure the availability and integrity of Sage Active Public API V2, a rate limit of 3000 requests per application per minute has been set. The rate limit is set for each unique client application.Source: Sage Active Developer Portal
The Xentral API is currently rate limited independent of the plan to 100 requests/minute (one request per 600ms).Bursts of up to 300 simultaneous requests are accepted and processed as follows:
the first two requests are processed immediately
the following requests (up to 300 requests) will be queued and processed with a fixed rate of one request per 600ms (300 requests in a burst will take up to three minutes to get processed).
the response for the requests in a burst will be delayed until the request is processed.
The limits mentioned above are flagged as due to change. Please check the Xentral developer portal regularly for the latest values