sevdesk · Rate Limits

Sevdesk Rate Limits

sevdesk does not publish fixed numeric rate limits for its REST API in the official OpenAPI specification or developer documentation. In practice the API is a shared multi-tenant SaaS surface, so clients should assume server-side throttling exists and design defensively - use pagination (limit / offset), request only the fields needed, use the embed parameter to reduce round trips, and back off on throttling responses. Bulk and long-running work (DATEV / CSV exports) is handled asynchronously through export jobs polled at /Progress/getProgress, which naturally spreads load rather than requiring large synchronous requests.

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

It captures 3 rate-limit definitions, measuring requests, records, and jobs.

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

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

3 Limits Throttle: 429
AccountingInvoicingSaaSRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the sevdesk API.
List Pagination request
records
configurable via limit / offset
List endpoints page results with the limit and offset query parameters.
Export Jobs account
jobs
async / progress-tracked
DATEV and CSV exports run as jobs polled at /Progress/getProgress instead of large synchronous calls.

Policies

Backoff Strategy
On 429 (or 5xx) responses, back off exponentially with jitter and honor any Retry-After header before retrying.
Payload Minimization
Use limit/offset and the embed parameter to fetch only needed records and nested resources, reducing request volume.
Asynchronous Export
Prefer the export-job endpoints for bulk data rather than repeatedly paging large synchronous result sets.

Sources