Changelog

Never miss a new feature - Follow Stedi on Twitter and LinkedIn

March 28, 2024

Send and monitor real-time eligibility checks in the Stedi app

From the Eligibility menu in the Stedi app, you can now perform the following actions:

Submit manual eligibility checks and review the full 271 JSON response. This feature is useful for testing and for operations teams who need to do one-off checks.

Review errors for every eligibility check you send through the Stedi API and the app. You can filter by payer or timeframe (last hour, last day, or last week) and view details about each error code.


View destination attempts from the event details page

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.



Require Multi-factor Authentication for your account

You can now require all users to enable Multi-Factor Authentication (MFA) before accessing your Stedi account. To enforce MFA for all users:

  1. Click the account name.
  2. 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.


Mappings UX improvements

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.



X12 HIPAA guides preloaded into Stedi guide builder

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 from the Stedi Network 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.


Idempotency for Generate EDI API

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. Learn more.


Stedi app UX improvements

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.


New HIPAA guides in the Stedi Network

You can now find the following X12 HIPAA guides in the Stedi Network:

The Stedi Network is a free and open catalog of Stedi guides for hundreds of popular trading partners. You can import any X12 HIPAA guide into your account for free and use it in your EDI integration. 

Request guides: If you don’t see your partner’s guides in the Stedi Network, submit a request, and we’ll build the guides you need for free in 1-2 business days.


Authorization Header update

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.


Support for new X12 release 008050

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.


Pre-filled settings for OAuth 2.0 Destination webhooks

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.


Custom Interchange Version Control Number Code

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.


Support for additional X12 releases and custom GS identifier codes

You can now use Stedi to read and write any transaction set from all releases in the 1980s-era X12 Version 2:

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, 005010UCS and 004010VICS or 005010X279A1 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 002002FORD) and Chrysler (which uses 002040CHRY).


Improved Stedi app navigation

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.


Retrieve file execution metadata

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:


Retry individual events without reprocessing a file

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:

  1. Go to the Files page.
  2. Click the name of the processed file.
  3. Go to the Events tab.
  4. Click the ellipses (...) next to an event and select Retry.

X12 HIPAA 999 Implementation Acknowledgment added to the Stedi Network

The HIPAA 999 Implementation Acknowledgment is now available in the Stedi Network’s collection of X12 HIPAA guides. 

The Stedi Network is a free and open catalog of Stedi guides for hundreds of popular trading partners. Stedi guides are a machine-readable format for EDI requirements that Stedi uses to automatically validate, translate, and generate EDI according to trading partner’s requirements.

You can import the 999 into your account for free and add it to transaction settings for your EDI integration. 

Request guides: If you don’t see your partner’s guides in the Stedi Network, submit a request, and we’ll build the guides you need for free in 1-2 business days.


Set the log level for Destination webhooks

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.


Test your mapping for multiple use cases

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.


Import guides when creating transaction settings

You can now import your trading partner’s EDI guides directly from the Stedi Network when creating transaction settings. The Stedi Network 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. 

Request guides: If you don’t see your partner’s guides in the Stedi Network, submit a request and we’ll build the guides you need for free in 1-2 business days.


Trigger Destination webhooks based on connection and data mode

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.




Send transformed file processed events to your API

You can now use Mappings to automatically transform file.processed.v2 events into a custom JSON shape. You can then attach the mapping to a Destination webhook to automatically forward transformed event data to your API.

For every successful file execution, Stedi emits a file.processed.v2 event that includes information about when Stedi processed the file, the associated partnership configuration, the file size, and more.

Visit the Events documentation for complete details.


Create Stedi mappings faster

