API docs by Redocly

Tender API (1.0.0-public-preview)

URL: https://github.com/dsdcapis/full-truckload License: DSDC Repository License

Overview

The Book Tender API provides a standard way to tender Full Truckload (FTL) shipments to carriers. It enables shippers, carriers, and third parties to offer, accept, update, and cancel truckload tenders in a consistent, digitized format, replacing manual processes such as phone calls, faxes, and emails and reducing the time it takes to secure carrier capacity.

Value Proposition

Shipper

Shippers can tender a load to a carrier using a single standardized request, and can update or cancel that tender as needed, reducing the manual effort of phone calls, faxes, and emails traditionally used to secure carrier capacity.

Carrier

Carriers can receive tender offers in a standard format, simplifying connectivity with a large number of shippers and third parties while reducing onboarding costs and the manual effort required to accept, update, or cancel tenders.

3rd Party

Third parties such as brokers and 3PLs can embed the Book Tender API into their platforms to tender loads to carriers programmatically on behalf of shippers, enabling automated capacity sourcing and faster tender turnaround.

Product Requirements Document (PRD)

The Product Requirements Document (PRD) for this API can be found here.

Book Tender API Standards

Standards for the FTL Book Tender API

Create a tender

Request Body schema: application/json
required
Array of objects (TenderParty)

Parties involved in the tender (customer, billing, or third party).

required
Array of objects (TenderLocation) >= 2 items

Ordered pickup, midpoint, and/or drop stops for the shipment.

object (ShipmentDetails)

Service options and constraints requested for this tender.

Array of objects (ReferenceNumber)

Responses

Request samples

Content type
application/json
{
  • "parties": [
    ],
  • "locations": [
    ],
  • "shipmentDetails": {
    },
  • "references": [
    ]
}

Response samples

Content type
application/json
{
  • "status": "CREATED",
  • "tenderIdentifier": "TenderNumber-123",
  • "details": "Tender created successfully."
}

Update a tender

Request Body schema: application/json
required
tenderIdentifier
required
string
Array of objects (TenderParty)
Array of objects (TenderLocation)
object (ShipmentDetails)

Service options and constraints requested for this tender.

Array of objects (ReferenceNumber)

Responses

Request samples

Content type
application/json
{
  • "tenderIdentifier": "string",
  • "parties": [
    ],
  • "locations": [
    ],
  • "shipmentDetails": {
    },
  • "references": [
    ]
}

Response samples

Content type
application/json
{
  • "status": "CREATED",
  • "tenderIdentifier": "TenderNumber-123",
  • "details": "Tender created successfully."
}

Cancel a tender

Request Body schema: application/json
required
tenderIdentifier
required
string
reason
string
Array of objects (ReferenceNumber)

Responses

Request samples

Content type
application/json
{
  • "tenderIdentifier": "string",
  • "reason": "string",
  • "references": [
    ]
}

Response samples

Content type
application/json
{
  • "status": "CREATED",
  • "tenderIdentifier": "TenderNumber-123",
  • "details": "Tender created successfully."
}