Introducing the List Payers CSV API
Jun 24, 2025
Products
You can now use the List Payers CSV API to get a full list of Stedi’s supported payers in CSV format:
curl --request GET \
--url https://healthcare.us.stedi.com/2024-04-01/payers/csv \
--header 'Authorization: <api-key>'
The CSV includes the same data as the Stedi Payer Network UI and other JSON-based Payer APIs:
Payer IDs
Transaction support flags
Transaction enrollment requirements, and more.
No setup or feature flag is needed to access the new endpoint. Just use your Stedi API key.
Why we built this
If you’ve worked with a legacy clearinghouse, you’ve probably dealt with CSV payer lists.
Sometimes they show up in your email inbox. Sometimes you have to dig them out of a portal. Either way, they’re static and go stale fast. You end up guessing what’s still valid – and maintaining brittle mappings to keep things running.
That’s risky. Every healthcare transaction depends on using the right payer ID. If the ID is wrong, the transaction fails. At scale, your system fails. And payer IDs change often.
With most clearinghouses, there’s no easy way to know which IDs still work.
That’s why we built a better way.
We already expose our payer lists programmatically through our JSON-based Payer APIs. Now you can get the same list as a CSV – updated in real time, with one row per payer. It’s easy to load into Google Sheets or Excel, feed into your tools, or compare against your current setup.
If you’re migrating to Stedi, this makes it easier. One API call gives you everything you need.
How it works
Make a GET request to the List Payers CSV API endpoint:
curl --request GET \
--url https://healthcare.us.stedi.com/2024-04-01/payers/csv \
--header 'Authorization: <api-key>'
You’ll get a plain-text CSV. The first row contains headers. Each row after that is one payer.

The CSV includes:
The payer’s immutable Stedi payer ID
Their name, primary payer ID, and known payer ID aliases
Supported transaction types
Whether transaction enrollment is required for a transaction type
Try it out
The List Payers CSV API is free on all paid Stedi plans.
To see how it works for yourself, reach out to schedule a demo.
You can now use the List Payers CSV API to get a full list of Stedi’s supported payers in CSV format:
curl --request GET \
--url https://healthcare.us.stedi.com/2024-04-01/payers/csv \
--header 'Authorization: <api-key>'
The CSV includes the same data as the Stedi Payer Network UI and other JSON-based Payer APIs:
Payer IDs
Transaction support flags
Transaction enrollment requirements, and more.
No setup or feature flag is needed to access the new endpoint. Just use your Stedi API key.
Why we built this
If you’ve worked with a legacy clearinghouse, you’ve probably dealt with CSV payer lists.
Sometimes they show up in your email inbox. Sometimes you have to dig them out of a portal. Either way, they’re static and go stale fast. You end up guessing what’s still valid – and maintaining brittle mappings to keep things running.
That’s risky. Every healthcare transaction depends on using the right payer ID. If the ID is wrong, the transaction fails. At scale, your system fails. And payer IDs change often.
With most clearinghouses, there’s no easy way to know which IDs still work.
That’s why we built a better way.
We already expose our payer lists programmatically through our JSON-based Payer APIs. Now you can get the same list as a CSV – updated in real time, with one row per payer. It’s easy to load into Google Sheets or Excel, feed into your tools, or compare against your current setup.
If you’re migrating to Stedi, this makes it easier. One API call gives you everything you need.
How it works
Make a GET request to the List Payers CSV API endpoint:
curl --request GET \
--url https://healthcare.us.stedi.com/2024-04-01/payers/csv \
--header 'Authorization: <api-key>'
You’ll get a plain-text CSV. The first row contains headers. Each row after that is one payer.

The CSV includes:
The payer’s immutable Stedi payer ID
Their name, primary payer ID, and known payer ID aliases
Supported transaction types
Whether transaction enrollment is required for a transaction type
Try it out
The List Payers CSV API is free on all paid Stedi plans.
To see how it works for yourself, reach out to schedule a demo.
You can now use the List Payers CSV API to get a full list of Stedi’s supported payers in CSV format:
curl --request GET \
--url https://healthcare.us.stedi.com/2024-04-01/payers/csv \
--header 'Authorization: <api-key>'
The CSV includes the same data as the Stedi Payer Network UI and other JSON-based Payer APIs:
Payer IDs
Transaction support flags
Transaction enrollment requirements, and more.
No setup or feature flag is needed to access the new endpoint. Just use your Stedi API key.
Why we built this
If you’ve worked with a legacy clearinghouse, you’ve probably dealt with CSV payer lists.
Sometimes they show up in your email inbox. Sometimes you have to dig them out of a portal. Either way, they’re static and go stale fast. You end up guessing what’s still valid – and maintaining brittle mappings to keep things running.
That’s risky. Every healthcare transaction depends on using the right payer ID. If the ID is wrong, the transaction fails. At scale, your system fails. And payer IDs change often.
With most clearinghouses, there’s no easy way to know which IDs still work.
That’s why we built a better way.
We already expose our payer lists programmatically through our JSON-based Payer APIs. Now you can get the same list as a CSV – updated in real time, with one row per payer. It’s easy to load into Google Sheets or Excel, feed into your tools, or compare against your current setup.
If you’re migrating to Stedi, this makes it easier. One API call gives you everything you need.
How it works
Make a GET request to the List Payers CSV API endpoint:
curl --request GET \
--url https://healthcare.us.stedi.com/2024-04-01/payers/csv \
--header 'Authorization: <api-key>'
You’ll get a plain-text CSV. The first row contains headers. Each row after that is one payer.

The CSV includes:
The payer’s immutable Stedi payer ID
Their name, primary payer ID, and known payer ID aliases
Supported transaction types
Whether transaction enrollment is required for a transaction type
Try it out
The List Payers CSV API is free on all paid Stedi plans.
To see how it works for yourself, reach out to schedule a demo.
Share
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.