Stedi Mappings is our powerful JSON-to-JSON transformation engine. We recently made the following major improvements to the visual mapping tool:

  • The visual mapper now shows warnings when the expected mapping output does not match the target JSON Schema. These warnings highlight issues such as invalid value types and missing properties to help you more easily create a complete, accurate mapping.
  • We added a quickstart workflow that makes it easier to create new mappings. You can choose a quickstart for reading EDI (mapping transactions from Stedi to a custom shape for your API), writing EDI (mapping JSON from your system to the shape required for Stedi’s Generate API), and ingesting Stedi events (for example, mapping `file.failed.v2` events to a custom shape).
  • To help you keep mappings up-to-date, we added clearer notifications when a connected Stedi guide has changed (for example, it has new segments or elements) and provided instructions for pulling those changes into your mapping.
The new Stedi mappings quickstart options

View Destination webhook logs

You can now view detailed logs for each Destination webhook and filter them by a specific date range. The logs provide details about how the webhook is functioning, such as when each webhook is triggered and the response from the configured endpoint, which can help you troubleshoot issues. 

Destination webhooks allow you to send transaction data and events from Stedi to any external API. To view the logs for a destination, click its name to go to its details page, and then navigate to the Logs tab.


Customize the filename for autogenerated acknowledgments

You can now set a custom filename for autogenerated acknowledgments to comply with your trading partner’s requirements.

Stedi can automatically generate a 997 Functional Acknowledgment or a 999 Implementation Acknowledgment for each inbound transaction and deliver it to a specified connection.

To set a custom filename, navigate to the partnership, turn on the Acknowledgments functionality, and enter a JSONata expression into the Filename expression field. For example, the expression "EDI997_" & $millis()would produce filenames that start with EDI997 and then contain a timestamp, such as EDI997-5182341242.edi.


Filter inbound files from Remote SFTP/FTPS connections

You can now specify a regex expression for Stedi to use when retrieving files from a Remote SFTP/FTPS connection. When polling the remote server, Stedi only processes files that match the filter pattern.

For example, your trading partner may place files for multiple different entities on the remote server, with different prefixes for each entity. In this case, you could write a regex expression that matches only files with a given prefix.

You can specify a Filter pattern for the remote poller in the connection’s Inbound settings.


Send transformed file failed events to your API

You can now use Stedi mappings to automatically transform file.failed.v2 events into a custom shape before sending them to external APIs.

Stedi emits file.failed.v2 events when it cannot parse an inbound EDI file, or it cannot deliver an outbound EDI file to the configured connection. You may want to automatically send these events to an external platform like Slack or Jira, so your team can receive alerts and monitor issue resolution.

You can now create a Stedi mapping to transform the file.failed.v2 event JSON into the shape your external systems can receive and ingest. Then, you can attach the mapping to a Destination webhook to automatically forward the transformed event data to your API.


Add attachments to Stedi guides

You can now attach files to any Stedi guide and choose whether the attachments are public or private (only available to members of your Stedi account). 

Stedi guides are a machine-readable representation of the EDI specifications that your trading partners provide to you or that you provide to your trading partners. Attachments provide additional information about the guide. 

For example, you may want to add private attachments that help your team debug issues in your EDI pipeline, such as the original PDF specifications or a changelog. For a public guide, you may want to attach an appendix with a supplementary code list or a diagram that helps your partners understand the messaging flow.

To add attachments to a guide in your account, navigate to its Overview page, scroll to the Attachments section, and click Attach file.


Destination webhooks now support OAuth 2.0

You can now use OAuth 2.0 with Destination webhooks

Destination webhooks allow you to send transaction data and events from Stedi to any external API. To configure a destination webhook, you first create an auth configuration that defines how to authenticate with a set of URL endpoints. 

The OAuth 2.0 configuration includes setting the Authorization endpoint and parameters, the HTTP method, a client ID, and a client secret. You can create a new OAuth 2.0 configuration from the Event Destinations page.


Automatically process inbound TA1 Interchange Acknowledgments

Your trading partner may send you TA1 Interchange Acknowledgments in response to outbound EDI files.

Stedi now automatically processes inbound TA1s and displays the data in the File executions and Transactions pages for inspection.

You can also set the acknowledgmentRequestedCode outbound EDI files to request interchange acknowledgments from your trading partner. Visit the Generate EDI docs for details.

