Availity · Rate Limits
Availity Rate Limits
Published per-plan rate limits and quotas for the Availity REST APIs, read from the developer portal product catalogue. Limits are enforced per subscribed application/plan; the plan itself is governed by the trading-partner agreement.
Availity Rate Limits is the machine-readable rate-limit profile for Availity on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring calls.
The profile also includes 6 backoff/retry policies defined and response codes documented for throttled, throttled_message, serviceUnavailable, and serviceUnavailable_note.
Tagged areas include Healthcare, HIPAA, X12 EDI, and Rate Limiting.
4 Limits
Throttle: 429
HealthcareHIPAAX12 EDIRate Limiting
Limits
Healthcare HIPAA Transactions — Standard plan, daily quota application-plan
100000
Healthcare HIPAA Transactions — Standard plan, burst rate application-plan
100
AWS Availity Payer List — Standard plan, daily quota application-plan
1000000
AWS Availity Payer List — Standard plan, burst rate application-plan
100
Policies
Client-side throttle against the published ceiling
Because there is no header signal, size a client-side token bucket to the plan ceiling (100 calls/sec on both published Standard plans) rather than reacting to the server.
Backoff strategy
Exponential backoff with jitter on 429 and 503. Honor Retry-After if one ever appears, but do not depend on it — it is not documented.
Cache the token
Tokens live 300 seconds with no refresh token. Cache and refresh at ~80% of life, serialized, so a burst does not stampede the token endpoint. See authentication/availity-authentication.yml.
Never retry a write to recover from a timeout
Availity ships no idempotency key. On 504 or a timeout on a submit, re-poll the transaction id instead of re-submitting, or risk duplicate adjudication. See conventions/availity-conventions.yml.
Trading partner agreement governs
Sustained production throughput must be authorized in the Availity trading-partner agreement; the plan tier is assigned during contracting, not self-selected.
HIPAA / PHI handling
All requests carry PHI. Clients must operate under a BAA with Availity and meet HIPAA Security Rule controls in addition to rate posture.