Transforming data
Similar to working with a platform like Stripe or Shopify, you will likely need to transform Stedi transactions to and from a format that your system can understand.
Inbound transactions
After processing an inbound transaction from your trading partner, Stedi can send a webhook to each configured Destination URL. This webhook includes standardized metadata and the actual EDI transaction represented in Guide JSON, a JSON format that reflects the structure of the original EDI transaction. Many integrations require transforming this Guide JSON into a format that your system can consume.
Outbound transactions
When you send an outbound transaction to your partner, you will likely need to transform your system’s data into Stedi’s Guide JSON format before calling the Generate API. This process is similar to the transformation you would need to do when calling Stripe or Shopify’s API.
Ways to transform data
Stedi supports three ways to transform transaction data, depending on your circumstances and preferences.
Stedi Mappings or Functions
This route is best if you want to keep all of your business logic in one place.
This functionality is available on Cloud and Enterprise plans.
- Mappings provides a visual interface for building JSON-to-JSON transformations. You can use it to transform data from Stedi’s JSON format into your system’s JSON format, or vice versa.
- Functions is a serverless compute service (like AWS Lambda) that lets you run code on Stedi’s infrastructure. If a transformation or operation is too complicated to handle purely within a mapping, you can write and deploy a function to handle it.
iPaaS platforms like Zapier, Workato, or Tray.io
This route is best if you already have an iPaaS system in place and want to continue to use it to encapsulate your business logic.
These platforms can ingest the Guide JSON payload from Stedi and transform it into your system’s format using a visual interface. They can also transform your system’s data into Stedi’s JSON format before calling the Generate API.
Code running on your infrastructure
This route is best if you prefer to manage all of the data transformations and business logic within your own codebase.
You can consume webhooks from Stedi and make API calls to the Generate API. Stedi’s webhooks can send data to any URL using Basic, OAuth, or API Key authorization, or directly to a cloud function like AWS Lambda, Google Cloud Functions, or Azure Functions.
Was this page helpful?