: The Lexoffice API supports ETags and If-Modified-Since headers for some resources. Using these can avoid transferring unchanged data and does not count against the rate limit in the same way as full responses.
As of the current documentation, the Lexoffice API enforces a rate limit of for most authenticated endpoints. This limit is applied on a per-API-key basis, meaning each unique integration or application has its own independent quota. Additionally, there is a broader daily quota of 5,000 requests per day for the standard API tier, though this can vary depending on the specific subscription plan of the Lexoffice account owner. lexoffice api rate limit
Financial data changes relatively infrequently for many use cases. Implement caching for read-heavy endpoints like contact lists or tax types. A cache TTL (time-to-live) of 5–15 minutes can eliminate the need to query the same data repeatedly during a single user session. : The Lexoffice API supports ETags and If-Modified-Since
Use a token bucket algorithm or a simple "sleep" command in your code between consecutive calls to stay under the 2 requests/sec threshold. This limit is applied on a per-API-key basis,
Lexoffice offers batch operations for certain resources. For instance, instead of fetching 100 contacts with 100 separate GET requests, use pagination with a reasonable page size (e.g., 50 or 100 items per request). This dramatically reduces request volume while retrieving the same data.