Juro · Rate Limits

Juro Rate Limits

Juro governs the v3 API with both a monthly request quota and per-second rate limits, and the quota depends on whether API access is on a free/trial footing or a paid subscription. Juro's documentation describes a free tier at roughly 100 requests per month and a paid tier at roughly 30,000 requests per month, both at about 10 requests per second with a burst of 20. Certain write operations carry tighter method-specific limits - contract creation is throttled more aggressively and PDF operations more aggressively still. Because API access is plan-gated, effective quotas are ultimately set by your Juro subscription; confirm exact numbers with your Customer Success Manager.

Juro Rate Limits is the machine-readable rate-limit profile for Juro on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Contract Management, CLM, Legal, Rate Limiting, and Quotas.

5 Limits Throttle: 429
Contract ManagementCLMLegalRate LimitingQuotas

Limits

Free Tier Monthly Quota account
requests
~100 per month
Free/trial API access allowance per Juro's API docs.
Paid Tier Monthly Quota account
requests
~30000 per month
Paid subscription API access allowance per Juro's API docs.
Global Request Rate account
requests
~10 per second (burst 20)
Applies across the API for all endpoints.
Contract Creation Rate account
requests
~5 per second
Tighter method-specific cap on POST /v3/contracts.
PDF Operation Rate account
requests
~1 per second
Tighter method-specific cap on PDF generation/download operations.

Policies

Plan-Governed Quota
Monthly request allowance is governed by your Juro plan; verify quota before large-scale syncs or bulk contract operations.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Pagination
List endpoints use skip/limit paging (limit default 50, max 200) to keep request counts within quota.

Sources