The same EDI engine, delivered as a hosted REST API

Translate, validate and acknowledge EDI files over HTTPS. Your EDI data is processed on our servers, so use a self-hosted API when you are working with PHI.

EDI to JSON and back

POST an EDI file and get structured JSON back, or POST JSON and get valid EDI. Transactions are transposed according to their configurable specifications.

Custom OpenEDI models

Switch between public specifications and your own partner-specific models. Community uses public models; Developer and Enterprise add private ones.

Our cloud, or self-hosted

Want the REST API but not hosted in our cloud? Build the same API with ediFabric Native and run it on AWS, Azure or your own rack. Every plan includes Native.

Nothing to install

Any language that can call a REST API, can call ediFabric Cloud. No NuGet package, no native library, no runtime on the machine that sends the request.

Validation

Validate messages against public or private OpenEDI models and get a detailed error report before the file ever reaches a trading partner.

Acknowledgments

Generate TA1, 997 or 999 for X12, and CONTRL for EDIFACT, including batched 997/999 and configurable technical acknowledgments.

Translate EDI to JSON in a few lines

The same three operations — read, write, validate — for every supported standard. Swap x12 for edifact, hl7 or ncpdp.

                            Read
                        

                            Write
                        

                            Validate
                        
curl -L -X POST 'https://api.edination.com/v2/x12/read' \
-H 'Ocp-Apim-Subscription-Key: YOUR_KEY' \
-H 'Content-Type: text/plain' \
--data-binary '@/C:/purchase-order.edi'

                                 API reference
                                X12
                                EDIFACT
                                HL7
                                NCPDP
                            
curl -L -X POST 'https://api.edination.com/v2/x12/write' \
-H 'Ocp-Apim-Subscription-Key: YOUR_KEY' \
-H 'Content-Type: application/json' \
--data-binary '@/C:/purchase-order.json'

                                 API reference
                                X12
                                EDIFACT
                                HL7
                            
curl -L -X POST 'https://api.edination.com/v2/x12/validate' \
-H 'Ocp-Apim-Subscription-Key: YOUR_KEY' \
-H 'Content-Type: application/json' \
--data-binary '@/C:/purchase-order.json'

                                 API reference
                                X12
                                EDIFACT
                                HL7
                            

Self-host the same API

Keep the REST shape, keep EDI data inside your network. Worked examples for AWS, Azure and ASP.NET — the libraries are already in every plan.

AWS Lambda

Build an in-house EDI API as a Lambda behind API Gateway.

Read the AWS how-to

Azure Function

The same API, hosted as an Azure Function.

Read the Azure how-to

ASP.NET Core

Run it as a regular ASP.NET Core service.

Read the ASP.NET how-to

All self-hosting how-tos

You do not buy ediFabric Cloud on its own

Every plan includes ediFabric .NET, ediFabric Native and ediFabric Cloud. Pick Cloud because a REST call suits your stack, not because of what it costs.

Included in every plan

Free forever to start

Community costs nothing and never expires, giving you 250 operations a day across .NET, Native and Cloud combined. Developer includes 3,000 Cloud operations a month, Enterprise 25,000.

All ten standards

Same coverage as .NET

EDIFACT, EANCOM, X12, HIPAA, IAIABC, NCPDP, HL7, VDA, EDIGAS and IATA. Files up to 3 MB. Your plan never limits which standards you get.

EDI data is uploaded

Not HIPAA or SOC compliant

All EDI data is transported to our service, so hosted Cloud is not suitable for PHI. Use .NET or Native, or self-host the same API with the libraries already in your plan.

Compare the Plans Compare the Products

A REST API that translates EDI to structured JSON