Metriport · Rate Limits

Metriport Rate Limits

Metriport publishes a per-operation rate-limit table on its Limits and throttling page: eight named limits, all expressed as requests per minute against the hosted cloud at https://api.metriport.com. What it does not publish is any runtime signal — no X-RateLimit-* or RateLimit-* response headers, no documented status code on exhaustion, and no Retry-After behaviour. A client therefore knows the ceiling from the docs but cannot discover its remaining budget, or even reliably detect that it has been throttled, from a response. Higher limits are negotiated by emailing support@metriport.com. Self-hosted deployments enforce whatever the operator configures.

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

It captures 10 rate-limit definitions, measuring requests.

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

Tagged areas include Healthcare, Medical Records, FHIR, Health Data, and Open Source.

10 Limits Throttle: not documented
HealthcareMedical RecordsFHIRHealth DataOpen SourceRate LimitingQuotasThrottling

Limits

Patient Create account
requests
15
Patient Update account
requests
15
Document Query Start (Legacy) account
requests
20
Consolidated Data Query Start account
requests
120
Patient Consolidated Create account
requests
120
Send Message account
requests
20
Network Query — HIE account
requests
20
Network Query — Labs account
requests
20
Network Query — Pharmacy account
requests
20
Self-Hosted deployment
requests
operator-defined

Policies

Authentication
Every request requires a valid x-api-key header issued from the Metriport developer dashboard.
Limit Increases
Accounts whose request pattern needs higher limits contact support@metriport.com.
Asynchronous Processing
Network queries, consolidated data queries and bulk operations return immediately and deliver results by webhook, which spreads load off the synchronous path. See asyncapi/metriport-webhooks.yml.
Backoff Strategy
No provider guidance is published. Because no rate-limit headers and no exhaustion code are documented, clients should pace to the published per-minute ceilings rather than react to a runtime signal.

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/metriport-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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