Register for an Availity developer account at https://developer.availity.com and create an application to receive OAuth 2.0 client credentials.
Obtain an access token by posting to the Availity OAuth2 token endpoint (POST /v1/token) with your client_id, client_secret, and grant_type=client_credentials; the response includes access_token and expiration.
Subscribe to the API products relevant to your workflow (Coverages for eligibility, Claim Statuses, Service Reviews for prior auth) via the developer portal — Demo plan subscriptions are auto-approved for sandbox testing.
For HIPAA transaction enrollment (to submit X12 270/276/278 transactions), complete the Transaction Enrollment process in the portal, which links your application to your provider organization and trading partner agreements.
Make API calls using the access token in the Authorization: Bearer header; use the Availity Payer List API to look up payer IDs before submitting transactions.
Move from Demo to Production subscription by completing Availity's review and approval process, which includes attestation of HIPAA compliance and production-readiness.
Known gotchas
The Demo (sandbox) environment uses synthetic payer responses that may not reflect real payer behavior — test edge cases with a production pilot on low-risk transactions before full go-live.
Availity's HIPAA Transaction APIs wrap X12 EDI in REST/JSON; the underlying X12 segments are still generated by Availity, but you must supply correct loop and segment data in the Availity request schema.
Transaction Enrollment (EDI trading partner setup) is separate from API OAuth registration — completing OAuth does not grant permission to submit X12 transactions until enrollment is approved.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp