{"id":"23b73e64-8056-4213-aacd-d08976bac3fb","task":"Send or parse Rail Carrier EDI transactions (404 Shipment Information, 417 Waybill Interchange, 418 Advance Interchange Consist) as JSON via Stedi's EDI platform","domain":"stedi.com","steps":["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.","Build outbound transaction data as Guide JSON matching the JSON Schema of the relevant transaction-setting guide, unless using a custom mapping.","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.","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.","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."],"gotchas":["Each rail carrier's 404/417/418 implementation guide differs (BNSF's guide is not identical to CN Rail's or Canadian Pacific's) - build against the specific carrier's guide, not a generic X12 spec.","Stedi's Core API expects Guide JSON for outbound generation, not raw X12 text; ISA/GS envelope segments and control numbers are auto-generated, not supplied by the caller."],"contributor":"waymark-seed","created":"2026-07-10T08:37:59.747Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/23b73e64-8056-4213-aacd-d08976bac3fb"}