How Stedi works
Build end-to-end EDI integrations quickly, without being an EDI expert.
Configure your integration
Set up a full integration with Stedi Core.
Define partner relationships
Create partnerships between you and each trading partner. Define which transaction types you'll exchange and how to validate, read, and write files.
Use pre-built guides from the Stedi Network, which includes guides for hundreds of popular trading partners. We add any requested guide in 1-2 days.
Set up partner file exchange
For each partnership, create one or more connections to securely exchange files with your trading partner.
Inbound EDI files from your partner are processed immediately, and generated EDI is delivered to your partner automatically.
Use Stedi’s turn-key FTP and AS2, or connect to remote FTP servers.
Integrate using Webhooks and APIs
Virtually every aspect of Stedi is accessible via API, but only two simple integration points are necessary to build a fully-functioning system.
Receiving EDI: Configure Destination webhooks to automatically deliver inbound transactions and other events to any API endpoint (e.g. post 850 Purchase Orders to your own API and any errors to Slack).
Sending EDI: Use the Generate API to create and deliver EDI files according to your or your partner’s requirements, complete with auto-generated envelopes and control numbers.
A real-world example
Receiving an X12 850 Purchase Order ->
- Your trading partner sends you an 850 Purchase Order over SFTP.
Stedi automatically monitors the connection and processes files as they arrive in real-time. - The 850 Purchase Order is translated to JSON.
When the 850 file arrives, the file is validated and translated to JSON. Both the raw file and the translated JSON are available in the UI for inspection. - The JSON transaction is sent to your API endpoint.
An HTTP request with the outputted transaction is automatically sent to your system for ingestion.
Build custom middleware
Extend your integration with Stedi Cloud.
Functions
Run custom logicStedi Functions allowing you to react to Core processing events, integrate Stedi with external systems, and define functionality to fulfill any requirement. For example, you may want to transform and enhance 810 invoices before writing them to your ERP system.
Extend functions with:
Mappings
Transform dataBuild a mapping definition quickly in the UI and then use the API to transform JSON data into and out of the shape you need for internal systems and ERPs.
Buckets
Unlimited file storageStore any type of data, including EDI documents, on Stedi. All data you store is encrypted in transit and at rest.
Stash
Scalable key/value storageStash is a key-value store. You can use Stash to configure where you want to send data and even manage data feeds, like inventory or price catalogs.
Start building
Contact the onboarding team to discuss a plan that includes hands-on support designing, building, and testing your first integration.