: The first and most reliable source for information on rate limits is the official Lexoffice API documentation. Look for sections on usage guidelines, API keys, or FAQs.
Use a token bucket algorithm or a simple "sleep" command in your code between consecutive calls to stay under the 2 requests/sec threshold.
A client can make up to 2 requests per second to the API.
: Lexoffice hosts financial data for countless businesses. Without rate limiting, a single misconfigured integration or malicious script could generate thousands of requests per second, degrading performance for all other users.
If you're looking for general knowledge on handling rate limits: