Sejda Rate Limits
The Sejda HTML to PDF API does not meter or cap the total number of PDFs generated. Instead it limits the maximum number of requests per hour and the number of concurrent (in-flight) requests, both of which scale with the subscription tier. Exceeding either limit returns HTTP 429. A self-hosted deployment removes the requests-per-hour restriction. Request payloads are capped at 50MB (HTTP 413 when exceeded). Sejda's free web/desktop apps apply separate page, hourly, and per-tool limits unrelated to the API.
Sejda Rate Limits is the machine-readable rate-limit profile for Sejda on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, concurrency, and bytes.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and payloadTooLarge.
Tagged areas include PDF, HTML to PDF, Rate Limiting, Quotas, and Throttling.
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/sejda-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.