You can now use the Retrieve Payer API endpoint to get a single payer record by its Stedi payer ID:

curl --request GET \
  --url https://healthcare.us.stedi.com/2024-04-01/payer/{stediId} \
  --header 'Authorization: <api-key>'

Every payer in the Stedi Payer Network has a Stedi Payer ID: an immutable payer ID you can use to route transactions to the payer in Stedi.

If you already have a payer’s Stedi Payer ID, this new endpoint is the fastest way to fetch their payer metadata. No filtering, no pagination. Just the one record.

The endpoint returns the same payer information as our existing JSON-based Payer API endpoints: payer ID, name, payer ID aliases, transaction support, enrollment requirements, and more. Just for a single payer.

Why we built this

Payer IDs are used to route healthcare transactions to the right payer. If the ID is wrong, the transaction fails.

We recently introduced Payer List and Payer Search API endpoints to let you retrieve payer IDs and other metadata programmatically. This ensures you can always get an accurate, up-to-date payer ID.

Since then, several customers have asked, “Is there a way to get a single payer without a search?”

Until now, you had to either:

• Use the Payer Search API endpoint, which always returns an array – even for exact matches.
  OR

• Fetch and paginate the full list of payers (thousands of records), then filter it client-side.

If you already had a Stedi Payer ID from a previous search or a saved mapping, there was no way to get just that payer’s metadata without a search or filter.

Now you can.

How it works

Make a GET request to the /payer/{stediId} endpoint. Pass the Stedi Payer ID as the {stediId} in the path:

curl --request GET \
  --url https://healthcare.us.stedi.com/2024-04-01/payer/HPQRS \
  --header 'Authorization: <api-key>'

You’ll get back a single JSON object that contains:

• The payer’s name, primary payer ID, and known payer ID aliases

• Whether the payer supports medical or dental coverage (or both)

• Supported transaction types

• Whether transaction enrollment is required for a transaction type

{
  "payer": {
    "stediId": "KRPCH",
    "displayName": "Blue Cross Blue Shield of Michigan",
    "primaryPayerId": "00710",
    "aliases": [
      "00210I",
      "00710",
      "00710D",
      "00710P",
      "1421",
      "2287",
      "2426",
      "710",
      "CBMI1",
      "MIBCSI",
      "MIBCSP",
      "SB710",
      "Z1380"
    ],
    "names": [
      "Blue Cross Blue Shield Michigan Dental",
      "Blue Cross Blue Shield Michigan Institutional",
      "Blue Cross Blue Shield Michigan Professional"
    ],
    "transactionSupport": {
      "eligibilityCheck": "SUPPORTED",
      "claimStatus": "SUPPORTED",
      "claimSubmission": "SUPPORTED",
      "professionalClaimSubmission": "SUPPORTED",
      "institutionalClaimSubmission": "SUPPORTED",
      "claimPayment": "ENROLLMENT_REQUIRED",
      "coordinationOfBenefits": "SUPPORTED",
      "dentalClaimSubmission": "NOT_SUPPORTED",
      "unsolicitedClaimAttachment": "NOT_SUPPORTED"
    },
    "enrollment": {
      "ptanRequired": false,
      "transactionEnrollmentProcesses": {
        "claimPayment": {
          "type": "ONE_CLICK"
        }
      }
    },
    "parentPayerGroupId": "AWOCR",
    "coverageTypes": [
      "medical"
    ]
  }
}

Try it out

The Retrieve Payer API endpoint is free on all paid Stedi plans.

To see how it works, check out the docs or reach out for a free trial.