TA1s indicate receipt of an interchange and identify any errors in the interchange's envelope (ISA and IEA) information.


Automatically delete artifacts after a set time period

Stedi accounts on the Enterprise plan can now set an automatic data removal time frame in Stedi.

Artifacts refer to the transaction and file execution payloads from files Stedi has processed. They contain the actual input/output transaction data in EDI, JSON, or another format. You may want Stedi to remove artifacts after a certain time frame - for example, to comply with your company's PII/PHI retention policies.

Once you set a retention period, Stedi deletes artifacts after the retention window has passed. This affects both existing and future data in your account.

For example, if you set a retention period of 30 days and process a file today, Stedi will delete the artifact after 30 total days have elapsed. Stedi will also delete any artifact created more than 30 days prior. For more details on how artifact retention works, please visit the docs.You can set an automatic data removal time frame from the Settings page.


Generate inbound test files from your browser

You can now generate and send inbound test files to simulate receiving a file from your trading partner. This is useful for testing your downstream integration, since the inbound file will trigger configured destination webhooks.

To generate an inbound test file:

  1. Go to the File executions page or navigate into a partnership and click Test inbound.
  2. Select a partnership and an Inbound transaction setting.
  3. Autogenerate the test file from a sample EDI file in the guide or paste your own test data into the editor.
  4. Click Ingest file.

Stedi immediately processes the generated file and triggers any configured webhooks. You can review the results on the File Executions and Transactions pages.


Improvements to Stedi AS2

Stedi provides fully-managed AS2 connections that take care of the intricacies of AS2 and scale automatically to meet your demand. We recently made the following improvements:

  • We added extensive conditional validation to reduce common configuration errors.
  • You can now view and filter provisioning logs for each AS2 connection. These logs detail each step to create or update the connection, such as provisioning the certificates, making it easier to diagnose errors. To view provisioning logs, go to the partnership associated with the connection, and then click the connection to view its details page.
  • When creating or updating an AS2 connection, Stedi now clearly indicates when there are previously uploaded encryption and signing certificates and provides the option to update them. Previously, adding or updating certificates was a separate workflow.


Improvements to Stedi AS2

Stedi provides fully-managed AS2 connections that take care of the intricacies of AS2 and scale automatically to meet your demand. We recently made the following improvements:

  • We added extensive conditional validation to reduce common configuration errors.
  • You can now view and filter provisioning logs for each AS2 connection. These logs detail each step to create or update the connection, such as provisioning the certificates, making it easier to diagnose errors. To view provisioning logs, go to the partnership associated with the connection, and then click the connection to view its details page.
  • When creating or updating an AS2 connection, Stedi now clearly indicates when there are previously uploaded encryption and signing certificates and provides the option to update them. Previously, adding or updating certificates was a separate workflow.


Introducing Fragments: Split large transaction payloads

Stedi accounts on the Enterprise plan can now use fragments to split large transaction payloads from Stedi into smaller, more manageable chunks for downstream processing.

Large EDI files are often the result of transaction sets containing many repeated loops or segments. For example, a company may receive an 837 Health Care Claim file containing many insurance claims, or a retailer may receive an 846 Inventory Inquiry/Advice file containing millions of SKUs. To avoid overloading downstream systems, you can enable fragments on the repeated EDI segment.

Once enabled, Stedi splits the transaction payload into chunks based on that segment.For example, you might enable fragments on the LIN loop (list of inventory items) in an 846 Inventory Inquiry/Advice. For each processed 846, Stedi will emit fragment.processed.v2 events that each contain a chunk of LIN loop iterations.

You can create destination webhooks to automatically send fragment data to your downstream systems, or you can use the API to request the fragments for each processed transaction.


Introducing Sandbox mode

You can now create a free Sandbox account to evaluate Stedi.

Sandbox accounts are permanently free for testing purposes. They include all the features you need to demo and test an end-to-end EDI integration, including:

  • Translating any X12 EDI transaction to JSON
  • Generating EDI files in-app or through the API
  • Importing and editing guides from our Network
  • Testing webhooks
  • Reviewing, debugging, and retrying transactions.

