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.

User interface depicting EDI transaction settings
Stedi supports 300+ transaction types across retail, supply chain, transportation, logistics, healthcare, finance, and more.

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.

Supported file exchange methods
User interface depicting EDI transaction settings

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 ->

Diagram of an inbound 850 Purchase Order
Diagram of an inbound 850 Purchase Order
  1. 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.
  2. 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.
  3. The JSON transaction is sent to your API endpoint.
    An HTTP request with the outputted transaction is automatically sent to your system for ingestion.

Complete your integration

Connect Stedi to your business applications

Stedi translates EDI to and from a JSON shape that reflects the original transaction. To ingest processed transactions or call Stedi’s Generate EDI API, you need to transform Stedi’s JSON shape to and from a format your system can understand.

  • ~

    Stedi Mappings

    Build JSON transformations with an intuitive visual mapper that integrates seamlessly with the Stedi platform.

    Mappings docs

  • ~

    iPaaS platforms

    Use the built-in functionality in platforms like Workato and to transform JSON.

  • ~

    Code on your infrastructure

    Build data transformations and complex business logic within your own codebase.

Example mapping

Start building

Contact the onboarding team to discuss a plan that includes hands-on support designing, building, and testing your first integration.

Contact the onboarding teamCreate your first account

Build EDI integrations fast, without being an EDI expert

Start building
  1. Twitter
  2. GitHub
Backed by
AdditionBloomberg BetaFirst RoundStripeUSV
Customer AgreementService TermsPrivacy Notice

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.