Cloudmersive · Rate Limits

Cloudmersive Rate Limits

Cloudmersive enforces concurrency limits per API key (calls-per-second) and a monthly call quota tied to the subscribed plan. Calls beyond the concurrency cap are queued for execution rather than rejected with 429s. Higher throughput requires a larger plan or a single-tenant / on-premises deployment.

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

It captures 10 rate-limit definitions, measuring requests_per_second and requests_per_month.

The profile also includes 4 backoff/retry policies defined and response codes documented for quotaExceeded, throttled, and serviceUnavailable.

Tagged areas include Documents, Conversions, OCR, Validation, and Virus Scanning.

10 Limits Throttle: 429 Quota: 402
DocumentsConversionsOCRValidationVirus ScanningRate Limiting

Limits

Free Tier Concurrency api-key
requests_per_second · second
1
Free plan caps simultaneous calls to 1 per second; excess calls queue.
Basic / Business Concurrency api-key
requests_per_second · second
2
Basic ($19.99/mo) and Business ($49.99/mo) plans share the 2 calls/second concurrency ceiling.
Business Premier Concurrency api-key
requests_per_second · second
3
Business Advantage Concurrency api-key
requests_per_second · second
4
Free Monthly Quota api-key
requests_per_month · month
600
Basic Monthly Quota api-key
requests_per_month · month
10000
Business Monthly Quota api-key
requests_per_month · month
25000
Business Premier Monthly Quota api-key
requests_per_month · month
50000
Business Advantage Monthly Quota api-key
requests_per_month · month
100000
Enterprise / Government Concurrency contract
requests_per_second
see vendor sales
Single-tenant cloud, on-premises, and government deployments support negotiated throughput.

Policies

Queueing on Concurrency
Calls in excess of the per-second concurrency ceiling are queued for execution rather than rejected immediately; sustained over-subscription results in degraded latency.
Plan Quota Enforcement
Once the monthly call quota is exhausted the API key is blocked until the next billing cycle or until the plan is upgraded.
Backoff Strategy
Clients should implement exponential backoff with jitter and respect any Retry-After header returned with 429 responses.
Single-tenant / On-premises
For higher concurrency or strict isolation, customers deploy single-tenant cloud or on-premises stacks where limits are sized to the host hardware.

Sources