Skip to content

API limits

File sizes, page counts, request sizes, job queues and webhook timing.

The API is built for one person’s Mac: it enforces these limits so a single request can’t exhaust memory or disk. A request over a limit gets 413, 422 or 429 with a detail that names it.

Files

LimitValue
pdf_merge inputs2 or more PDFs, no upper limit
pdf_run_batch inputs1 to 50 PDFs
Steps in a pipeline or batch1 to 10

Fields

LimitValue
pagesUp to 200 characters, such as 1, 3-5
pdf_read_text max_chars100 to 200,000 (default 20,000)
pdf_extract_structure max_chars100 to 400,000 (default 60,000)
PasswordsUp to 127 characters
Watermark textUp to 60 characters
Page label textUp to 120 characters

Requests

LimitValue
Request body1 MB
Time to send a request5 minutes to receive it; a tool then runs as long as it needs
Tool calls at once4, of which 2 LibreOffice conversions; up to 64 more wait in order (then 429)

Jobs

LimitValue
Jobs running at once1, in the order received
Jobs waiting100 (then 429)
Finished jobs kept1 hour, at most 500, until the API stops
callback_urlUp to 2,048 characters

Webhooks

LimitValue
Delivery attempts5, after 1, 2, 4 and 8 seconds
Time to answer10 seconds per attempt
Signature age accepted (by your receiver)5 minutes

Security

LimitValue
SUPERPDF_API_TOKENAt least 32 characters

Concurrency

Tool calls are handled as they arrive and share this Mac’s processor, so several heavy calls at once each take longer. Jobs run one at a time, in the order received, so a batch never competes with itself. For many files, prefer one pdf_run_batch job over many parallel calls.