The EDI Dev Toolkit

Translate EDI inside your applications

X12, HIPAA, EDIFACT, HL7 and six more EDI standards become typed .NET objects or structured JSON - in your process, on your hardware, at a flat yearly price with zero per-document fees. Validate, split, merge and acknowledge in the same toolkit.

Validate EDI Files Free

Free forever on the Community plan, $179 a year when you ship. No credit card required. See the plans.

.NET
Native
Cloud
EDI JSON

License.SetSerial("YOUR_SERIAL_KEY");
var edi = File.OpenRead(@"C:\837P_Claim.txt");
using (var reader = new X12Reader(edi, "EdiFabric.Templates.Hipaa"))
{
    var claims = (await reader.ReadToEndAsync()).OfType<TS837P>();
    foreach (var claim in claims)
    {
        if (claim.IsValid(out MessageErrorContext errors))
            Console.WriteLine(claim.ST.TransactionSetControlNumber_02);
        else
            Console.WriteLine(string.Join("\n", errors.Flatten()));
    }
}

                                     See Examples
                                    X12
                                    EDIFACT
                                    HL7
                                    NCPDP
                                    SCRIPT
                                    VDA
                                    Flat File
                                
import json
import edifabric_x12 as ef

serial = "YOUR_SERIAL_KEY"
ef.load_library()
ef.set_serial(serial)
ef.set_map(json.dumps({"default": serial, "maps": {}}))

edi = open("837P_Claim.txt", "rb").read()
output, offset = ef.parse(edi, ef.ParseMode.JSON_VALIDATE)
report = json.loads(output[offset:])
if report["errors_count"] == 0:
    print(output[:offset])
else:
    print(report["errors"])
                                     See Examples
                                    PYTHON
                                    C
                                    JAVA
                                    C#
                                
curl -L -X POST 'https://api.edination.com/v2/x12/read' \
-H 'Ocp-Apim-Subscription-Key: YOUR_SUBSCRIPTION_KEY' \
-H 'Content-Type: application/octet-stream' \
--data-binary '@/C:/purchase-order.edi'

                                     See Examples
                                    EDI JSON
                                    Validate EDI
                                    X12 999
                                    EDIFACT CONTRL
                                
{
  "ST": {
    "TransactionSetIdentifierCode_01": "837",
    "TransactionSetControlNumber_02": "000000001",
    "ImplementationConventionPreference_03": "005010X222A1"
  },
  "BHT_BeginningOfHierarchicalTransaction": {
    "HierarchicalStructureCode_01": "0019",
    "TransactionSetPurposeCode_02": "00",
  },
  "AllNM1": {
    "Loop1000A": {
      "NM1_SubmitterName": {
        "EntityIdentifierCode_01": "41",
        "EntityTypeQualifier_02": "2",
      },
      "PER_SubmitterEDIContactInformation": [
        {
          "ContactFunctionCode_01": "IC",
          "ResponseContactName_02": "JERRY",
        }
...
                                    Named JSON fields
                                    EDI JSON
                                    Try in EdiNation
                                

Ten EDI standards, from X12 and HIPAA to EDIFACT, HL7 and NCPDP

ediFabric .NET covers all ten plus custom flat files, ediFabric Native brings X12 and HIPAA to any language on Windows, Linux and macOS, and ediFabric Cloud exposes the lot over REST, hosted or self-hosted. Every plan includes all three.

EDI and JSON

Translate between EDI data and structured JSON, both ways. Built-in splitting and merging of large files, with automatic trailer generation.

More EDI translation →

Validate EDI Data

Check the file against its spec, including HIPAA 5010 and 4010. SNIP levels 1–4 set how far the check goes. Failures come back in an error report.

More EDI validation →

Adjust EDI Specs

Partner-specific formats as OpenEDI, SEF, or JSON templates, or attributes on the .NET class, with required elements, code sets, and custom rules.

More custom EDI specs →

EDI Acks

Generate the partner receipt from the validation result: X12 999, 997, and TA1, or an EDIFACT CONTRL acknowledgment.

More EDI acks →

View All EDI Standards

Three runtimes. One plan.

ediFabric .NET and ediFabric Native run inside your own application, so EDI files and PHI never leave your network. ediFabric Cloud is a REST API: the version we host receives your files, or you can self-host the same API on your own infrastructure when the data has to stay put. Every plan includes all three, so you choose the runtime that fits your architecture.

ediFabric .NET

Fully managed C# library for .NET Core and .NET Framework, installed as a NuGet package. Translates between EDI and typed .NET objects. Covers all ten EDI standards, custom flat files and Entity Framework mapping.

ediFabric Native

One native library per platform (Windows, Linux, macOS), callable over a C ABI from C, C++, Rust, Go, Python, Node.js, Java and .NET. Translates EDI to structured JSON. X12 and HIPAA today, more standards to follow.

ediFabric Cloud

REST API for all 10 EDI standards - call it from any language, with nothing to install. Translates EDI to structured JSON. Hosted by us, or self-hosted on your own infrastructure when data must stay in your network.

Structured JSON that APIs and AI can work with

Partner files arrive as positional EDI. Everything downstream - REST clients, validators, and language models - works better when that data is named JSON that follows a published schema.

Named, structured JSON

Every loop, segment and element becomes a named field. Map, query, store, and round-trip the same payload without writing an EDI parser. Keep EDI in the same contract-first workflow as the rest of your APIs.

A published specification

The shape of the JSON is documented in the open OpenEDI specification, so the format is a stable, documented contract. Generate clients and validate requests.

Read the OpenEDI spec →

Better input for models

Every field carries its EDI name and position, so a model reads a field such as TransactionSetControlNumber_02 by name. Validate whatever it produces against the same templates before it reaches a trading partner.

Explore the EDI Specs

Start free. Upgrade when you ship.

Three plans, and each one includes ediFabric .NET, ediFabric Native and ediFabric Cloud. The plans differ in scale and support.

Community

$ 0 /forever

Evaluate, learn and prototype. 250 operations a day, three leased seats, and it never expires.

Developer Popular

$ 179 /year

See What's Included

For individual developers and small teams. Production use in one environment you own, unlimited local operations, three leased seats, and service bureau on those hosts.

Enterprise

$ 799 /year

See What's Included

For company-wide use at scale. Unlimited seats and full offline mode for air-gapped environments.

Working with PHI or under SOC 2? ediFabric .NET and ediFabric Native run entirely inside your own application, so your EDI data never leaves your network. Self-host the Cloud API for the same guarantee. The Cloud API we host receives your files, so it is not HIPAA or SOC compliant.

Compare the Plans Compare the Products