However, I can guide you on how to approach this:
If your integration performs background synchronization (e.g., nightly export of all invoices), implement a simple request queue with a token bucket algorithm. By limiting your own application to, say, 8 requests per second, you build a safety margin that avoids hitting Lexoffice’s 10-per-second ceiling.
You don’t have to guess how many requests you have left. With every API call, lexoffice sends back specific that tell you exactly where you stand: lexoffice api rate limit
Mitigates the risk of Denial of Service (DoS) attacks.
To ensure your integration remains reliable and avoids frequent throttling, follow these recommendations from the Lexware API Documentation : However, I can guide you on how to
Develop and test your integration using free Lexware Test-Accounts (valid for 30 days) before going live. Lexware API Documentation
Performance and load tests against the Public API are strictly prohibited without prior authorization from Lexware. With every API call, lexoffice sends back specific
: If the documentation doesn't provide clear information, consider reaching out to Lexoffice's support team. They can offer insights into current rate limits and any potential adjustments for your specific use case.