Similar to working with transactions from platforms like Stripe or Shopify, you need to transform Stedi’s Guide JSON format to and from a format that your system can understand.
You need to do these transformations for both inbound (from your trading partner) and outbound (to your trading partner) transactions.
After processing an inbound file from your trading partner, Stedi can use Destination webhooks to send the data to your business systems. By default, this webhook includes standardized metadata about the processing event along with the actual EDI transaction represented in Guide JSON.
Prior to ingesting the payload into your system, you can use one of the following transformation approaches to reshape it into your system’s format.
- Stedi Mappings: Configure the webhook to deliver the transaction data directly to your API. Add a mapping to transform the transaction into your system’s forma before delivery.
- Custom code: Configure the webhook to deliver the transaction to your system as-is. Your transformation code will map that payload into your system’s format and deliver it to the ultimate destination.
- iPaaS platform: Configure the webhook to trigger a workflow run. The workflow should transform the Guide JSON into your system’s format and then use a pre-built or custom connector to deliver the transformed payload to your system.
For outbound transactions, you need to call the Generate EDI API with a Guide JSON payload. For example, you may need to translate employee records exported from your internal database into Guide JSON to create an 834 Benefit Enrollment file.
You can use one of the following transformation approaches to transform data from your system into Stedi’s Guide JSON format.
- Custom code: Transform your system’s data into Guide JSON and call the Generate API directly.
- Stedi Mappings: First, call the Mappings API from your codebase to transform your system’s data into Guide JSON. Then, call the Generate API with the transformed payload.
- iPaaS platform You can use the iPaaS platform’s built-in functionality to map your system’s data into Guide JSON, and then use the iPaaS platform’s pre-built HTTP connector to call the Generate API with the transformed payload.