Translate EDI resources with the HTTP POST Method
In order to translate from EDI or translate to EDI use the following resources with the POST method:
-
Read EDI file into JSON
You can read two resources, X12 files and EDIFACT files/streams. To do so, execute HTTP POST to the resource URL, with the request body being the file to translate included as either binary or form-data content.
-
- URL:
https://api.edination.com/v2/x12/read
- Header:
Ocp-Apim-Subscription-Key: {API key}
- Request: X12 file as
binary
- Response: Array of X12Interchange
- URL:
-
- URL:
https://api.edination.com/v2/edifact/read
- Header:
Ocp-Apim-Subscription-Key: {API key}
- Request: EDIFACT file as
binary
- Response: Array of EdifactInterchange
- URL:
The response will contain an array of EDI interchanges, encoded in
application/json
format.Example with Postman:
-
-
Write JSON to EDI file
Again, you can write out two resources, X12 and EDIFACT. Execute HTTP POST to the resource URL, the request body must contain a single EDI interchange, included as application/json content.
-
- URL:
https://api.edination.com/v2/x12/write
- Header:
Ocp-Apim-Subscription-Key: {API key}
- Request: X12Interchange
- Response: X12 file as
application/octet-stream
- URL:
-
- URL:
https://api.edination.com/v2/edifact/write
- Header:
Ocp-Apim-Subscription-Key: {API key}
- Request: EdifactInterchange
- Response: EDIFACT file as
application/octet-stream
- URL:
The response will contain an EDI interchange, encoded in
application/octet-stream
format.Example with Postman:
-
Comments
0 comments
Please sign in to leave a comment.