How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

NMFTA Carrier API Standards API

Standards for Carrier APIs

NMFTA Carrier API Standards API is one of 9 APIs that NMFTA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Carrier API Standards. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

4 operations 3 paths 6 schemas 1 DELETE2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Resource Areas
1

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Carrier API Standards 4

Standards for Carrier APIs

POST
/bol/v1/app
Create/Update/Delete an Electronic Bill of Lading
bol body → 200400
POST
/bol/v1/app/
Create an Electronic Bill of Lading
body → 200400
PUT
/bol/v1/app/{pro}
Update an Electronic Bill of Lading
1 param body → 200400404
DELETE
/bol/v1/app/{pro}
Delete an Electronic Bill of Lading
1 param → 200404400

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are BOL_Request (13 properties), BOL_Response (8 properties). Each schema is shown below with its type and property counts.

FTL_BOL_Response
FTL_Version
string
Indicates which version of the Digital FTL Council Bill of Lading spec you are consuming
FTL_BOL_Request
BOL_Response
object
8 properties
BOL_Request
object
Objects and/or attributes that are required are indicated by a red asterisk. For those that are conditionally required, it will be indicated within their descr…
13 properties 7 required
Result_Status_Codes
Numerical codes describing any logical status outcomes. Not all codes apply to this API, but are included to encourage adoption of these standards across API s…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nmfta-carrier-api-standards-api-openapi.yml Raw ↑

Other APIs NMFTA publishes across the network.

NMFTA Document Management API
NMFTA Events API
NMFTA In Transit Visibility API
NMFTA Invoice Management API
NMFTA Preliminary Freight Charges API
NMFTA Rate Quote API Standards API
NMFTA Subscriptions API
NMFTA Webhooks API
Where this information came from

This is an independent, third-party profile of NMFTA Carrier API Standards API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.