Skip to main content
Rate limits help keep the API fast and available for everyone. They prevent any single user or accidental spike in traffic from slowing things down for others. Limits apply per organization, so all API keys in an organization share them. When you exceed a rate limit, the API returns an HTTP 429 response; wait before retrying and use exponential backoff.

​
Parse v2 API

The following limits apply to the Parse v2 API. The rate limit depends on your pricing plan.
LimitValue
Maximum document size50 MiB.
Maximum pages per request100 per PDF. An image counts as one page.
Rate limitBased on the number of pages processed.

​
Parse Jobs

Parse Jobs v2 accepts much larger documents than synchronous parsing and meters usage against an hourly limit.
LimitValue
Maximum document size1 GiB for PDFs, 50 MiB for images.
Maximum pages per request6,000 per PDF.
Rate limitBased on the number of pages processed, measured against your plan’s hourly limit. Both service tiers share the same hourly limit; the tier affects turnaround time and credit consumption only.
To set the tier, see Choose a Service Tier.

​
Extract v2 API

The following limits apply to the Extract v2 API. The rate limit depends on your pricing plan.
LimitValue
Maximum input sizeNo limit.
Rate limitBased on the size of the input Markdown. A markdown_url counts as a single unit.

​
Extract Jobs

Extract Jobs v2 has no input size cap, and creating a job never returns a rate-limit error. Submissions are accepted immediately (HTTP 202) and paced internally against a per-minute budget, so a burst of jobs waits in the queue instead of failing. The service tier affects turnaround time and credit consumption only. To set the tier, see Choose a Service Tier.