Skip to main content
Rate limits cap how much work your organization can submit in a given time window, so one user or an accidental traffic spike cannot slow processing for everyone else. 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 Parse v2 API has two kinds of limits:

​
Size Limits

Size limits apply per request and differ between synchronous requests and async jobs:

​
Rate Limits

Every request counts against one of two rate limits, one per service tier, and the two limits are independent of each other. Synchronous requests and priority jobs count against the same priority limit, so splitting traffic across the two routes does not increase capacity. Jobs run on the standard tier by default. To set a job’s tier, see Choose a Service Tier.
The Explore values apply once you purchase credits. During the free trial, a lower standard limit applies.

​
Run Large Documents as Async Jobs on the Standard Tier

A parse request is admitted against its tier’s rate limit all at once. This means a document with more pages than your priority per-minute limit can never run on the priority tier: the request returns a 429 error no matter how long you wait between retries. The error message states the limit and the fix. This is by design. The priority tier is sized for interactive work, so your plan’s per-minute limit is also the largest single document the tier accepts. Submit larger documents as a Parse Job on the standard tier, which accepts up to 6,000 pages per PDF.

​
Extract v2 API

The Extract v2 API has no input size limit, and rate limiting differs between synchronous requests and async jobs. The synchronous limit depends on your pricing plan. For jobs, the service tier affects turnaround time and credit consumption only. To set a job’s tier, see Choose a Service Tier.