Validate EDI files Last updated: 2026-11-03
Validate EDI resources with the HTTP POST Method
In order to validate EDI documents according to the implementation guide for each standard and version use the following resources with the POST method:
You can validate EDI transactions for the following EDI standards. To do so, execute HTTP POST to the resource URL, with the request body being the relevant EdiNation resource.
X12
The request body must be an X12Interchange. Execute HTTP POST to the resource URL, with the request included as application/json content.
- URL:
https://api.edination.com/v2/x12/validate - Header:
Ocp-Apim-Subscription-Key: {API key} - Request: X12Interchange
- Response: OperationDetails
The response will contain validation details, encoded in application/json format.
The URL above is for API v2, which accepts JSON only. API v3 supports X12 only for now. On v3, use Parse X12 in mode 2, with a raw X12 file as the request body:
curl -X POST "https://api.edination.com/v3/x12/parse?mode=2" \
-H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
-H "Content-Type: application/octet-stream" \
-D headers.txt -o response.bin \
--data-binary @purchase-order.ediTo validate an X12Interchange on v3, first convert it to an X12 file with Build X12. The response is the X12Interchange JSON followed by the validation report, split at the offset in the X-EdiFabric-Offset header.
EDIFACT
The request body must be an EdifactInterchange. Execute HTTP POST to the resource URL, with the request included as application/json content.
- URL:
https://api.edination.com/v2/edifact/validate - Header:
Ocp-Apim-Subscription-Key: {API key} - Request: EdifactInterchange
- Response: OperationDetails
The response will contain validation details, encoded in application/json format.
HL7
The request body must be an Hl7Interchange. Execute HTTP POST to the resource URL, with the request included as application/json content.
- URL:
https://api.edination.com/v2/hl7/validate - Header:
Ocp-Apim-Subscription-Key: {API key} - Request: Hl7Interchange
- Response: OperationDetails
The response will contain validation details, encoded in application/json format.
VDA
The request body must be an FlatMessage. Execute HTTP POST to the resource URL, with the request included as application/json content.
- URL:
https://api.edination.com/v2/vda/validate - Header:
Ocp-Apim-Subscription-Key: {API key} - Request: FlatMessage
- Response: OperationDetails
The response will contain validation details, encoded in application/json format.
NCPDP
The request body must be an NcpdpTransmission. Execute HTTP POST to the resource URL, with the request included as application/json content.
- URL:
https://api.edination.com/v2/ncpdp/validate - Header:
Ocp-Apim-Subscription-Key: {API key} - Request: NcpdpTransmission
- Response: OperationDetails
The response will contain validation details, encoded in application/json format.
Example with Postman:

