The OnTime Trucking API

Every request carries an API key as a Bearer token over HTTPS. Mint one in the portal under API Access. Keys are prefixed ott_live_, shown once at creation (copy it immediately), and you can keep 2 active keys at a time so you can rotate with zero downtime.

Authorization: Bearer ott_live_xxxxxxxx

A key can only do what OnTime Trucking has granted your account — its scopes. Each endpoint below lists the scope it requires; calling one you aren't granted returns 403 insufficient_scope (and names the missing scope).

Full request/response schemas live in the OpenAPI spec — point your codegen, Postman, or AI agent at it for the canonical types.

Pass accessorial services on POST /quotes as an accessorials array of these codes — for example "accessorials": ["LIFD", "RESD"]. Send the code, not a label like “liftgate”.

Replace $OTT_KEY with your key. Prefer a guided walkthrough? The interactive quickstart in your portal takes you from key → first verified call with a live test button.

export OTT_KEY=ott_live_xxxxxxxx

# Fetch one of YOUR quotes by its id
# (the "Quote #" on the quote page, or the quoteId from POST /quotes)
curl https://ontimetrucking.com/api/v1/quotes/759124905 \
  -H "Authorization: Bearer $OTT_KEY"

# Live tracking by PRO
curl https://ontimetrucking.com/api/v1/shipments/123456789/tracking \
  -H "Authorization: Bearer $OTT_KEY"

# Create a rate quote (add accessorials by code — see the Accessorial codes table)
curl -X POST https://ontimetrucking.com/api/v1/quotes \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json" \
  -d '{"originZip":"11735","destZip":"10001","weightLbs":500,"accessorials":["LIFD","RESD"]}'

# Create a rate quote with per-commodity line items (mixed classes + NMFC per line).
# When you send commodities[], each line is rated with its own class; top-level
# weightLbs/pieces/freightClass become optional aggregates.
curl -X POST https://ontimetrucking.com/api/v1/quotes \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json" \
  -d '{"originZip":"11735","destZip":"10001","commodities":[
        {"freightClass":"70","weightLbs":800,"pieces":2,"nmfc":"156600"},
        {"freightClass":"125","weightLbs":300,"pieces":1,"nmfc":"049880"}
      ]}'

# Book that quote — assigns a PRO and schedules the pickup in one call.
# ship-from/ship-to are reused from the saved quote unless you override them here.
# notes prints on the OTT BOL; customerReference (your PO / pickup ref) rides to
# the carrier so it lands on carrier paperwork + tracking.
curl -X POST https://ontimetrucking.com/api/v1/quotes/qt_3Fa9c2/book \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json" \
  -d '{"pickupDate":"2026-07-15","readyTime":"09:00","closeTime":"17:00","customerReference":"PO-88231","notes":"Call dock 30 min before arrival"}'

You only ever see your own data — a quote or shipment that isn't yours returns 404 (never a hint that it exists).

Sample — POST /quotes (201)

{
  "quoteId": "qt_3Fa9c2",
  "options": [
    { "carrierName": "TForce Freight", "totalUSD": 312.40, "transitDays": 2 },
    { "carrierName": "Ward", "totalUSD": 318.75, "transitDays": 2 }
  ],
  "expiresAt": "2026-06-29T20:14:00Z"
}

Sample — POST /quotes/{id}/book (201)

{
  "quoteId": "qt_3Fa9c2",
  "status": "BOOKED",
  "pro": "773117166",
  "bolNumber": "BOL-260715-3FA9C2",
  "pickupConfirmation": "WBU68949302",
  "carrierName": "TForce",
  "customerReference": "PO-88231"
}

Sample — GET /shipments/{pro} (200)

{
  "pro": "123456789",
  "status": "IN_TRANSIT",
  "originZip": "11735",
  "destZip": "10001",
  "weightLbs": 500,
  "freightClass": "100",
  "dims": { "lengthIn": 48, "widthIn": 40, "heightIn": 48 },
  "pieces": 2,
  "nmfc": "156600",
  "customerReference": "PO-88231",
  "accessorials": ["LIFD"],
  "commodities": []
}

Sample — GET /shipments/{pro}/tracking (200)

{
  "pro": "123456789",
  "status": { "code": "IN_TRANSIT", "description": "In transit" },
  "pickup": { "date": "2026-06-25T14:02:00Z" },
  "delivery": null,
  "events": [
    {
      "date": "2026-06-26T09:14:00Z",
      "description": "Departed service center",
      "serviceCenter": "Edison, NJ"
    },
    {
      "date": "2026-06-25T14:02:00Z",
      "description": "Picked up",
      "serviceCenter": "Farmingdale, NY"
    }
  ]
}

Every response is clean and ready to use — one all-in price, transit time, live status, and your shipment documents. No rate tables to decode, no surcharges to add up.

Switch on code, not the human title. Every error echoes the requestId too.

{
  "type": "https://ontimetrucking.com/technology/api#errors",
  "title": "Resource not found",
  "status": 404,
  "detail": "Shipment not found.",
  "code": "not_found",
  "requestId": "0be4c35a-0f05-4905-97da-d3367748eaa4"
}

Per-client caps, shared across our servers. On exceed you get 429 with a Retry-After header (seconds) — wait, then retry.