availity · Rate Limits

Availity Rate Limits

Rate limits for the Availity REST and X12 surfaces. Limits are per registered application / trading-partner, with separate ceilings for batch X12 vs real-time transactions. Numeric limits are not posted publicly; they are enforced via Availity's trading-partner agreement and gateway.

3 Limits Throttle: 429

HealthcareHIPAAX12 EDIRate Limiting

Limits

REST API per-application application

varies

see trading-partner agreement

Availity gates real-time eligibility / claim-status REST APIs per registered application; numeric ceilings depend on the partner agreement.

X12 batch trading-partner

varies

see trading-partner agreement

Batch X12 submissions are sized by file size and submission frequency rather than per-second RPS.

Real-time X12 (270/271, 276/277, 278) trading-partner

varies

see trading-partner agreement

Real-time 270/276/278 transactions are intended for point-of-care lookups and shaped to sub-second latency; volume is bounded by partner contract.

Policies

Backoff Strategy

Implement exponential backoff with jitter on 429 / 503. Honor Retry-After when present.

Trading Partner Agreement Governs

Sustained throughput must be authorized in the Availity trading-partner agreement; uncoordinated bursts may be throttled even if within the technical ceiling.

HIPAA / PHI Handling

All requests carry PHI; clients must operate under a BAA with Availity and adhere to HIPAA Security Rule controls in addition to rate posture.

Idempotency for Claims

837 claim submissions should use payer-assigned tracking identifiers (ICN / Claim ID) to prevent duplicate adjudication on retry.