> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.joincandidhealth.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.joincandidhealth.com/_mcp/server.

Candid Health supports most payers. You can find a list of supported payers with their respective `payer_id`, `primary_name`, 'availity_claims_professional_id', and 'availity_claims_institutional_id' [here](https://app.joincandidhealth.com/dynamic-files/payers-list.csv).

The `payer_id` and `primary_name` should be used in the `payer_id` and `payer_name` fields of the subscriber's insurance card information and when you use the [Encounters](../api-reference/encounters) endpoint.

When denoting a claim as self-pay, please use the `responsible party` field on the [Encounters](../api-reference/encounters) endpoint.

If your organization uses [Payer Plan Groups](../api-reference/payer-plan-groups), you can omit `payer_id` and `payer_name`. Instead, pass the `payer_plan_group_name` and set `emr_payer_crosswalk` to `PAYER_PLAN_GROUP`. The subscriber's payer information will be automatically populated based on your configured Payer Plan Group settings. Encounters created with an unconfigured payer plan group name will be routed to a queue where you can configure the payer plan group.

> **Info**
>
> When submitting claims to Candid, ensure you are using the exact `primary_name` and `payer_id` from the provided [CSV](https://app.joincandidhealth.com/dynamic-files/payers-list.csv). The relationship between `primary_name` and `payer_id` is not one-to-one, meaning that certain `payer_id`s are used for multiple payers. As such, Candid has to do a match on a combination of `primary_name` and `payer_id` to determine the right destination for the claim.