Changelog

Auto-generate EDI Translate API calls from any Stedi guide

EDI Translate uses Stedi guides to read, validate, and generate EDI according to partner-specific requirements. When you call EDI Translate APIs, you must provide your Stedi API key for authorization and either the EDI document (reading) or JSON document (writing EDI).

The guide builder now auto-generates sample EDI Translate API calls for reading and writing EDI. Click Actions > Get Translate API snippet to copy sample calls for several languages, including cURL, HTTP, and Python.

The sample API calls include valid test EDI or JSON data based on the guide's specifications. The guide builder auto-generates generic test data, but you can also get test data from an attached sample EDI file.

Bootstrap module now supports polling FTP/SFTP servers

The Stedi bootstrap repository lets you quickly deploy a reference implementation that sends and receives EDI documents, connecting Stedi products in an end-to-end flow.

The bootstrap implementation now supports polling remote FTP / SFTP servers for new files. When the poller finds files, it copies them to a Stedi bucket and optionally deletes those files from the remote server. You can configure the bootstrap module to process these files automatically. Visit the bootstrap external poller README for more details.

Book time with our technical team for help deploying the bootstrap repository to your Stedi account and customizing it for your use case.

View connected Stedi guide for any mapping on the list view

Building a Stedi mapping requires defining a source and target JSON schema. You can generate these schemas automatically by connecting the mapping to an existing Stedi guide.

Now, the Mappings UI shows you which mapping source or target schemas are connected to Stedi guides and links directly to the connected guide. This new view helps you understand how many mappings are linked to Stedi guides and which mappings are affected by specific guide changes.

Enable payload validation for transformed JSON documents in Mappings API

Stedi Mappings let you transform JSON documents from one structure to another. By default, the Mappings API does not apply any payload validation on the /map endpoint. Now, you can enable Strict validation mode to validate the input and the output payload of the mapping operation. Validation helps you ensure that the mapping results are accurate and catch deviations from expected results early. To apply strict validation, set the validation_mode query parameter to strict. Mappings uses the source schema to validate the input document and the target schema to validate the outgoing document. If validation of the input or output payload fails, the response is a 400 error with the validation_failed code and validation_errors object.

HTTP/1.1 400 Content-Type: application/json { "code": "validation_failed", "message": "The input of the mapping does not conform to the specified source JSON Schema, and the output of the mapping does not conform to the specified target JSON Schema.", "validation_errors": { "source": { "mapping_input": { "quantity": 15, "unit_price": 2.50 }, "errors": [ { "code": "required", "message": "must have required property 'unit_description'", "json_pointer": "/", "json_schema_pointer": "#/required" } ] }, "target": { "mapping_output": { "total": 37.50 }, "errors": [ { "code": "type", "message": "must be integer", "json_pointer": "/total", "json_schema_pointer": "#/properties/total/type" } ] } } }

Add a description to validated samples in Stedi guides

You can include multiple EDI sample files in Stedi guides to help new trading partners understand valid usage patterns faster and reduce onboarding time.

Now, you can add a description to each sample that gives trading partners even more context about the intended use cases. The description appears at the top of the guide’s EDI Inspector.

This feature is available both for Public Guides and for Stedi guides published privately. View descriptions for samples in the YRC Freight X12 Motor Carrier Bill of Lading.

Mappings UI Improvements

Stedi mappings let you transform JSON data from one shape to another, most importantly between your internal schema and EDI-like JSON required for EDI Translate. We launched the following improvements to the Mapping builder UI:

• When you connect a Stedi guide to the mapping’s source or target schema, the Guide tab links directly to the connected guide.

• The Schema and Example tabs are now read-only when a guide is connected. This prevents you and collaborators from manually editing the schema out of sync with the connected guide.

• You can use the View menu to show and hide the source and output columns as needed.

Change the industry identifier for X12 HIPAA guides

The industry identifier for an EDI transaction set is specified in characters 7-12 of the GS-08 element of the functional group header.

You can now change the industry identifier when building a custom Stedi guide for an X12 HIPAA transaction set. You can build a custom guide by importing an X12 HIPAA public guide into your account. EDI Translate uses the industry identifier you choose when generating EDI documents according to your guide's specifications.

Use underscore as a delimiter in Stedi guides

Delimiters separate the segments and elements in an EDI file. When you create a Stedi guide, you can choose the delimiters that the EDI Translate API should use when writing EDI.

Now, you can choose underscore as the delimiter option in Stedi guides.

EDI samples are now included in Stedi guide PDFs

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.

Announcing X12 HIPAA guides

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.

Quickly update mapping source and target schemas from connected Stedi guides

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.

Download validated EDI files from EDI Inspector

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.

Build a new mapping directly from a Stedi guide

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.

Guide builder: Add multiple codes and built-in support for standard ISO currency codes

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.

Guide builder: More easily specify when to use segment and loop variants

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.

EDI Inspector 'Format' option now prompts auto-adjustments for malformed ISA header

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.

Stedi achieves SOC 2 Type II compliance

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.

Stedi completes external audit for HIPAA eligibility: Ensuring the protection and confidentiality of patient data

We are excited to announce that Stedi has successfully passed an external audit and our products have been certified as HIPAA eligible. This certification means that our products have undergone rigorous testing and have been deemed compliant with HIPAA regulations.

We understand that HIPAA eligibility is important for our customers in the healthcare industry as it ensures their sensitive patient data and protected health information (PHI) will be safe and kept confidential when using Stedi products. This is critical when you are exchanging health information such as claims, eligibility, and enrollment information with your partners.

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 and documents, or contact us with any compliance questions related to your business case.

Bootstrap: Configure a simple, end-to-end EDI workflow

Stedi creates building blocks for custom, end-to-end EDI integrations. Now, our bootstrap repository lets you quickly configure and run a sample implementation that reads and writes EDI documents from your Stedi account.

The bootstrap implementation uses the following steps to handle inbound EDI:

1. You add EDI documents to a Stedi Bucket.

2. New EDI documents automatically invoke a Stedi Function that processes this data payload.

3. The function calls the EDI Translate API to transform the EDI data into JSON. The transformation requires a Stedi Guide to map EDI fields to JSON fields.

4. The function sends the JSON document to a webhook.

The bootstrap implementation has a similar workflow for generating outbound EDI. Your EDI flows may differ from these simple examples, but the bootstrap is an excellent starting point for your first integration. We encourage you to Contact us as you get started with Stedi, so our team can help you customize the bootstrap workflow for your use case.

Stedi EDI Forum: Connect with the EDI community

EDI is really hard. We’re here to help!

Introducing the Stedi EDI Forum: A public resource for sharing EDI questions, complaints, and ideas with Stedi experts and the EDI community. You can also use it to provide feedback about Stedi products.

Everyone can view the forum for free, and you can create a free Stedi account to contribute.