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.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/sevdesk-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.