Browse, validate and transform UN/EDIFACT messages using the Truugo API
Add EDIFACT capabilities to your processes and applications using the Truugo EDIFACT API.
Performs message validation which covers: message syntax, message structure (segment groups), and general content requirements (mandatory elements, length restrictions).
Helps especially software developers who need to transform in-house files to EDIFACT syntax.
Transforms EDIFACT message to XML format.
Helps an XML-aware application to process EDIFACT messages.
Example: EDIFACT » XML
Transforms EDIFACT message to JSON format.
Helps an JSON-aware application to process EDIFACT messages.
Returns the URL of a visualized EDIFACT message ("EDIFACT Browser" feature in Truugo portal).
Helps a help desk to solve message content issues more efficiently. EDIFACT Browser URL can be shared with trading partners as well.
Files are stored on the Truugo server for a user-defined period (5min...14d). EDIFACT Browser URL is secured with SSL connection and 32-char unique identifier (UID).
Example: Plain view » Grouped view
Transforms EDIFACT message into CSV documentation template. CSV can be formatted and completed with your comments in a spreadsheet application (Excel) and exported to PDF format.
Example: EDIFACT » CSV » PDF
The company receives EDIFACT messages just from a few trading partners. If the company has applications for JSON processing, the to-json API request helps to start processing EDIFACT messages immediately without additional applications.
API returns an EDIFACT message transformed into a clean and logically structured JSON message, which can be processed using any JSON-aware application.
BENEFITS: Start receiving EDIFACT messages with a shorter development time and lower costs.
The company needs to set up an EDIFACT integration/translator using in-house tools without strong EDIFACT experience. Using the check-syntax API request, developers can easily check that message syntax, structure, and default content requirements are fulfilled. For invalid messages, the get-browser API request provides a visualized view for browsing message content and locating content issues.
BENEFITS: Get faster EDIFACT implementation with lower costs.
The help desk needs to solve issues as quickly and cost-efficiently as possible. However, the 1st/2nd level support does not have the technical knowledge and tools to solve the EDIFACT-related issues. Thus those issues are forwarded to technical professionals, resulting in higher costs and longer response times.
The help desk gets instant information on whether a message contains general syntax issues using the check-syntax API request. As a result, responses get quicker, and only particular cases are forwarded to technical professionals. For invalid messages, the get-browser API request visualizes message contents, and the visualization can be easily shared with trading partners as a URL.
BENEFITS: Solve issues more efficiently and enhance customer satisfaction by quicker responses.
The company wants to inform a sender quickly and with descriptive notice when issues are detected in a message flow. The system can automatically generate a clear and detailed presentation of an invalid message using the get-browser API request. As a result, the browser URL can be attached to the notice to help the sender solve issues efficiently.
BENEFITS: Speed up error correction, enhance user experience and decrease help desk requests.
The company wants to enhance the quality of the EDIFACT documentation process to minimize the effort needed for integrations. An accurate and descriptive documentation layout can be generated for a message sample in no time using the get-documented-sample API request. API transforms a message sample into CSV, which can be formatted and exported to PDF using a spreadsheet application (Excel, OpenOffice, etc.).
BENEFITS: Save resources from both parties and enable shorter lead times by helping trading partners to integrate more efficiently.