Once you configure a trading partner, Stedi automatically parses and validates inbound EDI files in real time.
Generate test files in the browser
You can generate and process inbound test files to simulate receiving a file from your trading partner. This can be useful for testing your downstream integration, since the inbound file will trigger any configured webhook.
To generate and send an inbound test file:
Do one of the following:
Click Test inbound.
Select a Partnership and an Inbound transaction setting.
Edit the Transaction payload to include realistic or actual data from your system. The payload editor validates your data as you change it.
- If the guide associated with this transaction setting has sample files, you can choose a Sample and load its data into the editor.
Click Ingest file.
Inbound processing flow
Stedi automatically processes all new files that arrive over a partnership’s connections.
When a new EDI file arrives over a connection, Stedi automatically:
- Confirms that the information in the file’s
ISAheaders matches the corresponding partnership. If not, the file will error, and you can retry after creating the required configuration.
- Identifies all available transaction sets in the file and validates them against the transaction settings for the partnership, either using the specified guide or the base X12 specification.
- Translates the EDI transaction into Guide JSON, using the JSON Schema defined by the guide.
- Persists the original EDI file and the Guide JSON for review and retrieval. Files are retained for 10 years.
- Displays the transaction set data in the UI for inspection.
Send transactions to destinations
Stedi can deliver transactions and other events to any API endpoint using a Destination webhook. For example, you can configure a destination that automatically sends inbound transactions to an API endpoint, or you can configure a destination that sends a notification to a ticketing system when a file fails to parse.
transaction.processed.v2 event contains a URL that you can use to fetch processed transaction data from Stedi.
Transforming Guide JSON
Stedi’s native format is Guide JSON, a JSON format that closely reflects the structure of an EDI transaction. You will likely need to transform Guide JSON into a format your system can understand and ingest.
Visit Transformation approaches for details.
Large file support
If you need to process EDI files over 50 MB in size, we recommend using the Large file processing module.
The module also includes Fragments, which allow you to split processed transactions from Stedi into smaller chunks for downstream ingestion.
Other file types
Stedi can also route non-EDI formats like CSV, JSON, and XML for further processing. When a non-EDI file arrives, the file will appear in the UI, and Stedi will emit an event that contains a summary of the file execution. This event can be used to trigger additional processing.
How Stedi processes non-EDI files depends on the file extension:
- Stedi emits a
file.processed.v2event for all files with
- Stedi attempts to process any other file extension, such as .
.edi, as EDI. If parsing fails, it attempts to parse the file first as JSON and then as CSV. If parsing still fails, it will mark the execution as failed and emit a
file.failed.v2event, which can be used to trigger additional processing.
Stedi can process EDI files that are gigabytes in size, and there is no hard restriction on the maximum file size you can attempt to process. If you run into issues processing a large file, please reach out and our engineers will help remove any limitations that you’re encountering.