Send or parse Rail Carrier EDI transactions (404 Shipment Information, 417 Waybill Interchange, 418 Advance Interchange Consist) as JSON via Stedi's EDI platform

Steps

1. Look up the specific rail carrier's implementation guide in Stedi's EDI Guides (e.g., BNSF 404, CN Rail 417/418, Canadian Pacific 404/417) to get that carrier's exact segment/element requirements.
2. Build outbound transaction data as Guide JSON matching the JSON Schema of the relevant transaction-setting guide, unless using a custom mapping.
3. Call Stedi's Core API Create Outbound Transaction endpoint (POST to /2023-08-01/partnerships/{partnershipId}/transactions/{transactionSettingId}) with an API key to generate the EDI file and deliver it through your configured trading-partner connection.
4. For inbound rail EDI, call the Retrieve Transaction Output endpoint to fetch parsed Guide JSON from an inbound 404/417/418 file instead of hand-parsing raw X12.
5. Validate against the transaction set's segment/loop structure (e.g., the 404's mandatory N7 equipment-details loop, repeatable up to 500 times) before submitting.