Rate Limits

Limits

Context	Requests/min	Expensive ops/min
Authenticated	600	30
Unauthenticated	60	5

“Expensive ops” include POST /v1/documents (uploads), POST /v1/documents/{id}/structured-output, and POST /v1/documents/{id}/chat/completions. All other endpoints count as standard requests.

Rate limit headers

Every API response includes rate limit information:

Header	Description
`X-RateLimit-Limit`	Max requests per window
`X-RateLimit-Remaining`	Requests remaining
`X-RateLimit-Reset`	Unix timestamp when window resets

When rate limited

You receive a 429 response:

{
  "error": {
    "code": "RATE_LIMITED",
    "message": "Rate limit exceeded. Please try again later."
  }
}

The Retry-After header tells you how many seconds to wait.

Best practices

Check headers before hitting limits — monitor X-RateLimit-Remaining
Use exponential backoff on 429 responses
Batch small PDFs — prefer one large job over many small ones
Cache results — store extraction results locally after fetching

import time

def respect_rate_limit(response):
    remaining = int(response.headers.get("X-RateLimit-Remaining", 1))
    if remaining <= 1:
        reset = int(response.headers.get("X-RateLimit-Reset", 0))
        wait = max(0, reset - time.time())
        time.sleep(wait)

Errors How It Works

Overview

Files

Documents

Content

Entities

AI

Exports

Hosting

Conversions

Agents

Workflows

Collections

Filings (Data API)

Companies (Data API)

SDK & React

Limits

Rate limit headers

When rate limited

Best practices

​Limits

​Rate limit headers

​When rate limited

​Best practices

Limits

Rate limit headers

When rate limited

Best practices