You can also create Stedi-hosted SFTP/FTPS connections to test sending EDI. In order to exchange live files with your trading partner, you'll need to upgrade to a paid plan. You can upgrade your Sandbox account at any time to one of our flat-rate, monthly pricing plans.


Guide builder now shows warnings for missing ID element codes

Stedi's guide builder now shows warnings when an ID element does not specify the set of allowed codes. You can see which fields are missing ID codes and specify the allowed values from the provided list or supply your custom codes.

Code warnings are available to help improve the quality of your guides, and you can ignore them without affecting Stedi's ability to use the guide for EDI processing. Warnings only appear for ID fields where the X12 specification includes the allowed code values. For example, they will not appear for State or Province codes.

Why element codes are important

ID element codes are a powerful component of the X12 EDI specification to provide additional information about data fields and reference well-known values. For example, you can use ID codes to specify the currency code of a monetary value, the meaning of a date value, or the reason for a shipment delay.

Many elements offer 1,000 or more possible codes, but most trading partners only expect to use just one or a few of these values. If a guide does not indicate which codes are accepted, trading partners often have to engage in costly follow-up with EDI departments or conduct multiple rounds of testing as they discover more code values in use.

The new warnings in Stedi's guide builder help ensure you and your trading partners work with the most accurate EDI specifications on the market.

Warnings in guide builder

Pre-built guides: Instead of building guides from scratch, you can find hundreds of free guides for popular trading partners in the Stedi Network.


Add a mapping to destination webhooks

You can now add a mapping to destination webhooks to automatically transform transactions before delivering them to external APIs.Stedi parses EDI files into Guide JSON, which reflects the structure of an EDI transaction in a modern format. You can use a mapping to transform Guide JSON into the shape required by your internal systems and business applications. Mappings provide a visual interface for building JSON-to-JSON transformations and are available in the Cloud and Enterprise plans.

To add a mapping to a destination webhook:

  1. Use the mappings editor to create a transformation for the transaction.processed.v2 event. Visit the mappings documentation for instructions.
  2. Select the mapping in the Mapping menu when creating a transaction.processed.v2 event binding. Visit the webhooks documentation for complete instructions.

Import partnership details from the Stedi Network

You can now create partnerships faster by importing guides from the Stedi Network.

Partnerships contain transaction settings that define the EDI transaction sets you plan to exchange with that trading partner. For each transaction setting, you specify the EDI guide Stedi should use to validate data. The Stedi Network has pre-built guides for hundreds of popular trading partners that you can use in your integrations.

To import a partnership from the Stedi Network, go to the Trading partners page, click Create partnership, and choose Import from network. Visit the partnerships documentation for step-by-step instructions.

If you can't find your partner or guide in the network, you can submit a request, and we'll build it for you for free within 1-2 business days.


Role-based access control for Enterprise plans

Stedi accounts on the Enterprise pricing plan can now use role-based access control (RBAC) to ensure only authorized users can access and modify account resources.

Admins can assign account members to one of four roles:

  • Admin: These users can access and modify all resources within a Stedi account. This includes adding and removing members, assigning member roles, adding billing information, switching between pricing plans, configuring Partnerships, generating EDI files, and configuring resources like Mappings and Functions.
  • Developer: These users can access and configure all resources, such as Partnerships, Mappings, and Functions.
  • Operator: These users can access and configure Partnerships, Guides, and Mappings. They can interact with developer resources like Functions, but cannot modify them. For example, they can invoke existing Stedi functions, but cannot change them or add new functions.
  • Read-only: These users can view account resources, but cannot modify them. For example, they can review processed transactions in Stedi's interface but cannot call the Generate EDI API or edit partnership details.

To change a member's role, go to Settings > Members in your account. Click the pencil icon for a member, choose a Role from the list, and click Update role.


Automatically generate 999s

You can now enable automatic 999 Implementation Acknowledgments for any Stedi partnership.

