Pre-launch — your 10 free credits are reserved for launch day. Join the waitlist
converters · free tool

EDI to JSON

Turn an X12 or EDIFACT file into JSON — the shape you map from.

Runs in your browser — your data never leaves it

Paste, type, or drop a file. Runs as you type.

Output appears here as you type.

Worked example

Input
ST*850*0001~BEG*00*SA*PO123**20260101~N1*BT*NORTHWIND SUPPLY CO.~PO1*1*2*EA*9.99*CP*BP*SKU-1~CTT*1~SE*6*0001~
Output
{
  "@_standard": "X12",
  "@_code": "850",
  "@_name": "Purchase Order",
  "Header": {
    "Number": "PO123",
    "Date": "20260101",
    "Purpose": "00",
    "Currency": ""
  },
  "Parties": {
    "Party": [
      {
        "@_code": "BT",
        "Role": "Bill-to",
        "Name": "NORTHWIND SUPPLY CO.",
        "Id": "",
        "City": "",
        "State": ""
      }
    ]
  },
  "LineItems": {
    "LineItem": [
      {
        "@_line": "1",
        "Quantity": "2",
        "Unit": "EA",
        "Price": "9.99",
        "ProductIds": {
          "ProductId": [
            {
              "@_qualifier": "BP",
              "#text": "SKU-1"
            }
          ]
        }
      }
    ]
  },
  "Dates": {
    "Date": []
  },
  "References": {
    "Reference": []
  }
}

This example is one of EDI to JSON's test cases — if the tool stopped producing this output, the build would fail.

Questions

Why JSON instead of XML?
JSON is the shape most mapping tools and scripts want. If you're writing a Groovy mapping or a transformation, this is the structure you code against.
Are qualifiers resolved or left as codes?
Both. Codes are preserved verbatim (they're the data), and party roles are resolved to their meaning so you can read the file without a code table open.

Related tools