Intelerad · Rate Limits

Intelerad Rate Limits

Intelerad does not publish fixed numeric rate limits for the InteleShare / Ambra v3 Services or Storage APIs in the public reference. Access is gated by session (sid), Basic, or OAuth authentication and by per-account, per-role, and per-namespace permissions rather than by a documented public per-minute request cap. Practical throughput is bounded by account entitlement and by the study / image volume of the contracted deployment. The v3 API signals errors with a status of "ERROR" plus HTTP codes such as 401 (authorization), 405 (invalid method), and 412 (precondition failed).

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

It captures 3 rate-limit definitions, measuring requests and bytes.

The profile also includes 2 backoff/retry policies defined and response codes documented for unauthorized, invalidMethod, and preconditionFailed.

Tagged areas include Medical Imaging, PACS, Image Exchange, Rate Limiting, and Quotas.

3 Limits
Medical ImagingPACSImage ExchangeRate LimitingQuotas

Limits

v3 Services API Requests account
requests
not published
No fixed numeric request-rate limit is documented; access governed by auth, roles, and namespace permissions.
Storage API Throughput account
bytes
not published
Image upload / retrieve throughput bounded by account entitlement and deployment scope.
DICOMweb Access account
requests
not published
WADO-RS / QIDO-RS / STOW-RS access governed by the same authentication and permission model.

Policies

Permission-Scoped Access
Access is controlled by a role/permission matrix (Admin, User, PHR, Anonymous) and by namespace scoping rather than a global public rate limit.
Backoff Strategy
Clients should implement exponential backoff with jitter and handle 401 / 405 / 412 responses and ERROR status payloads gracefully.

Sources