NMFTA website screenshot

NMFTA

The National Motor Freight Traffic Association (NMFTA) is the nonprofit membership body that has set the standards for North American freight since 1956, and through its Digital Standards Development Council (DSDC) it publishes that industry agreement as open OpenAPI contracts. Two councils sit under the DSDC — the Digital LTL Council, founded November 2020, and the Digital FTL Council, which absorbed the Scheduling Standards Consortium — and between them they turn the paper artifacts of trucking into machine-readable APIs: the electronic bill of lading, the rate quote, the invoice and supporting documents, in-transit visibility, appointment scheduling, book and tender, and preliminary freight charges. For most of NMFTA's history its standards were classification and coding — the NMFC freight classification, ClassIT+, SCAC carrier codes, SPLC location codes — and the DSDC is the same institution doing the same job for the API layer. 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, and the gap between what its website advertises as released and what its public repositories actually contain is the most interesting thing about it.

NMFTA publishes 9 APIs on the APIs.io network, including Carrier API Standards API, Document Management API, Events API, and 6 more. Tagged areas include API Standards, DSDC, Digital FTL Council, Digital LTL Council, and Freight.

NMFTA’s developer surface includes developer portal, product news, and 19 more developer resources.

21.9/100 emerging ▬ flat Agent 17/100 agent aware Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
6 APIs 10 Features
API StandardsDSDCDigital FTL CouncilDigital LTL CouncilFreightFull TruckloadLTLLess-Than-TruckloadLogisticsNMFTAOpenAPIStandardsStandards BodySupply ChainTransportationTrucking

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/nmfta: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

NMFTA Carrier API Standards API

Standards for Carrier APIs

NMFTA Document Management API

Endpoints for uploading, and managing supporting documents.

NMFTA Events API

Pull shipment events

NMFTA In Transit Visibility API

The In Transit Visibility API API from NMFTA — 0 operation(s) for in transit visibility api.

NMFTA Invoice Management API

Endpoints for creating, retrieving, and managing invoices.

NMFTA Preliminary Freight Charges API

Access freight charges information

NMFTA Rate Quote API Standards API

Standards for the FTL Rate Quote API

NMFTA Subscriptions API

Manage webhook subscriptions

NMFTA Webhooks API

Webhook management and testing

Scroll for all 9

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

In-Transit Visibility API

OPEN COLLECTION

Invoice & Document API

OPEN COLLECTION

Rate Quote API

OPEN COLLECTION

Features 10

Notable capabilities this provider offers.

Host: NMFTA, founded 1956; DSDC is a division, not a separate entity
Councils: Digital LTL (November 2020) and Digital FTL (absorbed the Scheduling Standards Consortium)
APIs advertised: 10 across the two councils
Specifications in public repositories: 5 of 10
GitHub repositories: 6, two of which are named test repositories
Contributors: 5 humans, 123 total contributions
Participating companies published as logos: 32
Participants already in the API Evangelist network: 15
Regulatory mandate: none — adoption earned on cost and friction
Server declarations across all six harvested specifications: zero

Scroll for all 10

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Build 3

SDKs, sample code, and the tooling you integrate with

Operate 2

Status, limits, changes, and where to get help

Company 2

The organization behind the API

Other 11

Properties that don't map to a standard resource type

Scroll for all 11

Source (apis.yml)

apis.yml Raw ↑
aid: nmfta
url: https://raw.githubusercontent.com/api-evangelist/nmfta/refs/heads/main/apis.yml
name: NMFTA
description: 'The National Motor Freight Traffic Association (NMFTA) is the nonprofit membership body that has set the standards
  for North American freight since 1956, and through its Digital Standards Development Council (DSDC) it publishes that industry
  agreement as open OpenAPI contracts. Two councils sit under the DSDC — the Digital LTL Council, founded November 2020, and
  the Digital FTL Council, which absorbed the Scheduling Standards Consortium — and between them they turn the paper artifacts
  of trucking into machine-readable APIs: the electronic bill of lading, the rate quote, the invoice and supporting documents,
  in-transit visibility, appointment scheduling, book and tender, and preliminary freight charges. For most of NMFTA''s history
  its standards were classification and coding — the NMFC freight classification, ClassIT+, SCAC carrier codes, SPLC location
  codes — and the DSDC is the same institution doing the same job for the API layer. 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, and the
  gap between what its website advertises as released and what its public repositories actually contain is the most interesting
  thing about it.'
tags:
- API Standards
- DSDC
- Digital FTL Council
- Digital LTL Council
- Freight
- Full Truckload
- LTL
- Less-Than-Truckload
- Logistics
- NMFTA
- OpenAPI
- Standards
- Standards Body
- Supply Chain
- Transportation
- Trucking
kind: standard
deliveryModel:
  model: unknown
  open_source: unknown
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  - repository-unlicensed
  generated: '2026-08-28'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/nmfta.png
access: 3rd-Party
created: '2026-08-03'
modified: '2026-08-03'
position: Producing
specificationVersion: '0.23'
x-type: standards-body
x-category: Specification
x-host: National Motor Freight Traffic Association
x-host-structure: Trade association division
apis:
- aid: nmfta:nmfta-carrier-api-standards-api
  name: NMFTA Carrier API Standards API
  description: Standards for Carrier APIs
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - Carrier API Standards
  properties:
  - type: OpenAPI
    url: openapi/nmfta-carrier-api-standards-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