When you enable 999 acknowledgments for a partnership, Stedi automatically generates a 999 acknowledgment per functionality group of every valid inbound EDI file and delivers the 999s to your trading partner using the specified connection.

You will only use 999 acknowledgments in response to healthcare transactions. It's likely you should use 999s if you receive these transaction sets:

Each generated acknowledgment includes ISA and GS envelopes, complete with auto-incremented control numbers. Visit the partnerships documentation for more details.


Stedi guides EDI Inspector autogenerates envelopes for EDI test files

The EDI Inspector in Stedi guides can now autogenerate an envelope for any sample EDI file.

If the EDI test file in the editor does not contain an envelope, the EDI Inspector displays a Generate envelope button that you can use to instantly create a generic envelope for the transaction set. You can then edit the envelope with information for you and your trading partner.Stedi guides are a machine-readable format for EDI specifications that Stedi uses to translate inbound EDI files and generate outbound EDI files according to your and your trading partners' requirements. You can use the EDI Inspector in each guide to validate EDI test files according to the guide's specifications. You can start from sample files attached to the guide or add your own test file into the editor.Check out the Stedi Network, which includes Stedi guides for hundreds of popular trading partners. You can import any guide into your Stedi account to use in your EDI integrations.


Set max concurrent executions for Stedi Functions

You can now set the maximum number of concurrent executions for any Stedi function to avoid overloading downstream services and ensure that the function can scale up as needed.

Concurrency refers to the number of in-flight requests your function is handling at the same time. With the new concurrency controls, you can set the maximum number of executions that a given function can execute simultaneously. Generally, you would set this to a number that your downstream system can comfortably support.

In addition to limiting the number of concurrent requests, concurrency controls help ensure that you always have available capacity for a given function within your Stedi account. All functions within a Stedi account share an overall concurrency limit that can be raised upon request. When you set a concurrency limit for a specific function, you reserve a part of the overall account "budget" for that function. This approach ensures that you can scale up to the reserved level, even if other functions are experiencing a high load. Visit the functions documentation for more details.

To use this feature, go to the Functions UI, click the function you want to edit, and set the Max concurrent executions.


EDIFACT support in EDI Inspector

We are excited to announce that our EDI Inspector can now validate EDIFACT EDI files. All EDIFACT releases D96A and later are supported.

The EDI Inspector instantly recognizes any X12 or EDIFACT EDI file and validates its content against the corresponding EDI standard. You can view the transaction data on an easy-to-read UI, and identify and fix errors, such as incorrect codes and formats, missing or misplaced segments, and more.

EDIFACT integration preview: Soon, you'll be able to configure an EDIFACT integration on Stedi to exchange EDIFACT files with your partners. Contact us to get added to the preview launch.


Enable Static IP address for your Remote FTP connections

You can now configure your Remote FTP connections to use a static source IP address when exchanging EDI files with your trading partners.

Enabling a Static IP address ensures that your Remote FTP connections always use the same source IP address when communicating with the remote server. This may be required if one or more of your trading partners need to add your IP address to an allowlist to enable access.

You can enable a static IP address for your Remote FTP connections from the Core settings UI.


Create and send test EDI files from your browser

You can now generate and send test files to your trading partner from your browser.

To send a test EDI file from within a partnership, you can open the menu next to any outbound transaction setting and click Send EDI. You can also access this feature from the File Executions page.Stedi can autogenerate the input transaction payload (JSON) from any sample EDI file in the guide. You can modify this payload or paste your data into the editor. You can send the file from the browser or get the (HTTP) Generate API syntax for that payload. If you send the file, Stedi delivers the outbound test file to the connection, and you can review the results on the File Executions and Transactions pages.

Learn more about configuring new trading partners in our documentation.

Stedi
System status
+1 332-378-5040
About
PlatformPricingDocumentationCustomers
Backed by
AdditionBloomberg BetaFirst RoundStripeUSV
228 Park Ave S, PMB 58460, New York, NY 10003, USA
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.