Learn about rate limits for maesn’s unified APIs
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.
For the abacus API, the following rate limits apply:
Source: abacus API documentation
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 BuchhaltungsButler API, the following rate limits apply:
Source: BuchhaltungsButler API documentation
No rate-limits are known for the DATEV Online APIs at the time of writing.
No rate-limits are known for the DATEV Online APIs at the time of writing.
For the Exact Online REST API, the following rate limits apply:
The following limits are effective as of 1 July 2021:
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
For the fortnox REST API, the following rate limit apply:
Source: fortnox API documentation
For FreeAgent API, the following rate limits apply:
Source: FreeAgent API documentation
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
The holded API has a rate-limit of 1500 requests per 60 seconds.
For the Lexware Office Partner API, the following rate limits apply:
Source: Lexware Office Partner API documentation
Business Central imposes a range of strict and well-defined limits both per environment and user. Some examples:
Source: Microsoft Developer Portal
The Moneybird API has a rate-limit of 150 requests per 5 minutes.
1 call/sec is the official rate limit for Odoo.
QuickBooks implement the following rate limits and throttles:
Source: Intuit Developer Portal
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 sevdesk API enforces a rate limit, that limits the number of requests per minute a client can make. Currently, the limit is not published.
No rate-limits are known for the Twinfield API at the time of writing
Visma eAccounting implements the following rate limits:
Visma e-conomic implements the following rate limits:
The weclapp API enforces a rate limit, that limits the number of requests per minute a client can make. Currently, the limit is not published.
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:
Source: Xentral Developer Portal
Xero implements three types of rate limiting against the respective tenant:
Source: Xero Developer Portal
Learn about rate limits for maesn’s unified APIs
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.
For the abacus API, the following rate limits apply:
Source: abacus API documentation
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 BuchhaltungsButler API, the following rate limits apply:
Source: BuchhaltungsButler API documentation
No rate-limits are known for the DATEV Online APIs at the time of writing.
No rate-limits are known for the DATEV Online APIs at the time of writing.
For the Exact Online REST API, the following rate limits apply:
The following limits are effective as of 1 July 2021:
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
For the fortnox REST API, the following rate limit apply:
Source: fortnox API documentation
For FreeAgent API, the following rate limits apply:
Source: FreeAgent API documentation
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
The holded API has a rate-limit of 1500 requests per 60 seconds.
For the Lexware Office Partner API, the following rate limits apply:
Source: Lexware Office Partner API documentation
Business Central imposes a range of strict and well-defined limits both per environment and user. Some examples:
Source: Microsoft Developer Portal
The Moneybird API has a rate-limit of 150 requests per 5 minutes.
1 call/sec is the official rate limit for Odoo.
QuickBooks implement the following rate limits and throttles:
Source: Intuit Developer Portal
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 sevdesk API enforces a rate limit, that limits the number of requests per minute a client can make. Currently, the limit is not published.
No rate-limits are known for the Twinfield API at the time of writing
Visma eAccounting implements the following rate limits:
Visma e-conomic implements the following rate limits:
The weclapp API enforces a rate limit, that limits the number of requests per minute a client can make. Currently, the limit is not published.
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:
Source: Xentral Developer Portal
Xero implements three types of rate limiting against the respective tenant:
Source: Xero Developer Portal