For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Contact Sales
DocsAPI reference
DocsAPI reference
  • API Reference
        • GETSubmit encounter eligibility check (Availity)
        • POSTSubmit encounter eligibility check (Availity Post)
Contact Sales
LogoLogo
API ReferenceEligibilityV2

Submit encounter eligibility check (Availity)

Deprecated
GET
/api/eligibility/v2/availity
GET
/api/eligibility/v2/availity
$curl https://api.joincandidhealth.com/api/eligibility/v2/availity \
> -H "Authorization: Bearer <token>"
1{
2 "key": "value"
3}
<Tip>Candid is deprecating support for this endpoint. It is instead recommended to use [Candid's Stedi passthrough endpoint](https://docs.joincandidhealth.com/api-reference/pre-encounter/eligibility-checks/v-1/post). For assistance with the transition, please reference the [Transitioning to Candid's New Eligibility Endpoint](https://support.joincandidhealth.com/hc/en-us/articles/34918552872980) document in the Candid Support Center.</Tip> **Availity has transitioned their GET endpoint to a POST endpoint. Candid has updated their pass-through integration to enable backwards compatibility for the GET endpoint so that customers do not have to immediately update their integrations.** **Candid recommends integrations with the [POST endpoint](https://docs.joincandidhealth.com/api-reference/eligibility/v-2/submit-eligibility-check-availity-post) to ensure the best possible integration experience. Given the transition, Availity’s documentation will be out of sync with this endpoint.** If you'd like access to this endpoint, please reach out to support@joincandidhealth.com with the subject line "Action: Activate Availity Eligibility API Endpoint This API is a wrapper around Availity's coverages API. Below are some helpful documentation links: - [Availity - Coverages 1.0.0 API](https://developer.availity.com/partner/documentation#c_coverages_references) - [Candid Availity Eligibility Integration Guide](https://support.joincandidhealth.com/hc/en-us/articles/24218441631892--Availity-Eligibility-Integration-Guide) A schema of the response object can be found here: [Availity Docs](https://developer.availity.com/partner/product/191210/api/190898#/Coverages_100/operation/%2Fcoverages%2F{id}/get) * Note Availity requires a free developer account to access this documentation. Check connection status of Availity API and partners here: - [Availity Trading Partner Connection Status](https://www.availity.com/status/)
Was this page helpful?
Previous

Submit encounter eligibility check (Availity Post)

Next
Built with
Candid is deprecating support for this endpoint. It is instead recommended to use Candid’s Stedi passthrough endpoint. For assistance with the transition, please reference the Transitioning to Candid’s New Eligibility Endpoint document in the Candid Support Center.

Availity has transitioned their GET endpoint to a POST endpoint. Candid has updated their pass-through integration to enable backwards compatibility for the GET endpoint so that customers do not have to immediately update their integrations.

Candid recommends integrations with the POST endpoint to ensure the best possible integration experience. Given the transition, Availity’s documentation will be out of sync with this endpoint.

If you’d like access to this endpoint, please reach out to support@joincandidhealth.com with the subject line “Action: Activate Availity Eligibility API Endpoint

This API is a wrapper around Availity’s coverages API. Below are some helpful documentation links:

  • Availity - Coverages 1.0.0 API
  • Candid Availity Eligibility Integration Guide

A schema of the response object can be found here: Availity Docs

  • Note Availity requires a free developer account to access this documentation.

Check connection status of Availity API and partners here:

  • Availity Trading Partner Connection Status

Authentication

AuthorizationBearer

OAuth authentication of the form <token>.

Response

This endpoint returns any.

Errors

422
HTTP Request Validation Error