NMFTA (the National Motor Freight Traffic Association) is the nonprofit membership body that has set the standards for North American freight since 1956, and through its Digital Standards Development Council it is now publishing that same industry agreement as open OpenAPI contracts. Its councils — Digital LTL and Digital FTL — turn the paper artifacts of trucking into machine-readable APIs: the bill of lading, the rate quote, the invoice and supporting documents, in-transit visibility, appointment scheduling, and preliminary freight charges. It is one of the clearest examples of an old, mandate-free trade association choosing specifications-as-code over another PDF behind a membership wall.
NMFTA
NMFTA has been the standards-setting authority for North American freight since 1956, and it frames itself as “setting the standards for a smarter, safer, and more connected freight industry.” For most of that history the standards were classification and coding — the NMFC freight classification, ClassIT+, the SCAC carrier codes and SPLC location codes that the industry still runs on. The interesting part now is the Digital Standards Development Council (DSDC), which is doing the same job for the API layer.
- Two councils, one program - The DSDC integrates the earlier Digital LTL Council (less-than-truckload) and Digital FTL Council (full truckload) under a single mission: publish API guidelines, documentation and process so freight movements can run as a fully digital exchange.
- Specifications as OpenAPI, in public - The contracts are OpenAPI 3.x documents in public GitHub repositories under github.com/dsdcapis, versioned and forkable, rather than a document you have to join to read.
- The paper artifacts, digitized - Electronic Bill of Lading (eBOL), Rate Quote, Invoice & Documents, In-Transit Visibility, Appointment Scheduling, Preliminary Freight Charges — each one a physical or EDI process the standard replaces with an HTTP contract.
- Volunteer workshops, not a vendor spec - Scope, field definitions and logic are set in workshops run with carriers, shippers, 3PLs and technology providers, which is why the specs read as industry agreement rather than one platform’s model.
- A public-preview maturity ladder - Much of the FTL catalog ships as
1.0.0-public-preview, while the LTL eBOL is already at 2.1.0 — the two councils are visibly at different stages of the same journey. - No regulatory mandate - Like CAMARA, and unlike the open-banking standards, NMFTA’s API work is industry-built. Adoption has to be earned on cost and friction, not compelled.
The gap worth watching is the same one every industry standard has: the specification is downloadable and the endpoint is somebody else’s. The DSDC publishes the contract; carriers, shippers and their technology providers publish — or don’t publish — the callable implementation. That distance between a published standard and a developer who can find, price and call a real API is exactly what the freight sector has not yet been measured on.
