AWS B2B Data Interchange automates the transformation between Electronic Interchange Data (EDI) documents and JSON or XML formats, to simplify your downstream data integrations.
-
Inbound EDI: the AWS customer receives an EDI file from their trading partner. AWS B2B Data Interchange converts this EDI file into a JSON or XML file with a service-defined structure. A mapping template provided by the customer, in JSONata or XSLT format, is optionally applied to this file to produce a JSON or XML file with the structure the customer requires.
-
Outbound EDI: the AWS customer has a JSON or XML file containing data that they wish to use in an EDI file. A mapping template, provided by the customer (in either JSONata or XSLT format) is applied to this file to generate a JSON or XML file in the service-defined structure. This file is then converted to an EDI file.
Businesses use EDI documents to exchange transactional data with trading partners, such as suppliers and end customers, using standardized formats such as X12, EDIFACT, or HL7v2. Currently, AWS B2B Data Interchange only supports X12 to JSON or XML conversions.
The following sections document the AWS B2B Data Interchange API service calls, data types, parameters, and errors.
This API interface reference for AWS B2B Data Interchange contains documentation for a programming interface that you can use to manage AWS B2B Data Interchange. The reference structure is as follows:
-
For the alphabetical list of API actions, see Actions.
-
For the alphabetical list of data types, see Data Types.
-
For a list of common query parameters, see Common Parameters.
-
For descriptions of the error codes, see Common Errors.
Tip
Rather than actually running a command in the AWS Command Line Interface, you can use the
--generate-cli-skeleton parameter with any API call to generate and
display a parameter template. You can then use the generated template to customize and
use as input on a later command. For details, see Generate and use a parameter skeleton file.
