Limits: uploads, pages, corrections, rates
Size and pages
The same limits as the interface, per plan. These numbers are read from the service when this page is shown, so they are the ones it enforces; they are also at GET /v1/plans.
| Plan | Largest upload | Pages per document | Corrections a day |
|---|---|---|---|
| Free | 15 MB | 50 | 10 |
| 1 document | 50 MB | 50 | Unlimited while a credit is unspent, for up to 30 days after a purchase, then 10 |
| 10 documents | 50 MB | 50 | Unlimited while a credit is unspent, for up to 30 days after a purchase, then 10 |
| Personal | 100 MB | 100 | Unlimited |
| Business | 100 MB | 300 | Unlimited |
The free daily limit on this deployment is 10 corrections. API keys belong to Business accounts, whose corrections are unlimited.
A file over the limit answers 413 file_too_large, and a document with too many pages 422 too_many_pages; both messages name the limit.
A file sent to be compressed (POST /v1/compress) has a ceiling of its own, the same for every plan: 100 MB unless the deployment sets another. Over it the answer is 413 compress_too_large, with size_mb and limit_mb. The page limit above still applies to it, since what is chosen becomes a document.
Rate limits
Each key may make 120 requests a minute, in bursts of up to 30 at once. Every response to a key carries X-RateLimit-Limit (requests a minute), X-RateLimit-Remaining (requests you can send now) and X-RateLimit-Reset (seconds until the allowance is full again). Past the limit the answer is 429 too_many_requests with a Retry-After in seconds.
A busy engine is different from a rate limit: 503 busy means every engine slot is in use for a moment, not that your key has done too much. It also carries Retry-After, and the request is safe to send again because it did nothing.
Work on a large file takes turns. An upload, a correction or an export of a file over 15 MB runs one at a time across the service, because the memory it takes grows with the file. A second one waits its turn for up to a minute and then answers 503 busy in the same way. Looking at a page of a large file does not wait.
Last updated