Ambra Health · Rate Limits

Ambra Health Rate Limits

The Ambra Health / InteleShare v3 Services Public API reference does not publish fixed numeric rate limits, per-minute request caps, or a documented throttling (429) contract. As an enterprise, per-tenant healthcare platform, practical throughput is governed by the customer's environment and platform agreement rather than a public per-key quota. The API does provide a first-class /bundle endpoint that executes many calls sequentially in a single HTTP request, which is the documented mechanism for reducing round trips and request volume. Clients should still implement retry-with-backoff and treat any throttling or transient error responses defensively.

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

It captures 4 rate-limit definitions, measuring requests, calls, studies, and bytes.

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

Tagged areas include Medical Imaging, DICOM, Healthcare, PACS, and Rate Limiting.

4 Limits Throttle: 429
Medical ImagingDICOMHealthcarePACSRate LimitingQuotas

Limits

v3 Services API Requests session
requests
not published
No fixed numeric per-session or per-account request-rate limit is documented in the v3 reference.
Bundle Batch Size request
calls
not published (sequential execution)
The /bundle endpoint accepts a JSON array of calls executed sequentially; use it to consolidate round trips.
Storage / Study Volume account
studies
per agreement
Stored study and image volume is governed by the customer's platform agreement, not a public API quota.
Study Upload / Download Throughput account
bytes
environment-bound
Image transfer throughput depends on the customer's Ambra cloud environment and network, not a documented cap.

Policies

Bundling
Use POST /bundle with inherit_sid and the X-AmbraHealth-SID header to run many calls in one request and reduce load.
Backoff Strategy
Implement exponential backoff with jitter on transient errors, and honor any Retry-After header if returned on throttling.
Session Reuse
Reuse the sid from /session/login across calls rather than re-authenticating per request to avoid unnecessary session churn.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/ambra-health-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.