Metriport · Rate Limits

Metriport Rate Limits

Metriport authenticates every request to https://api.metriport.com with an x-api-key header. The hosted cloud applies account-level rate limits and asynchronous processing - document queries and consolidated data queries run in the background and return results via webhook rather than synchronously - which naturally throttles heavy network operations. Self-hosted deployments enforce whatever limits the operator configures. Specific published per-account request-per-second or per-minute thresholds are not documented and are not reconciled in this artifact.

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 5 rate-limit definitions, measuring requests and queries.

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

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

5 Limits Throttle: 429
HealthcareMedical RecordsFHIRHealth DataWearablesOpen SourceRate LimitingQuotasThrottling

Limits

API Key Requests account
requests
see provider documentation
Account-level limits applied to the hosted cloud; not publicly itemized.
Document Query account
queries
asynchronous
Document queries run in the background and return results via webhook; they do not block synchronously.
Consolidated Data Query account
queries
asynchronous
Consolidated FHIR queries run in the background and return results via webhook.
Devices Data account
requests
see provider documentation
Per-account limits on hosted Devices API data reads.
Self-Hosted deployment
requests
operator-defined
Self-hosted deployments enforce whatever limits the operator configures.

Policies

Authentication
Every request requires a valid x-api-key header issued from the Metriport developer dashboard.
Asynchronous Processing
Long-running network operations return immediately and deliver results via webhook to reduce synchronous load.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources