Stedi guides let you view and share EDI specifications as interactive web pages with built-in X12 EDI validation. You can also download Stedi guides as high-quality PDFs.
EDI samples attached to the guide are now included in the downloaded PDF.
The guide builder automatically validates new sample files against the guide specifications, so you can be sure that the sample matches the specification before sharing the PDF with your trading partners.
We are excited to announce the availability of Stedi’s X12 HIPAA guides, a free catalog of X12 HIPAA specifications that make it easier to understand, test, and translate healthcare EDI.
Browse interactive specifications for each transaction set, view sample transactions, and even validate EDI files in real time in your browser. Import any X12 HIPAA guide directly into your Stedi account and customize it to fit your integration use case. You can use Stedi's EDI Translate APIs to programmatically validate against any X12 HIPAA guides as well as parse and generate X12 EDI that conforms to the specifications.
Stedi guides and EDI Translate convert data between EDI and EDI-like JSON. Stedi mappings transform data between EDI-like JSON and a custom JSON shape that reflects your internal data model.
Each mapping has a source schema and a target schema, which you can define based on a Stedi guide or a sample JSON file.
Now, the mappings UI automatically detects changes in connected Stedi guides and lets you pull those changes into the schema. When you change the schema, the mappings UI alerts you when the updates affect existing expressions in the mapping.
Stedi EDI Inspector instantly recognizes data from any X12 EDI file and validates it against the standard to catch errors such as incorrect codes and formats, missing or misplaced segments, and more. Each Stedi Guide has a built-in EDI Inspector that validates files against partner-specific EDI specifications. Now, you can download validated EDI files.
Try the EDI Inspector on Walmart's 204 Motor Carrier Load Tender. Visit the EDI Guide Catalog for public guides from many trading partners, including Amazon, FedEx, Walmart, Trader Joe's, and more.
The first step toward building an EDI integration with Stedi is to create a Stedi guide from your partner's PDF implementation guide. Now, you can skip this step and directly import any guide from our EDI Guide Catalog into your Stedi account to integrate faster.
The EDI Guide Catalog is an open directory of our most-requested guides, and we continue adding more. You can view these guides as interactive EDI specifications and validate test files right in your browser. You can also request new guides, and we'll add them to the catalog.
A Stedi mapping lets you transform data into any JSON shape you want. Now, you can create a mapping directly from a Stedi guide for EDI reading or writing use cases.
Mappings are useful when you want to transform data to or from EDI-like JSON. For example, you may need to transform data from the guide JSON format that EDI Translate understands into a custom shape for internal systems. EDI Translate uses guides to quickly and accurately convert data between EDI and JSON. The JSON shape for both input and output closely matches the shape of the incoming or outgoing EDI.
We're constantly simplifying the guide builder experience. Instead of adding allowed values one-by-one for code (Identifier) elements, you can now provide a comma separated list of all the values you want to allow.
For the Currency Code, you can now select from a dropdown of standard ISO codes. This minimizes the chances of errors in the specification from entering an invalid code.
You may want to allow multiple variants of a segment or loop in your EDI specifications. For example, you could specify that partners include two N1 Name loops in each 850 purchase order: one for the ship to contact and another for the bill to party.
The guide builder UI now lets you select a discriminant element that has unique values for each variant. The discriminant tells the guide’s EDI Inspector and the EDI Translate API when one variant should be used over the other for validating, generating, or parsing EDI documents.
In the 850 purchase order example, you’d add the Entity Identifier Code as the discriminant for N1 Name loops. For the bill to variant, you’d use the BT qualifier, and for the ship to variant, you’d use the ST qualifier.
Formatting a malformed EDI file can be painful, especially if you are new to EDI or when you are troubleshooting a problem. This is why we originally introduced the 'Format' option on the EDI Inspector to make EDI content easier to navigate.
We noticed that EDI samples enclosed in PDF implementation guides almost always have incorrect whitespace padding within the ISA header. A customer needs to manually correct these to get to a valid EDI even if the rest of the EDI document is valid. Starting today, the format action detects the whitespace issues within the ISA header, and recommends one-click fixes to quickly get to a valid EDI. Try it out on a sample guide today.
We are excited to announce that Stedi has received SOC 2 Type II compliance certification. This certification demonstrates our commitment to maintaining the highest standards of security, availability, and confidentiality for our customers’ data.
SOC 2 Type II certification is a rigorous and comprehensive evaluation process that assesses a company’s internal controls and security practices to protect customers’ sensitive information. We will continue to undergo independent audits at regular intervals to verify our compliance.
This certification is just one of the many ways in which Stedi is fortifying its platform to handle customer data safely and securely. Visit our trust page for more information on our security and compliance policies, or contact us with any compliance questions related to your business case.