This functionality is available in a Stedi module. Contact us for details.

When to use Mappings
There are three ways you can transform Stedi transaction data (JSON) into a custom format: Stedi Mappings, writing custom code, and using an iPaaS platform. The approach you choose depends on your circumstances and preferences. Mappings may be a good fit for your business when:- Your system can natively produce and consume JSON payloads.
- You plan to do one-step transformations without multi-step processing.
- You want your business or operations team to manage mappings without engineering involvement.
- You want a solution that’s integrated with the Stedi platform.
Read EDI
The most common Mappings use case is transforming processed transaction data from Stedi into a custom JSON Schema for your business system. You can use webhooks to automatically send transaction processed events to any API endpoint. Then, you can use the Map Transaction Output endpoint to return the mapped output of the processed inbound transaction.Write EDI
You can also use Mappings to transform JSON from your business systems into the Guide JSON format required to Stedi’s API.Ingest Stedi events
You may want to transform Stedi events into a custom shape before sending them to your business system. For example, you may want to ingestfile.failed.v2
events into applications like Slack or Zapier to create internal alerts for your operations team.