Changelog

Control numbers are now deprecated for JSON eligibility and claim status APIs

The controlNumber request body field is now deprecated in the following JSON API endpoints:

The controlNumber field is now optional. We don't recommend specifying the controlNumber field in requests.

About interchange control numbers

In the underlying X12, an interchange control number is used by payers to detect duplicate transaction submissions. Many payers enforce strict uniqueness rules for interchange control numbers.

When you use Stedi's JSON APIs – like those above – Stedi generates valid, unique interchange control numbers when we translate your JSON API request to X12. We ignore the controlNumber field in the JSON request.

For more information, see our Control numbers in X12 EDI blog.

Introducing Stedi's Institutional Claims X12 API endpoint

You can now submit 837I institutional claims as X12 EDI using the Institutional Claims X12 API endpoint.

Most Stedi customers submit 837I claims using our JSON-based Institutional Claims endpoint. JSON is familiar and easy to work with. You can build an integration faster.

But if you already work with X12, converting to JSON wastes time. The new endpoint accepts X12 directly.

Previously, X12 submissions of 837I claims required SFTP. With SFTP, you have to wait for files to get errors or validation. With the API, you get instant responses. Development is faster, and debugging is easier.

For complete details, check out the Institutional Claims (837I) Raw X12 API reference.

Introducing Stedi apps and integrated accounts

Stedi integrated accounts and Stedi apps are now available. Together, this new set of capabilities allows end customers of Stedi’s Platform Partners to have Stedi accounts of their own.

Integrated accounts drastically reduce the amount of clearinghouse functionality that partners need to build themselves.

**Integrated accounts
**Integrated accounts are simplified Stedi accounts that are designed to be friendly to non-technical users. The more complex developer-focused functionality – such as configuring API access and webhooks, and viewing raw JSON payloads – has been removed.

**Stedi apps
**Integrated accounts can install Stedi apps, which are Stedi’s pre-built integrations to a growing list of third-party RCM, PMS, EHR, and other platforms.

Stedi apps allow providers to quickly connect their Stedi account to these external systems using preconfigured SFTP credentials and API keys.

They can also grant Stedi portal access for external support and implementation teams to assist with setup and ongoing support.

Learn more
See our announcement blog.

Correct and resubmit claims in the Stedi portal

You can now correct and resubmit claims directly from the transaction detail page of any claim in the Stedi portal.

We’ve also made other UI improvements that make the portal’s Claims section simpler and faster to use. Here’s what’s new:

Streamlined list views and filters on the Transactions and Files pages help you find what you need, fast.
Cleaner detail pages for transactions and files put the most important information front and center.

For more information, see our announcement blog.

Introducing real-time claim status checks in the Stedi portal

You can now run 276/277 real-time claim status checks in the Stedi portal.

You can submit a claim status check using the Stedi portal’s new Create claim status check page. You can access the page by clicking Claims > New claim status in the portal’s nav.

Previously, you could only run these checks using Stedi’s Real-Time Claim Status API.

For more information, check out the announcement blog.

Introducing enrollment document download

You can now download documents for a transaction enrollment request directly from its details page in the Stedi portal. This includes documents signed by Stedi on your behalf if you use delegated signature authority.

For more information, see our documentation.

Stedi Agent is now available in sandbox accounts and test mode

You can now use the Stedi Agent in sandbox accounts and test mode.

In sandbox accounts and test mode, you run predefined mock eligibility requests that return realistic responses. The Stedi Agent is the Stedi portal’s built-in AI assistant. It helps you recover failed eligibility checks.

Previously, you could only use the Stedi Agent for failed eligibility checks in production. Now, you can try the agent out in sandbox accounts and test mode using a predefined mock check.

For more information, check out the announcement blog.

Introducing new filters for the List Enrollments and List Providers endpoints

You can now filter results more precisely in the List Enrollments and List Providers API endpoints.

We’ve also updated the Enrollments page and Providers page in the Stedi portal to surface these filters.

List Enrollments endpoint

We’ve added new query parameters to the List Enrollments endpoint. You can use the parameters to filter by:

Partial term: filter lets you search across multiple fields at once.
Status: Filter by one or more enrollment statuses—such as DRAFT, SUBMITTED, PROVISIONING, LIVE, CANCELED, or REJECTED.
Provider details: Filter by NPI (providerNpis), tax ID (providerTaxIds), or name (providerNames).
Payer: Filter by payer IDs (payerIds).
Source: Limit results by how the enrollment was created: API, UI, or IMPORT.
Transaction type: Filter by transaction types, like eligibilityCheck, claimStatus, or claimSubmission.
Date: Filter enrollments by when they were created (createdFrom, createdTo) or when their status last changed (statusUpdatedFrom, statusUpdatedTo).
Import ID: If an enrollment was created through CSV import, filter by the returned importId.

Several of these query parameters accept arrays. You can include an array parameter more than once in the URL to filter by multiple values.

List Providers endpoint

The List Providers endpoint now accepts a filter parameter for searching by provider name, NPI, or tax ID. Filtering is case-insensitive and supports partial matches.

Updated filters in the Stedi portal

Alongside API improvements, we’ve updated the Stedi portal to surface these new filters on the Enrollments page and Providers page.

On the Enrollments page:

On the Providers page:

Introducing the Stedi Agent

Now available in the Stedi portal, the Stedi Agent brings AI-powered automation to healthcare clearinghouse workflows, beginning with eligibility check recovery.

Use the Stedi Agent to recover failed eligibility checks. If a check fails with a known recoverable error, a Resolve with Stedi Agent option appears next to the related search. The agent runs in Debug view, where you can watch it work – step by step, in real time.

For more information, see our announcement blog.

Introducing enriched BCBS eligibility responses

Stedi now enriches most Blue Cross Blue Shield (BCBS) eligibility responses by automatically including the member’s home payer name and primary payer ID whenever possible.

This info appears in a related benefitsInformation.benefitsRelatedEntities entry in our JSON eligibility responses and in a 2120C or 2120D loop in X12 responses.

For more information, see our announcement blog.