EDI, APIs and AI Agents: Data Exchange in Transportation
A trailer leaving Montréal for Chicago generates about ten data exchanges before the invoice is paid, whether by EDI, API, portal, email or phone. I wanted to understand who sets these rules, who exchanges what with whom and what is changing. I built an atlas of data exchange in transportation, freely available; here is what I took away from it.
In brief
- In North America, transportation still runs on EDI under the ASC X12 standard: the 204 for the tender, the 990 for the response, the 214 for status updates, the 210 for the invoice.
- APIs are arriving one mode at a time, driven by industry standards: the NMFTA's DSDC for trucking, the DCSA for ocean shipping, IATA's ONE Record for air cargo.
- Customs authorities are already setting the pace: CARM has been the CBSA's official system since October 21, 2024, and the road electronic manifest must be transmitted at least one hour before arrival at the border, in both Canada and the United States.
- AI agents connected through MCP sit on top of APIs: they replace neither APIs nor data quality.
- For a carrier or a shipper, the priority is to take stock of its exchanges and put its data in order before changing channels.
An ordinary shipment, about ten exchanges
Let's take a generic example: a trailer leaving Montréal for Chicago. Even before the truck rolls, the shipper has sent a tender (a load offer), the carrier has accepted it and a bill of lading has been issued. The bill of lading is the document that attests to the pickup of the goods and the terms of transport.
At least one hour before the border, the carrier has transmitted its electronic manifest to U.S. customs. Next come tracking statuses, the delivery appointment, proof of delivery, the invoice and the payment.
Some of these exchanges go through EDI, others through API, portal, email or phone. And each partner has its own rules.
1. EDI still holds the chain together
EDI (electronic data interchange) is the transmission of business documents between systems in a standardized format. In North America, the reference standard is that of ASC X12, a not-for-profit organization accredited by the American National Standards Institute for more than 40 years, which has a subcommittee dedicated to transportation (X12I).
Four messages structure the cycle of a road shipment, as described by TrueCommerce:
- 204: the shipper or broker offers a load to the carrier (locations, goods, schedules, rate, instructions).
- 990: the carrier accepts, accepts with conditions or declines.
- 214: the carrier transmits statuses (pickup, transit, delivery), each with a code.
- 210: the carrier invoices the shipper or broker electronically.
Large shippers require it of their carriers, and it works. TrueCommerce also notes that a carrier unable to meet a partner's EDI requirements may be excluded from certain business opportunities.
The difficulty is not the standard, it is how it is applied. Each large partner sets its own requirements and publishes its own implementation guide: mandatory fields, status codes, references to transmit. No two 214 messages are ever quite alike. Each new EDI connection is therefore partly a custom project.
2. APIs are arriving, one mode at a time
An API (application programming interface) lets two systems query each other directly, in real time, rather than exchanging files in batches. In transportation, APIs are being structured mode by mode, around standards published by industry organizations.
| Mode | Organization | Published standards | What they cover |
|---|---|---|---|
| Trucking | DSDC, a division of the NMFTA | Less-than-truckload (LTL) and full truckload (FTL) | Electronic bill of lading (eBOL), in-transit visibility, rating/quoting, booking and tender, appointments, invoice and documents |
| Ocean | DCSA, founded by the major carriers | Track & Trace, Booking 2.0, Bill of Lading 3.0 | Container tracking, booking, electronic bill of lading |
| Air | IATA | ONE Record | Data sharing on air cargo shipments |
Trucking. The Digital Standards Development Council (DSDC) is a division of the National Motor Freight Traffic Association (NMFTA), the organization that issues and governs SCAC codes used to identify carriers. It publishes open API standards for LTL (eBOL 2.1, in-transit visibility, preliminary freight charges) and for full truckload (Book and Tender, Rate/Quote, appointment scheduling, invoice and documents).
Ocean. The Digital Container Shipping Association was formed in 2019 by Maersk, Hapag-Lloyd, MSC and Ocean Network Express, according to Supply Chain Dive. Its Track & Trace standard describes shipment, transport and equipment events, as well as IoT sensor and refrigerated container events. In February 2025, it published the final versions of its Booking 2.0 and Bill of Lading 3.0 standards.
Air. Since January 1, 2026, ONE Record has been the preferred data-sharing standard for air cargo. In a survey published on December 10, 2025 by IATA, more than 70% of respondents were aware of ONE Record and nearly 50% said they were ready.
An API brings real-time data and simpler integration. But moving from EDI to JSON does not, by itself, settle the underlying question: agreeing on what the data means. That is why these standards matter more than the technology itself.
The two channels will coexist for a long time. The right question is not "EDI or API?" but "which flow would benefit from going real-time?"
3. Authorities are moving too
Canadian and U.S. customs have already digitized their exchanges with carriers, importers and brokers. Their deadlines apply to every cross-border shipment.
| System | Authority | For whom | Channels | Deadline |
|---|---|---|---|---|
| CARM | CBSA (Canada) | Importers and brokers | CARM Client Portal, EDI or API | Official system since October 21, 2024 |
| ACI eManifest (road) | CBSA (Canada) | Road carriers | EDI or eManifest portal | Data received and validated at least 1 h before arrival |
| ACE eManifest (truck) | CBP (United States) | Road carriers | Electronic transmission | 1 h before arrival; 30 min for FAST shipments |
Since October 21, 2024, CARM has been the CBSA's official system for assessing and collecting duties and taxes. The detailed declaration can be submitted there through the client portal, by EDI or by API. However, a broker can submit it for an importer only once the importer has delegated that authority to them in the CARM portal.
On the carrier side, the CBSA's ACI eManifest requires that conveyance and cargo data be received and validated at least one hour before arrival at the border, by EDI or through the eManifest portal.
In the United States, the CBP rule announced in 2003 also sets a one-hour advance notice, reduced to 30 minutes for carriers enrolled in the FAST program, according to FleetOwner. A guide published in July 2026 by Kordovatek confirms these time frames and specifies that the 30-minute window assumes the carrier, the driver and the importer are all FAST-approved and the shipment is eligible.
For a cross-border carrier, these deadlines already dictate part of how the work is organized: data must be ready before departure, not at the border.
4. Canada uses standards written elsewhere
While building the atlas, one box stayed empty: I did not find a Canadian organization that publishes data exchange standards specific to road transportation. Carriers and shippers here use American standards (X12, NMFTA) or international ones (GS1, UN/CEFACT).
That is not a problem in itself. But requirements specific to Canada (Canadian customs, GST and QST, provincial identifiers, French) then get handled case by case, in each integration.
5. The middle of the chain remains manual
Between major accounts and large platforms, exchanges are automated. Between a broker and a small carrier, it is often a rate confirmation as a PDF by email, a phone call to find out where the truck is, a proof of delivery taken with a photo.
That is where I see the most re-keying, errors and invoicing delays. It is also where it is hardest to verify that a partner is who they claim to be.
This is not a matter of goodwill. A small transportation company has neither the budget nor the team to maintain dozens of EDI connections, each with its own guide.
6. What about AI agents?
MCP (Model Context Protocol) is an open protocol that lets an AI assistant call tools, data and applications. Freight platforms are starting to expose MCP servers so that an agent can quote, book or track a shipment:
- On May 13, 2026, Shipwell launched an MCP server giving AI assistants access to the shipments, carriers, contracts, invoices and dock schedules in its TMS.
- On September 29, 2026, Flexport launched an MCP server that lets shippers' AI agents track, quote and book freight on its platform.
- Since December 9, 2025, MCP has been one of the founding projects of the Linux Foundation's Agentic AI Foundation, to which Anthropic contributed it.
So should we skip the API step and go straight to agents? I don't think so, because MCP does not replace APIs: it sits on top of them. It says how an agent calls a tool, not what a tender or a bill of lading is. An agent connected to poorly structured data does no better than a human. It just makes mistakes faster. I cover this at greater length in why AI projects in transportation fail.
One question remains open: when an agent books a truck for $4,200, who authorized it, and how can that be proven? I have not yet found an industry standard that answers it.
What I take away for a carrier or a shipper
- Take stock of your exchanges. Who sends you what, through which channel, and how much re-keying that represents.
- Put your own data in order before changing channels. References, status codes, addresses, units. This is what serves EDI, APIs and agents.
- Add APIs where real time pays off. Visibility, appointments, quoting. Keep EDI where it works.
- Don't wait for a perfect standard. But when a standard exists for a flow, start from it rather than inventing your own format.
Frequently asked questions
What is the difference between EDI and API in transportation?
EDI exchanges standardized documents (tender, status, invoice) between systems, generally in batches, under the X12 standard in North America. An API lets two systems query each other directly, in real time. In both cases, the value first depends on agreeing on what the data means.
Should EDI be replaced with APIs?
No, not systematically. EDI works well for established flows with large shippers, who continue to require it. It is better to ask which flows would benefit from going real-time, such as visibility, appointments or quoting, and add APIs there.
How long before the border must the electronic manifest be transmitted?
In Canada, the CBSA requires that ACI eManifest data be received and validated at least one hour before arrival, by EDI or through the eManifest portal. In the United States, the CBP also requires one hour, or 30 minutes for eligible FAST shipments. The data must therefore be ready before the truck leaves.
Will AI agents and MCP replace existing integrations?
No. MCP defines how an AI agent calls a tool, but not what a tender or a bill of lading is. It relies on existing APIs and data; if those are poorly structured, the agent will reproduce the errors faster.
Are there Canadian standards for data exchange in transportation?
While building the atlas, I did not find a Canadian organization that publishes data exchange standards specific to road transportation. Companies here use American standards (X12, NMFTA) or international ones (GS1, UN/CEFACT). Canadian requirements, such as GST and QST or French, are therefore handled in each integration.
Going further
The complete atlas, with 18 players, 32 flows and all the sources, is freely available. It also exists in English, and I will keep it up to date.
And you, which data exchange costs you the most re-keying today? If you want to take stock of your flows or decide where to add APIs, I invite you to get in touch with me or to look at my transportation consulting in Quebec offering.
Sources
Sources consulted on November 9, 2026.