The Stedi app now displays Destination webhook delivery attempts to help with testing and debugging. This page includes metadata about the delivery attempt, including the destination, the time of the attempted delivery, and detailed logs about each delivery stage.
To review delivery attempts, click a processed file or transaction, click any event to view its details page, and then go to the Destination attempts tab.
The following improvements make it easier to build and update Stedi mappings.
You can now view more context about Stedi guide segments and elements when you hover over them, allowing you to understand which part of the guide you are mapping more easily. This is especially helpful for large guides, including many X12 HIPAA guides, that repeat the same loop or segment in multiple locations.
You can now search within a mapping’s source or target fields for a specific text string and jump to each matching value. For example, you might search for the name of a specific segment or element.
Stedi can now validate and translate inbound EDI files containing multiple interchanges. The interchanges in the file must have the same partnership and direction (matching sender and receiver IDs).
You can now require all users to enable Multi-Factor Authentication (MFA) before accessing your Stedi account. To enforce MFA for all users:
Click the account name.
Select Account settings and toggle MFA to ON.
The next time each user logs into the account, Stedi prompts them to set up their MFA token. Once you enable MFA for a Stedi account, it cannot be disabled.
Connections and Destination webhooks now apply an automatic filter that displays the last hour of logs by default. You can remove or adjust this time filter as needed.
It’s now easier to build custom healthcare guides that conform to X12 HIPAA specifications. When creating a new guide, set the X12 Release to 5010 HIPAA. Stedi automatically preloads every HIPAA transaction set for you to choose as a base for customization.
Stedi guides are machine-readable versions of the EDI requirements trading partners typically provide as PDF, CSV, or Word documents. You can use Stedi’s guide builder to customize any X12 HIPAA transaction for your EDI integration. Then, you can make your guides public to share them with trading partners as user-friendly, interactive web pages.
The Generate EDI API now supports idempotent requests.
When you send a request to the Generate EDI API, you can include an idempotency key to prevent sending duplicate data to your trading partners. In the event of network errors or other intermittent failures, you can safely retry requests with the same idempotency key as many times as necessary within 24 hours after making the first request.
We made the following improvements to the Stedi app:
Execution metadata: You can now view file execution metadata, which includes the X12 Interchange and Functional Group values, along with other processing information. To view a file’s execution metadata, go to the Files page, click the file you want to view, and select Raw Metadata in the Results tab.
Event retries: You can now retrigger individual events from both the transaction details page and the file details page.
AS2 certificate validation: Stedi now gives you immediate feedback about errors in your local and partner signing and encryption certificates. For example, you will now receive an error when your certificate is improperly formatted, when a certificate doesn’t validate against a certificate chain, when a public and private key pair don’t match, and more.
We updated the authorization scheme in our API to better align with OpenAPI specifications.
The Authorization header no longer requires the Key prefix. Instead, you should now provide API keys directly (Authorization ${STEDI_API_KEY}). This change aligns with the OpenAPI standard and allows for out-of-the-box compatibility with OpenAPI tools and services.
Previously, our APIs required API keys to be passed with a Key prefix (Authorization: Key ${STEDI_API_KEY}), which required manual setup to work with OpenAPI. We will continue to support the previous format for backward compatibility, but we encourage you to adopt the new format to leverage the benefits of OpenAPI compliance.
You can now read and write EDI for X12 release 008050, the latest version approved in December 2023 and released in February 2024. Stedi now supports every release from 002001 (released in 1987) to present.
The 008050 release is supported throughout the entire Stedi platform. You can review every 008050 transaction set in EDI Reference, create PDF and machine-readable 008050 Stedi guides for your trading partners and EDI integrations, and process live 008050 transactions instantly.
Stedi Destinations now pre-fills the grant_type header for OAuth 2.0.
When you create or edit a Stedi Destination with OAuth 2.0 configured, the Header parameter grant_type is now pre-populated with client_credentials. This is the most common grant type used when the client is acting on its own behalf. You can change this value in the Advanced menu if you need to use a different grant type.
This change helps ensure that your OAuth 2.0 connections are set up correctly and securely, without extra manual configuration.
For more details on the OAuth 2.0 protocol, visit RFC 6749 section 4.4, which outlines the protocol for the client credentials grant.
You can now set a custom Interchange Version Control Number Code (ISA-12) for generated EDI files.
When you call the Generate EDI API, the outbound transaction setting ID you provide dictates which Stedi Guide will be used for validation and translation. By default, Stedi sets ISA-12 to be the X12 release number of the associated guide. However, some trading partners may require that you specify a different release for the transaction and the ISA envelope – for example, you might send a transaction from X12 release 003020 inside an ISA envelope with an Interchange Version Control Number Code of 00401.
Visit the Generate EDI docs for complete details about ISA and GS overrides.
You can now use Stedi to read and write any transaction set from all releases in the 1980s-era X12 Version 2:
002001 | Release year: 1987
002002 | Release year: 1988
002003 | Release year: 1988
002040 | Release year: 1989
With this update, Stedi now has complete coverage of all transaction sets across all releases from X12 002001 to X12 008040.
Stedi also now supports custom GS-08 Industry Identifier Codes for all X12 releases when reading and writing EDI.
Industry Identifier Codes are the 1-6 characters appended to the end of a release in the GS-08 element – for example, 005010**UCS** and 004010**VICS** or 005010**X279A1** in the X12 HIPAA standard. You can now define your own custom identifier for any transaction set as needed. Custom identifiers are helpful when trading with automotive OEMs such as Ford (which uses 002002**FORD**) and Chrysler (which uses 002040**CHRY**).
We consolidated the top navigation bar to make the Stedi app easier to use and understand.
The top navigation is now organized into three sections:
Files: Review, sort, filter, and inspect every file flowing through Stedi. This page was previously called File executions.
Transactions: Review, sort, filter, and inspect every EDI transaction flowing through Stedi.
Setup: Access all the tools and configurations required to onboard and manage trading partners. This menu includes Trading partners, Guides, Destinations, EDI settings, and Mappings (if applicable).
We also consolidated documentation and resources into a single menu and co-located key account admin pages, such as Account settings, under the account selection menu.
Stedi stores metadata about each successful file execution, such as the processing timestamp and X12 Interchange and Functional Group values. You can now retrieve this metadata through the following methods:
The file.processed.v2 event includes a metadata artifact with a document download URL you can use to fetch the execution metadata.
The Get Execution Metadata API returns a document download URL you can use to fetch the execution metadata.
You can now retrigger events for successfully processed files. This feature makes it easier to test your end-to-end integration – for example, triggering webhooks – without continually reprocessing the same files.
To retry an event:
Go to the Files page.
Click the name of the processed file.
Go to the Events tab.
Click the ellipses (...) next to an event and select Retry.
To make debugging easier, you can now set the log level for each Destination webhook. Destination webhooks allow you to send transaction data and events from Stedi to any external API.
You can edit the webhook to switch between the following log levels at any time:
OFF - no logs
ERROR - errors only
INFO - errors and select execution steps, such as successful deliveries
TRACE - all execution steps
To review a webhook’s logs, click its name and then go to the Logs tab.
You can now import pre-built EDI guides for your trading partners when creating transaction settings. Stedi has pre-built guides for hundreds of popular trading partners that you can use in your integration for free.
Stedi guides are a machine-readable version of the EDI requirements – sometimes called implementation guides – that your partner would typically provide as PDF, CSV, or Word documents. When you add a guide to a transaction setting, Stedi validates and translates (inbound files) or generates (outbound files) EDI according to the guide’s requirements.
When building a Stedi mapping for reading EDI, you can now switch between the sample files attached to the source guide. Sample files typically represent the use cases when you could receive that transaction set from your trading partner. For example, the X12 HIPAA 834 Benefit Enrollment and Maintenance guide includes samples for adding subscriber coverage, canceling a dependent, changing subscriber information, and more.
As you switch between samples, Mappings dynamically updates the source JSON shape and the expected mapping results, so you can ensure your mapping works for each use case.
The Mappings module is a powerful JSON-to-JSON transformation engine that helps you transform Guide JSON into and out of the shape you need for your business system. You can use Stedi’s visual mapper to build mappings for both inbound and outbound transactions.
You can now configure transaction.processed.v2 event bindings to trigger a Destination webhook based on the following new filters:
Connection: Inbound files from a specific connection. This option is useful when there are multiple connections within the same partnership. For example, you may set up a separate SFTP connection for test files and route them to a test endpoint.
Mode: The transaction contains a specific value in the ISA-15 element, which is used in X12 to distinguish between test and production files. This option is useful when you want to send test and production data to separate endpoints.
Destination webhooks allow you to automatically send data and events from Stedi to any external API. You can configure one or more event bindings that conditionally trigger each webhook. The new Connection and Mode filters are available under the Advanced menu.
