Changelog

Required fields are marked with a red asterisk. For example, in the form, the insured's First and Last name is required.

We’ve redesigned the benefits table for eligibility responses in the Stedi portal to make it faster and easier to read a patient’s benefits.

Benefits are now grouped by health plan. Each plan begins with its general limitations, followed by benefit details. The benefit details are organized by the Service Type Codes (STCs) and procedure codes from the payer’s response.

If present, benefits for STC 30 (Health Benefit Plan Coverage) and STC 35 (Dental Care) – the baseline STCs for medical and dental care – appear first.

The table displays information from the benefitsInformation objects in Stedi’s JSON Eligibility API responses.

Filter benefits

You can filter the table to quickly find benefits for a specific service, procedure, or coverage type – like a deductible or limitation. You can also filter by overage level and whether the benefit applies to in-network or out-of-network services.

For example, you can filter the table to only show individual deductibles for STC 3 (Consultation).

The table displays information from the benefitsInformation objects in Stedi’s JSON Eligibility API responses.

For more information, see our announcement blog.

The Batch Eligibility Check API endpoint now supports up to 10,000 eligibility checks in a single request. Previously, the limit was 1,000 checks per request.

For more information, see our announcement blog.

The Stedi Payer Network now displays logos for select payers.

The Payer Network is Stedi's online payer list. The site lets you browse and search Stedi's supported payers for payer IDs, supported transaction types, and transaction enrollment requirements.

Logos make it easier to confirm you’ve found the right payer while browsing or searching.

The payer’s logo also appears on its detail page.

Logos in the Payers API
Stedi’s Payers API now returns the URL for a payer’s logo, when available. You can use the URLs to fetch payer logos for use in your own applications and interfaces.

The logo URL appears in the payer.avatarUrl field of the API response. The field is available for the Search Payer, List Payer, and Retrieve Payer endpoints.

Example:

{
"payer": {
  "displayName": "Cigna",
  "primaryPayerId": "62308",
  "avatarUrl": "https://prod-payer-avatars.payers.us.stedi.com/HGJLR/avatar.png?v=1761841671464",
  ...
}