- aid: nmfta:nmfta-document-management-api
  name: NMFTA Document Management API
  description: Endpoints for uploading, and managing supporting documents.
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - Document-Management
  tags_raw:
  - Document Management
  properties:
  - type: OpenAPI
    url: openapi/nmfta-document-management-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
- aid: nmfta:nmfta-events-api
  name: NMFTA Events API
  description: Pull shipment events
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/nmfta-events-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
- aid: nmfta:nmfta-in-transit-visibility-api-api
  name: NMFTA In Transit Visibility API
  description: The In Transit Visibility API API from NMFTA — 0 operation(s) for in transit visibility api.
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - In Transit Visibility API
  properties:
  - type: OpenAPI
    url: openapi/nmfta-in-transit-visibility-api-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
- aid: nmfta:nmfta-invoice-management-api
  name: NMFTA Invoice Management API
  description: Endpoints for creating, retrieving, and managing invoices.
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - Invoice Management
  properties:
  - type: OpenAPI
    url: openapi/nmfta-invoice-management-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
- aid: nmfta:nmfta-preliminary-freight-charges-api
  name: NMFTA Preliminary Freight Charges API
  description: Access freight charges information
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - Preliminary Freight Charges
  properties:
  - type: OpenAPI
    url: openapi/nmfta-preliminary-freight-charges-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
- aid: nmfta:nmfta-rate-quote-api-standards-api
  name: NMFTA Rate Quote API Standards API
  description: Standards for the FTL Rate Quote API
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - Rate Quote API Standards
  properties:
  - type: OpenAPI
    url: openapi/nmfta-rate-quote-api-standards-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
- aid: nmfta:nmfta-subscriptions-api
  name: NMFTA Subscriptions API
  description: Manage webhook subscriptions
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - Subscription
  tags_raw:
  - Subscriptions
  properties:
  - type: OpenAPI
    url: openapi/nmfta-subscriptions-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
- aid: nmfta:nmfta-webhooks-api
  name: NMFTA Webhooks API
  description: Webhook management and testing
  humanURL: https://dsdc.nmfta.org/apis/ebol-api-standard
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/nmfta-webhooks-api-openapi.yml
  - type: Documentation
    url: https://dsdc.nmfta.org/apis/ebol-api-standard
  - type: SourceCode
    url: https://github.com/dsdcapis/less-than-truckload
  - type: SourceCode
    url: https://github.com/dsdcapis/full-truckload
common:
- type: Website
  url: https://www.nmfta.org/
- type: CapabilityMap
  url: capabilities/nmfta-capability-edges.yml
  name: NMFTA Business Capability Map
- type: IssueTracker
  url: https://github.com/dsdcapis/less-than-truckload/issues
- type: CodeOfConduct
  url: https://github.com/dsdcapis/less-than-truckload/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/dsdcapis/less-than-truckload/blob/main/CONTRIBUTING.md
- type: Portal
  url: https://nmfta.org/
- type: Specification
  url: https://dsdc.nmfta.org/apis
- type: GitHubOrganization
  url: https://github.com/dsdcapis
- type: SourceCode
  url: https://github.com/dsdcapis
- type: WorkingGroups
  url: https://dsdc.nmfta.org/digital-ltl-council
- type: Contributing
  url: https://dsdc.nmfta.org/contributor-agreement-form
- type: News
  url: https://dsdc.nmfta.org/news
- type: Events
  url: https://nmfta.org/nmfta-event/2026-dsdc-membership-meeting/
- type: Contact
  url: mailto:dsdc@nmfta.org
- type: Governance
  url: governance/nmfta-governance.yml
- type: Taxonomy
  url: taxonomy/nmfta-taxonomy.yml
- type: Companies
  url: companies/nmfta-companies.yml
- type: Adoption
  url: adoption/nmfta-adoption.yml
- type: Leads
  url: leads/nmfta-new-company-leads.yml
- type: Repositories
  url: repositories/nmfta-repositories.yml
- type: Contributors
  url: contributors/nmfta-contributors.yml
- type: Features
  updated: '2026-08-03'
  sources:
  - https://dsdc.nmfta.org/apis
  - https://github.com/dsdcapis
  data:
  - 'Host: NMFTA, founded 1956; DSDC is a division, not a separate entity'
  - 'Councils: Digital LTL (November 2020) and Digital FTL (absorbed the Scheduling Standards Consortium)'
  - 'APIs advertised: 10 across the two councils'
  - 'Specifications in public repositories: 5 of 10'
  - 'GitHub repositories: 6, two of which are named test repositories'
  - 'Contributors: 5 humans, 123 total contributions'
  - 'Participating companies published as logos: 32'
  - 'Participants already in the API Evangelist network: 15'
  - 'Regulatory mandate: none — adoption earned on cost and friction'
  - 'Server declarations across all six harvested specifications: zero'
maintainers:
- FN: Kin Lane
  email: info@apievangelist.com
  X: apievangelist
  url: https://apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/nmfta"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/nmfta/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/nmfta/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.