Skip to main content
A few limits keep the API fast and fair for everyone. Most integrations never hit them, but it’s worth knowing where they are.

​
Rate limit

Each organization can make up to 10 requests per minute to the parse endpoint. The limit is shared across all of your organization’s API keys. If you exceed it, the request is rejected with a 429 status and a Retry-After header telling you how many seconds to wait:
Respect Retry-After and retry after that delay. Building in exponential backoff is good practice for any production integration.

​
Document size

A single document can be at most 50 pages. Larger documents are rejected with a 413 status before any parsing happens, so an oversized file never consumes credits. If you need to parse a document over 50 pages, split it into smaller files and send them as separate requests.

​
Timeouts

Parsing runs synchronously: the connection stays open until your document is fully processed and the response is returned. A document is parsed page by page, so larger files take longer — anywhere from a few seconds to a couple of minutes for a 50-page document. Set a generous client-side timeout to avoid cutting off long requests. We recommend at least 600 seconds for larger documents:

​
Summary