lexoffice · Rate Limits

Lexoffice Rate Limits

lexoffice (lexware Office) rate limits the public API to a fixed 2 requests per second per client. Requests beyond that rate are rejected with HTTP 429 (Too Many Requests). The authorization/authentication server is documented to have its own independent rate limits and also returns 429 when exceeded. There is no published per-day or per-month request quota for the REST API itself; usage is bounded by the per-second cap and by the underlying subscription plan.

Lexoffice Rate Limits is the machine-readable rate-limit profile for lexoffice on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Accounting, Invoicing, Germany, Rate Limiting, and Quotas.

3 Limits Throttle: 429
AccountingInvoicingGermanyRate LimitingQuotas

Limits

API Requests client
requests
2 per second
Fixed limit across the REST API; HTTP 429 when exceeded.
Authorization Server Requests client
requests
independent (not numerically published)
The auth server has its own separate rate limit and also returns 429.
Daily / Monthly Quota account
requests
not published
No fixed per-day or per-month request quota is documented for the REST API.

Policies

Throttling
Keep sustained request rate at or below 2 requests per second per client to avoid HTTP 429 responses.
Backoff Strategy
On a 429 response, back off and retry with exponential backoff plus jitter rather than retrying immediately.
Serialization
Because the limit is per-second and low, batch/bulk jobs should serialize calls rather than fan out concurrently.

Sources