There's a battle taking place right now between EDI companies over the future of the industry in the context of artificial intelligence. Which companies have earned the right to advertise agentic EDI? To answer this question, we need a framework.
Paste an X12 document to view it decoded, with one segment per line annotated with human-readable information and checked against the X12 standard. Also available in the terminal as tedi edi inspect.
We've rolled out optimized SFTP connection infrastructure, direct AS2 connections route inbound messages by ISA identity when several partners share them, and a batch of smaller changes.
You can now resend a past outbound document from its EDI transaction page, with the original ISA, GS and ST control numbers intact, without regenerating the EDI or creating a second transaction.
Tediware now matches your partners' 997 acknowledgments back to the documents you sent, with a new column and filter on EDI Transactions and a new API endpoint for querying the transaction log.
As more people use coding agents, the experience that those agents are having is increasingly important. I've designed something novel: an API for those agents to send me their ideas and suggestions as they work with Tediware.
One click builds a complete working trading partner (Walmart or Petco) with a connection, mappings, flows, and seeded documents, so you can run a real inbound and outbound exchange and then take it apart to see how it works.
A new "Generate" action proposes the JSON shape your own system should emit for an outbound mapping based on your CSV, SQL schema, list of column names, or nothing at all.
A sandbox webhook delivers to an in-app sink, so you can inspect a real delivery and watch signature verification before you stand up an endpoint of your own.
When you fetch a processing result from the platform Results API, each step lists the files it produced as `artifacts`. Until now, those artifacts told you only whether a file was the `input` or the `output` of the step - not what kind of file it was. Every artifact now includes a `contentType`, the file's MIME type, so you can select a file by what it is rather than inferring its format from the processing direction.
