Flexpa · Rate Limits

Flexpa Rate Limits

Flexpa governs usage primarily through annual platform license caps - eligible users, IAL2 identity verifications, and included data retrievals - with per-active-user overage billing rather than published per-second request limits. The FHIR API additionally returns HTTP 429 while a freshly connected patient's data is still synchronizing from the payer (typically under one minute) and HTTP 422 if that synchronization fails. Specific per-second or per-minute request ceilings are not publicly documented and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring users, verifications, retrievals, and requests.

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

Tagged areas include Healthcare, FHIR, Patient Access, Claims Data, and Health Insurance.

4 Limits Throttle: 429
HealthcareFHIRPatient AccessClaims DataHealth InsuranceRate LimitingQuotasThrottling

Limits

Eligible Users account
users
per license tier (5,000 - unlimited)
Capped by platform license tier; overage billed per active user.
IAL2 Verifications account
verifications
per license tier (1,000 - 100,000)
Included identity-verification volume per annual license.
Data Retrievals account
retrievals
per license tier (10,000 - unlimited)
Included FHIR data retrievals per annual license.
Initial Patient Sync token
requests
retry after sync completes
FHIR reads/searches return 429 while payer data syncs (typically under one minute).

Policies

Sync Backoff
On a 429 during initial sync, wait briefly and retry; sync usually completes in under a minute.
License Caps
Usage is bounded by annual platform license caps with per-active-user overage billing.

Sources