OpenClinica · Rate Limits

Openclinica Rate Limits

OpenClinica does not publish fixed numeric REST API rate limits. Access is gated by OAuth 2.0 bearer tokens and by the study/site privileges of the authenticating user rather than by a documented per-minute request cap. On the self-hosted Community Edition, throughput is bounded by your own infrastructure. On Enterprise (hosted) instances, practical throughput is governed by the hosted environment and your agreement. Large data movements are designed to run as asynchronous bulk operations (bulk participants, bulk events, extracts) whose status is tracked through the bulk actions log, rather than as many small synchronous calls.

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

It captures 4 rate-limit definitions, measuring requests, records, and seconds.

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

Tagged areas include Clinical Trials, Electronic Data Capture, EDC, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Clinical TrialsElectronic Data CaptureEDCRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the REST API.
Self-Hosted Throughput deployment
requests
hardware-bound
Community Edition throughput is constrained by your own infrastructure.
Bulk Operation Size request
records
configurable via payload
Bulk participant and event endpoints accept a list per request and process it asynchronously.
Token Lifetime account
seconds
per expires_in
OAuth access tokens expire; re-request a token from the user-service token endpoint when expired.

Policies

Authorization Scoping
A user's study and site privileges bound which participants, events, and data the API returns or accepts.
Asynchronous Bulk Processing
Bulk actions run as jobs; poll the bulk actions log for status rather than blocking on large synchronous calls.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources