Centene · Rate Limits

Centene Rate Limits

Centene's CMS-mandated FHIR APIs are gated behind partners.centene.com application registration. Per-second / per-minute throttling numbers are not published on the public portal landing; CMS Interoperability guidance allows payers to apply reasonable throttling so long as it does not interfere with the member's right to access. Limits surface during application onboarding.

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

It captures 3 rate-limit definitions, measuring varies.

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

Tagged areas include Healthcare, FHIR, CMS Interoperability, and Rate Limiting.

3 Limits Throttle: 429
HealthcareFHIRCMS InteroperabilityRate Limiting

Limits

Patient Access (per registered application) application
varies
see partner portal documentation per registered app
Provider Directory (public) IP
varies
see partner portal documentation
Provider RTR / PDEX (authorized payer) payer-account
varies
see Payer Data Exchange agreement

Policies

SMART-on-FHIR auth
Patient Access requires SMART-on-FHIR / OAuth 2.0 with member-granted scopes; tokens are short-lived and refresh tokens follow the SMART-on-FHIR profile.
Backoff
On 429 / 503, retry with exponential backoff and jitter. Honor Retry-After when supplied by the FHIR gateway.
Member access protection
Per CMS guidance, throttling must not deny a member's right to access their own clinical and financial information; investigate sustained 429s through the partner portal.

Sources