Complete the following steps to configure an test your first EDI integration on Stedi.
Visit our EDI Essentials documentation to learn about EDI standards and transaction structure, including the types of and usage for segments and elements.
Configure your first trading partner
Time: About 15 minutes
To set up a new trading partner, you’ll need to configure the following settings:
- Partnership: Partnerships describe all aspects of the EDI relationship between you and your trading partner, including which transaction sets you plan to exchange and other important information for processing.
- Connections: Within the partnership, define SFTP/FTP/FTPS and AS2 connections to exchange data with partners.
- Transaction settings: Within the partnership, define the inbound and outbound transaction sets you plan to exchange with your trading partner. As part of this process, you’ll choose which EDI specifications to use to validate the data.
Send webhooks to your system
Time: About 5 minutes
Each time Stedi processes an EDI file from a trading partner, you will want to send the transactions to your downstream system. You can do this by configuring a Destination webhook to send the Guide JSON to your API, Cloud functions, IPaaS platforms, or ERP systems.
You can also configure webhooks for other events, like when a processing error occurs. You can use this approach to trigger alerts in systems like Slack, PagerDuty, or Zendesk for further review.
Process an inbound test file
Time: About 2 minutes
Once you have configured your first trading partner and a Destination webhook, you can process a test file to make sure your partner configuration is working correctly. If you don’t want to wait for a test file from your partner, you can also generate a test file.
When the test file is successfully processed, you will receive a webhook to your Destination URL for each included transaction. The webhook contains a JSON payload with metadata as well as the actual transaction.
Send an outbound test file
Time: About 10 minutes
You can send a test file to your partner from within the browser.
This is also useful for understanding what data is required to call the Generate API programmatically from your system. You can export cURL commands to use as a starting point for your live integration.
Configure data transformations
Time: A few hours
To complete your integration, choose a method to transform Stedi Guide JSON into and out of the format your internal systems can understand.