Introducing medical and dental coverage filters to the Payers API

Jun 30, 2025

Products

You can now see whether a payer supports medical or dental transactions using the Payers API and Stedi Payer Network.

In the API, the new coverageTypes response field helps you filter the list of payers to only those you care about. If you’re using the Search Payers API endpoint, you can also filter by coverage type. Example:

GET /payers/search?query=blue+cross&coverageType=dental

If you’re using the Payer Network, you can also filter by coverage type.

Why we built this

Stedi connects to both dental and medical payers.

Customers building dental applications kept running into the same problem: they couldn’t tell which payers supported dental transactions.

Previously, you could run an eligibility check with STC 35 (General Dental Care) and parse the response – but that was a bit hacky.

We added a coverageTypes field to fix that. It tells you what kind of coverage a payer supports, so you can safely include or exclude them from your workflows.

How it works

Every payer in the network now includes a coverageTypes field in responses from Payers API endpoints – JSON and CSV. For example, in JSON responses:

{
  "items": [
    {
      "displayName": "Blue Cross Blue Shield of North Carolina",
      "primaryPayerId": "BCSNC",
      ...
      "coverageTypes": ["dental"]
      ...
    }
  ]
}

If a payer’s coverageTypes is set to ["medical", "dental"], you can submit supported transaction types for both medical and dental services.

The coverageTypes field applies to any transaction type supported by the payer: eligibility, claims, ERAs, or more.

Try it now

You can filter by coverage type today in both the Payers API and the Payer Network.

Schedule a demo to see it yourself. Or reach out to let us know what else you’d like to see.

You can now see whether a payer supports medical or dental transactions using the Payers API and Stedi Payer Network.

In the API, the new coverageTypes response field helps you filter the list of payers to only those you care about. If you’re using the Search Payers API endpoint, you can also filter by coverage type. Example:

GET /payers/search?query=blue+cross&coverageType=dental

If you’re using the Payer Network, you can also filter by coverage type.

Why we built this

Stedi connects to both dental and medical payers.

Customers building dental applications kept running into the same problem: they couldn’t tell which payers supported dental transactions.

Previously, you could run an eligibility check with STC 35 (General Dental Care) and parse the response – but that was a bit hacky.

We added a coverageTypes field to fix that. It tells you what kind of coverage a payer supports, so you can safely include or exclude them from your workflows.

How it works

Every payer in the network now includes a coverageTypes field in responses from Payers API endpoints – JSON and CSV. For example, in JSON responses:

{
  "items": [
    {
      "displayName": "Blue Cross Blue Shield of North Carolina",
      "primaryPayerId": "BCSNC",
      ...
      "coverageTypes": ["dental"]
      ...
    }
  ]
}

If a payer’s coverageTypes is set to ["medical", "dental"], you can submit supported transaction types for both medical and dental services.

The coverageTypes field applies to any transaction type supported by the payer: eligibility, claims, ERAs, or more.

Try it now

You can filter by coverage type today in both the Payers API and the Payer Network.

Schedule a demo to see it yourself. Or reach out to let us know what else you’d like to see.

You can now see whether a payer supports medical or dental transactions using the Payers API and Stedi Payer Network.

In the API, the new coverageTypes response field helps you filter the list of payers to only those you care about. If you’re using the Search Payers API endpoint, you can also filter by coverage type. Example:

GET /payers/search?query=blue+cross&coverageType=dental

If you’re using the Payer Network, you can also filter by coverage type.

Why we built this

Stedi connects to both dental and medical payers.

Customers building dental applications kept running into the same problem: they couldn’t tell which payers supported dental transactions.

Previously, you could run an eligibility check with STC 35 (General Dental Care) and parse the response – but that was a bit hacky.

We added a coverageTypes field to fix that. It tells you what kind of coverage a payer supports, so you can safely include or exclude them from your workflows.

How it works

Every payer in the network now includes a coverageTypes field in responses from Payers API endpoints – JSON and CSV. For example, in JSON responses:

{
  "items": [
    {
      "displayName": "Blue Cross Blue Shield of North Carolina",
      "primaryPayerId": "BCSNC",
      ...
      "coverageTypes": ["dental"]
      ...
    }
  ]
}

If a payer’s coverageTypes is set to ["medical", "dental"], you can submit supported transaction types for both medical and dental services.

The coverageTypes field applies to any transaction type supported by the payer: eligibility, claims, ERAs, or more.

Try it now

You can filter by coverage type today in both the Payers API and the Payer Network.

Schedule a demo to see it yourself. Or reach out to let us know what else you’d like to see.

Share

Twitter
LinkedIn

Get started with Stedi

Get started with Stedi

Automate healthcare transactions with developer-friendly APIs that support thousands of payers. Contact us to learn more and speak to the team.

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Backed by

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.

Get updates on what’s new at Stedi

Backed by

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.

Get updates on what’s new at Stedi

Backed by

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.