Document & download EDI specifications

In addition to having all standard and custom EDI models represented in our free OpenAPI format, EdiNation lets you to automatically document EDI transactions in a similar layout as the original X12 or EDIFACT implementation guidelines. Documenting EDI specifications produces syntax-neutral and human-readable text format that analysts and developers can quickly utilize for mapping, sharing, or to track changes.

Document EDI models

Automatically generate documentation for all standard or custom EDI transactions in human-readable text format, resembling how X12 and EDIFACT implementation guides are distributed.

Add notes or edit the final content as you wish, and document single or multiple EDI transactions alike.

Learn more

Share EDI models

The documentation format visually depicts the nested structure of segments and loops for each transaction, then lists out all segments, and finally, the EDI codes.

Copy or download the documentation as a text file and distribute it amongst your team or partners.

Learn more

Common questions about EDI documentation

Do I need to use documentation?

No, you can programmatically use OpenAPI format to also document your EDI transaction. The documentation feature targets non-developers used to a certain representation of the EDI guidelines.

Can I configure the output?

Yes, once the documentation is displayed in the model dialog, you can modify it directly in the editor or download it and edit it as a simple text file.

Why some segments have no name?

Segment name is displayed for segment properties where the referenced schema name is defined as {text1}_{text2}, and the name of the segment is the value in {text2}, just after the underscore. For example, "BHT_BeginningOfHierarchicalTransaction_8" will have "BeginningOfHierarchicalTransaction" as a name, but "BHT" will have its name blank.

Scroll to top