Rate limiting

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 tenats:

​

Datev Unternehmen Online

No rate-limits are known for the Datev Online APIs at the time of writing.

​

Lexoffice

For the Lexoffice Partner API, the following rate limits apply:

• 2 requests per second, connection and endpoint (burst size: 5)
• 5 requests per second, API client and endpoint (burst size: 5)

Source: Lexoffice Partner API documentation

​

Microsoft Business Central

Business Central imposes a range of strict and well-defined limits both per environment and user. Some examples:

• Per environment:
  • 5 concurrent requests
  • 100 concurrent connections
  • 300/600 requests per minute in the sandbox/production environment
• Per user:
  • 5 concurrent requests
  • 100 concurrent connections
  • 6000 requests within a 5-minute sliding window

Source: Microsoft Developer Portal

​

QuickBooks

QuickBooks implement the following rate limits and throttles:

• For Online API endpoints:
  • 500 requests per minute per realm ID
  • 10 concurrent requests per realm ID and app
• For Batch endpoints:
  • Recommended maximum number of payloads in a single batch request is 30
  • Throttled at 40 requests per minute, per realm ID

Source: Intuit Developer Portal

​

Sage Active

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

​

Sevdesk

No rate-limits are known for the Sevdesk API at the time of writing

​

Xentral

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.

Source: Xentral Developer Portal

​

Xero

Xero implements three types of rate limiting against the respective tenant:

• Concurrent calls: 5 calls in progress at one time
• Minute Limit: 60 calls in a rolling 60-second window
• Daily Limit: 5000 calls in a rolling 24-hour window

Source: Xero Developer Portal