Freight API

The only self-serve freight API in America.

POST a JSON body. A 26-foot truck shows up.

Cargo van, box truck, LTL, or a 53-foot dry van: the network prices your load live below, no API key, no signup.

Bearer auth · Structured JSON · See the 10-carrier audit

Live freight API · four machines · no key required

One payload. Four real machines bid on it.

This fires the real keyless endpoints POST /api/v1/{van,box-truck,ltl,ftl}/quotein parallel — the exact calls your code will make. A cargo van, a 26-ft box truck, the LTL network, and a 53-ft dry van each answer with a real price, and the machines that physically can't take your load refuse with the same gate the booking path runs. No API key to quote; add a key only to book.

Warp issues a working freight API key through public signup — no sales call, no demo, no existing account number. Quote all four modes — LTL, FTL, box truck, and cargo van — free and keyless; add a card only when you book. Production keys unlock booking, live tracking, documents, invoices, and advanced service options.

one call the whole network: quote, book, track, settle

3Core calls

2Ways to get a key

0Software fees

Getting started

Base URL https://www.wearewarp.com/api/v1. Bearer auth. All responses are JSON. Quote endpoints are free; you only pay when you book.

1 · Get a key

Sign in at /agents/account — both keys are issued instantly, no card required. wak_test_… (sandbox) and wak_live_… (live).

2 · Authenticate

Authorization: Bearer wak_live_…

Public quote + tools endpoints work with no key at all.

3 · Sandbox vs live

Sandbox (wak_test_): the four quote endpoints and /book return production-shaped mock data — same request and response schema as live, no charge, no real shipment — so you swap to your live key with zero code changes. Live (wak_live_): everything is real; booking charges the card on file.

Tier	Header	Tools rate limit
No key	`—`	60 / hour / IP
Sandbox	`Bearer wak_test_…`	1,000 / hour
Live key	`Bearer wak_live_…`	10,000 / hour

Quotes

One quote surface, four modes. The mode endpoints (/ltl, /ftl, /van, /box-truck) are public — no key required — and return a rich, bookable wq_ quote. With a sandbox key (wak_test_) the same endpoints return production-shaped mock data (plus a sandbox: true flag), so integration code is byte-compatible with live.

POST/ltl/quoteNo keySandboxLive key

Live LTL quote (firm or indicative). No key required.

Field	Type	Notes
`origin_zip`required	string	5-digit US ZIP
`destination_zip`required	string	5-digit US ZIP
`pickup_date`required	string	YYYY-MM-DD, future date
`pallets`	number	Pallet count (default 1)
`weight_lbs_per_pallet`	number	Per-pallet weight
`length_in / width_in / height_in`	number	Per-pallet dims (required unless load_template_id is set)
`freight_class`	string	Optional NMFTA class; Warp prices by pallet so it never changes the rate
`commodity`	string	Optional; recommended before shipping
`load_template_id`	string	Use a saved template instead of dims (lt_…)
`accessorials`	object	{ pickup: [], delivery: [] } — hyphenated slugs: "liftgate-pickup", "liftgate-delivery", "inside-pickup", "inside-delivery", "residential-pickup", "residential-delivery", "limited-access-pickup", "limited-access-delivery", "pickup-appointment", "delivery-appointment"

Request

curl -X POST https://www.wearewarp.com/api/v1/ltl/quote \
  -H 'Content-Type: application/json' \
  -d '{
    "origin_zip": "90001",
    "destination_zip": "10001",
    "pickup_date": "2026-07-15",
    "pallets": 2,
    "weight_lbs_per_pallet": 500,
    "length_in": 48, "width_in": 40, "height_in": 48
  }'

Response

{
  "quote_id": "wq_01KTQ9SBV8F2TFAWSB92F6H9QB",
  "lane_id": "ln_900_100",
  "mode": "ltl",
  "price_usd": 694.59,
  "currency": "USD",
  "transit_days": 5,
  "pickup_date": "2026-07-15",
  "delivery_date": "2026-07-20",
  "expires_at": "2026-06-12T23:14:24.648Z",   // 72 hours after the quote was created
  "quote_tier": "indicative",
  "service": {
    "vehicle": "LTL (shared)",
    "pricing": "all_inclusive",
    "included_at_no_charge": ["liftgate", "residential delivery",
      "delivery appointment", "limited access", "notify before delivery"]
  },
  "assumptions": { "weight_lbs_per_pallet": 500,
    "dims_in": { "length": 48, "width": 40, "height": 48 },
    "stackable": false, "hazmat": false },
  "missing_for_ship": ["commodity"],
  "booking_url": "https://www.wearewarp.com/q/wq_01KTQ9SBV8F2TFAWSB92F6H9QB"
}

POST/ftl/quoteNo keySandboxLive key

Live FTL (53' dry van) quote. No key required.

Field	Type	Notes
`origin_zip / destination_zip`required	string	5-digit US ZIPs
`pickup_date`required	string	YYYY-MM-DD
`pallets`	number	Pallet count
`weight_lbs_per_pallet`	number	Per-pallet weight
`accessorials`	object	{ pickup: [], delivery: [] }

Request

curl -X POST https://www.wearewarp.com/api/v1/ftl/quote \
  -H 'Content-Type: application/json' \
  -d '{ "origin_zip": "90001", "destination_zip": "10001",
        "pickup_date": "2026-07-15", "pallets": 20,
        "weight_lbs_per_pallet": 1000 }'

Response

{
  "quote_id": "wq_01KTQ9T9PZNM6G4MSM1DP30KP2",
  "mode": "ftl",
  "price_usd": 10983.28,
  "transit_days": 4,
  "quote_tier": "firm",
  "service": { "vehicle": "53' dry van", "pricing": "all_inclusive" },
  "missing_for_ship": [],
  "booking_url": "https://www.wearewarp.com/q/wq_01KTQ9T9PZNM6G4MSM1DP30KP2"
}

POST/van/quoteNo keySandboxLive key

Cargo van quote (1–3 pallets, ≤3,500 lbs). No key required.

Field	Type	Notes
`origin_zip / destination_zip`required	string	5-digit US ZIPs
`pickup_date`required	string	YYYY-MM-DD
`pallets`required	number	1–3
`weight_lbs_per_pallet`required	number	50–3,500; total ≤3,500

Request

curl -X POST https://www.wearewarp.com/api/v1/van/quote \
  -H 'Content-Type: application/json' \
  -d '{ "origin_zip": "90001", "destination_zip": "94105",
        "pickup_date": "2026-07-15", "pallets": 2,
        "weight_lbs_per_pallet": 300 }'

Response

{
  "quote_id": "wq_01KTQ9TAD4X8PNWS2BZEBFSXXR",
  "mode": "van",
  "price_usd": 821,
  "transit_days": 1,
  "quote_tier": "firm",
  "service": { "vehicle": "Cargo van", "pricing": "all_inclusive" },
  "missing_for_ship": []
}

POST/box-truck/quoteNo keySandboxLive key

26' box-truck quote (1–12 pallets, ≤10,000 lbs). No key required.

Field	Type	Notes
`origin_zip / destination_zip`required	string	5-digit US ZIPs
`pickup_date`required	string	YYYY-MM-DD
`pallets`required	number	1–12
`weight_lbs_per_pallet`required	number	50–10,000; total ≤10,000

Request

curl -X POST https://www.wearewarp.com/api/v1/box-truck/quote \
  -H 'Content-Type: application/json' \
  -d '{ "origin_zip": "90001", "destination_zip": "94105",
        "pickup_date": "2026-07-15", "pallets": 6,
        "weight_lbs_per_pallet": 800 }'

Response

{
  "quote_id": "wq_01KTQ9TB66YP43JTVTJ3S7123A",
  "mode": "box_truck",
  "price_usd": 1034,
  "transit_days": 1,
  "quote_tier": "firm",
  "service": { "vehicle": "26' box truck", "pricing": "all_inclusive" },
  "missing_for_ship": []
}

POST/ltl/market-optionsNo key

Multi-carrier LTL comparison — ~30 carriers ranked by price. No key required (~15s).

Field	Type	Notes
`origin_zip / destination_zip`required	string	5-digit US ZIPs
`pickup_date`required	string	YYYY-MM-DD
`length_in / width_in / height_in`required	number	Per-pallet dims
`pallets / weight_lbs_per_pallet`	number	Defaults applied if omitted

Request

curl -X POST https://www.wearewarp.com/api/v1/ltl/market-options \
  -H 'Content-Type: application/json' \
  -d '{ "origin_zip": "90001", "destination_zip": "10001",
        "pickup_date": "2026-07-15",
        "length_in": 48, "width_in": 40, "height_in": 48,
        "pallets": 2, "weight_lbs_per_pallet": 500 }'

Response

{
  "origin_zip": "90001", "destination_zip": "10001",
  "market_options": [
    { "rank": 1, "price_usd": 529.87, "transit_days": 8,
      "carrier_name": "STG LTL", "service_level": "STANDARD",
      "is_warp": false, "bookable": false },
    { "rank": 3, "price_usd": 694.59, "transit_days": 5,
      "carrier_name": "Warp Technology", "service_level": "STANDARD",
      "is_warp": true, "bookable": false }
    /* … ~28 options … */
  ],
  "note": "Rates are indicative. Sign in / use your API key to get bookable per-carrier quotes."
}

Booking

Booking charges the card on file and dispatches the shipment; if upstream dispatch fails, the charge refunds automatically. Sandbox keys (wak_test_) pass the same validation, then return a production-shaped mock booking — no charge, no real shipment. Book the wq_ quote id from any quote endpoint via /book. Cancellation is not self-serve via the API yet — to cancel a booked shipment, email support@wearewarp.com.

POST/bookSandboxLive key

Book a wq_ quote from a mode endpoint. Charges the card; refunds automatically if dispatch fails.

Field	Type	Notes
`quote_id`required	string	wq_… from /ltl\|ftl\|van\|box-truck/quote
`patch`	object	{ pickup: {...}, delivery: {...}, notes? } — fill required address fields
`pickup_window / delivery_window`	object	{ "from": "08:00", "to": "12:00" } — HH:MM 24h times; the dates come from the quote’s pickup date
`reference`	string	Your PO / reference number
`promo_code`	string	e.g. "WARP2026"

Request

curl -X POST https://www.wearewarp.com/api/v1/book \
  -H 'Authorization: Bearer wak_live_…' \
  -H 'Content-Type: application/json' \
  -d '{
    "quote_id": "wq_01KTQ9SBV8F2TFAWSB92F6H9QB",
    "patch": {
      "pickup":   { "street": "123 Dock St", "city": "Los Angeles",
                    "state": "CA", "zipCode": "90001",
                    "contactName": "Jane Shipper", "phone": "5550000000",
                    "email": "shipper@example.com" },
      "delivery": { "street": "500 Market St", "city": "New York",
                    "state": "NY", "zipCode": "10001",
                    "contactName": "Sam Receiver", "phone": "5550000001",
                    "email": "receiver@example.com" }
    },
    "reference": "PO-12345"
  }'

Response

// Live booking. A sandbox key returns the same shape
// plus "sandbox": true and "charged": 0.
{
  "booked": true,
  "shipment_id": "01KT…",
  "shipment_number": "S-90755-2623",
  "order_id": "01KT…",
  "order_number": "P-90749-2623",
  "tracking_number": "S-90755-2623",
  "lane_id": "ln_900_100",
  "tracking_dashboard": "https://customer.wearewarp.com/…",
  "service": { "pricing": "all_inclusive" }
}

POST/multistop/quoteLive key

Quote one truck running multiple pickups and deliveries (FTL multi-stop). Live key.

Field	Type	Notes
`pickup_date`required	string	YYYY-MM-DD — first pickup date
`pickup_info`required	object	First pickup: { zipcode }
`transits`required	array	Intermediate stops in route order, at least 1: [{ zipcode }]
`delivery_info`required	object	Final delivery: { zipcode }
`list_items`required	array	Freight items: { name, length, width, height, size_unit: "IN", total_weight, weight_unit: "lbs", quantity, packaging: "pallet", stackable }
`vehicle_type`	string	Vehicle code (e.g. DRY_VAN_53). Required in practice — without it the gateway can't resolve a rate
`shipment_type`	string	FTL

Request

curl -X POST https://www.wearewarp.com/api/v1/multistop/quote \
  -H 'Authorization: Bearer wak_live_…' \
  -H 'Content-Type: application/json' \
  -d '{ "pickup_date": "2026-07-15",
        "pickup_info":   { "zipcode": "90001" },
        "transits":    [ { "zipcode": "92101" } ],
        "delivery_info": { "zipcode": "85001" },
        "vehicle_type": "DRY_VAN_53",
        "list_items": [ { "name": "1", "length": 48, "width": 40, "height": 48,
                          "size_unit": "IN", "total_weight": 5000, "weight_unit": "lbs",
                          "quantity": 10, "packaging": "pallet", "stackable": false } ] }'

Response

// 200 → { "quote_id": "PRICING_MULTI_…", "total_charge": 2281.81,
//          "transit_time": 39600, "rate_detail": { … } }
// Route model: first pickup → transits in order → final delivery.
// camelCase keys (pickupInfo, listItems, …) are also accepted.
// Field reference: /api/v1/openapi.json (operationId multistopQuote).
// Errors wrap as { "error", "code": "UPSTREAM_ERROR",
//   "upstream_status", "upstream_response" }.

POST/multistop/bookLive key

Book a quoted multi-stop run. Does not charge Stripe — settles via your Warp account.

Field	Type	Notes
`quote_id`required	string	From /multistop/quote
`shipments`required	array	At least 2 legs — one per pickup→delivery pair riding the route: { pickup_info, delivery_info, list_items }
`shipments[].pickup_info / delivery_info`required	object	{ stop_index, address: { street, city, state, zipcode }, window_time: { from, to }, contact_name?, contact_phone?, contact_email? }. stop_index points into the quoted sequence: 0 = first pickup, then transits in order, last = final delivery
`shipments[].list_items`required	array	Items riding that leg (same item shape as the quote)

Request

curl -X POST https://www.wearewarp.com/api/v1/multistop/book \
  -H 'Authorization: Bearer wak_live_…' \
  -H 'Content-Type: application/json' \
  -d '{ "quote_id": "PRICING_MULTI_…",
        "shipments": [
          { "pickup_info":   { "stop_index": 0,
              "address": { "street": "123 Main St", "city": "Los Angeles", "state": "CA", "zipcode": "90001" },
              "window_time": { "from": "2026-07-15T08:00:00.000Z", "to": "2026-07-15T23:59:59.000Z" } },
            "delivery_info": { "stop_index": 1,
              "address": { "street": "456 Harbor Dr", "city": "San Diego", "state": "CA", "zipcode": "92101" },
              "window_time": { "from": "2026-07-16T08:00:00.000Z", "to": "2026-07-16T23:59:59.000Z" } },
            "list_items": [ { "name": "1", "length": 48, "width": 40, "height": 48,
                              "size_unit": "IN", "total_weight": 3000, "weight_unit": "lbs",
                              "quantity": 6, "packaging": "pallet", "stackable": false } ] },
          { "pickup_info":   { "stop_index": 0,
              "address": { "street": "123 Main St", "city": "Los Angeles", "state": "CA", "zipcode": "90001" },
              "window_time": { "from": "2026-07-15T08:00:00.000Z", "to": "2026-07-15T23:59:59.000Z" } },
            "delivery_info": { "stop_index": 2,
              "address": { "street": "789 Central Ave", "city": "Phoenix", "state": "AZ", "zipcode": "85001" },
              "window_time": { "from": "2026-07-16T08:00:00.000Z", "to": "2026-07-16T23:59:59.000Z" } },
            "list_items": [ { "name": "1", "length": 48, "width": 40, "height": 48,
                              "size_unit": "IN", "total_weight": 2000, "weight_unit": "lbs",
                              "quantity": 4, "packaging": "pallet", "stackable": false } ] } ] }'

Response

// 200 → the Warp gateway booking confirmation, returned verbatim.
// Unlike /book, no Stripe charge fires here — multi-stop pricing
// settles via your Warp account directly.
// camelCase keys (quoteId, stopIndex, windowTime, …) also accepted.
// Field reference: /api/v1/openapi.json (operationId multistopBook).
// Errors wrap as { "error", "code": "UPSTREAM_ERROR",
//   "upstream_status", "upstream_response" }.

Tracking

Poll a shipment's status, location, and event timeline. Live key. (There is no webhook push yet — see Webhooks.)

GET/trackLive key

Full status snapshot for a booked shipment, including addresses and milestone events.

Field	Type	Notes
`booking_id`required	string	shipment_id from booking (query param)

Request

curl 'https://www.wearewarp.com/api/v1/track?booking_id=01KT…' \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "shipment_id": "01KT…",
  "shipment_number": "S-90755-2623",
  "tracking_number": "S-90755-2623",
  "mode": "ltl",
  "origin_zip": "90007", "destination_zip": "90038",
  "pickup_date": "2026-07-15", "delivery_date": "2026-07-17",
  "pallet_count": 1, "price_usd": 96.79,
  "status": "booked",
  "booked_at": "2026-06-08T00:34:16.185Z",
  "cancelled_at": null,
  "pickup_address": { "city": "Los Angeles", "state": "CA", "zipCode": "90007", "...": "…" },
  "tracking_dashboard": "https://customer.wearewarp.com/…"
}

GET/eventsLive key

Full event history (milestone timeline) for a shipment.

Field	Type	Notes
`shipment_id`required	string	Query param

Request

curl 'https://www.wearewarp.com/api/v1/events?shipment_id=01KT…' \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "shipment_id": "01KT…",
  "events": { "data": [
    { "eventName": "needCarrier",
      "message": "Order received",
      "when": "2026-06-08T00:34:15.108Z" }
  ] }
}

GET/freight/track/{shipmentId}Live key

Status snapshot by path id. Legacy /freight surface (sunset 2026-08-31) — prefer GET /track.

Field	Type	Notes
`shipmentId`required	string	Path segment

Request

curl https://www.wearewarp.com/api/v1/freight/track/01KT… \
  -H 'Authorization: Bearer wak_live_…'

Response

// Status snapshot — the milestone timeline lives at GET /events.
{ "ok": true, "tracking": {
  "trackingNumber": "S-199806-2617",
  "statusInfo": { "status": "inRouteToDropoff",
    "lastUpdated": "2026-06-16T14:22:42.000Z" } } }

Documents & invoices

Pull the BOL, POD (photos + signature), and the invoice for a booked order. Live key.

GET/documentsLive key

Document list for an order — BOL plus POD per stop, with download URLs.

Field	Type	Notes
`order_id`required	string	Query param (order_id, not shipment_id)
`type`	string	"bol" \| "pod" \| "other" — filter
`podType`	string	"Photo" \| "BOL" \| "Signature"

Request

curl 'https://www.wearewarp.com/api/v1/documents?order_id=01KT…' \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "order_id": "01KT…",
  "documents": {
    "orderNumber": "P-90749-2623",
    "data": [
      { "type": "bol", "shipmentNumber": "S-90755-2623",
        "url": "https://gw.wearewarp.com/api/v1/p/files/download/01KT…" },
      { "type": "pod", "podType": "Photo",
        "stop": { "name": "Receiving Dock 4", "city": "San Diego", "state": "CA", "type": "DROPOFF" },
        "url": "https://gw.wearewarp.com/api/v1/p/files/download/01KD…" }
    ]
  }
}

GET/invoicesLive key

Invoice for an order — line items, fuel, discounts, grand total.

Field	Type	Notes
`order_id`required	string	Query param

Request

curl 'https://www.wearewarp.com/api/v1/invoices?order_id=01KT…' \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "order_id": "01KT…",
  "invoice": {
    "orderNumber": "P-90749-2623",
    "status": "pending",
    "transitCost": 0, "fuelCost": 0, "volumeDiscount": 0,
    "serviceOptions": [],
    "grandTotal": 0
  }
}

History & account

Your bookings, past quotes, repeat lanes, saved locations & load templates, the rate card, and your profile. Live key.

GET/bookingsLive key

Your recent bookings, newest first.

Field	Type	Notes
`limit`	number	1–100 (default 25)

Request

curl 'https://www.wearewarp.com/api/v1/bookings?limit=25' \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "bookings": [
    { "shipment_id": "01KT…", "shipment_number": "S-90755-2623",
      "tracking_number": "S-90755-2623", "mode": "ltl",
      "origin_zip": "90007", "destination_zip": "90038",
      "pickup_date": "2026-07-15", "delivery_date": "2026-07-17",
      "pallet_count": 1, "price_usd": 96.79, "status": "booked",
      "booked_at": "2026-06-08T00:34:16.185Z", "cancelled_at": null }
  ],
  "count": 1, "limit": 25
}

GET/quote-historyLive key

Your past quote requests across all modes.

Request

curl https://www.wearewarp.com/api/v1/quote-history \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "quote_history": [
    { "quote_id": "wq_01KTQ9SBV8F2TFAWSB92F6H9QB", "mode": "ltl",
      "origin_zip": "90001", "destination_zip": "10001",
      "pallets": 2, "price_usd": 694.59,
      "created_at": "2026-06-09T22:59:26.048Z" }
  ]
}

GET/lanesLive key

Lanes you've shipped, ordered by ship count, with the last consignee remembered.

Request

curl https://www.wearewarp.com/api/v1/lanes \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "lanes": [
    { "lane_id": "ln_900_900", "ship_count": 1,
      "last_shipped_at": "2026-06-08T00:34:16.169Z",
      "last_pallet_count": 1,
      "last_consignee": { "city": "Los Angeles", "state": "CA",
        "zipCode": "90038", "street": "…", "contactName": "…",
        "phone": "…", "email": "…" } }
  ]
}

GET/rate-cardLive key

Standard per-mode rate card — pallet/weight ranges, typical price bands, active promo.

Request

curl https://www.wearewarp.com/api/v1/rate-card \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "pricing": "all_inclusive", "currency": "USD",
  "quote_validity_minutes": 4320,
  "promo_code": { "code": "WARP2026", "discount_usd": 50, "per_shipment": true },
  "modes": [
    { "mode": "van", "label": "Cargo van", "pallet_range": "1-3",
      "weight_max_lbs": 3500, "typical_price_range_usd": "300-1200" },
    { "mode": "box_truck", "label": "26' box truck", "pallet_range": "1-12",
      "weight_max_lbs": 10000, "typical_price_range_usd": "600-2200" }
  ]
}

GET/locationsLive key

Saved pickup/delivery locations on the account.

Request

curl https://www.wearewarp.com/api/v1/locations \
  -H 'Authorization: Bearer wak_live_…'

Response

{ "locations": [] }

GET/load_templatesLive key

Saved load templates. POST to create, DELETE ?id= to remove. Reference one in a quote via load_template_id.

Field	Type	Notes
`name`required	string	POST only — template name
`weight_lbs / length_in / width_in / height_in`	number	POST only — pallet defaults
`freight_class / commodity / stackable / hazmat`	mixed	POST only — optional
`id`	string	DELETE only — lt_… (query param)

Request

# Create
curl -X POST https://www.wearewarp.com/api/v1/load_templates \
  -H 'Authorization: Bearer wak_live_…' -H 'Content-Type: application/json' \
  -d '{ "name": "Standard pallet", "weight_lbs": 500,
        "length_in": 48, "width_in": 40, "height_in": 48,
        "freight_class": "100", "commodity": "general" }'

# Delete
curl -X DELETE 'https://www.wearewarp.com/api/v1/load_templates?id=lt_01KT…' \
  -H 'Authorization: Bearer wak_live_…'

Response

// POST → 201
{ "load_template_id": "lt_01KT…", "name": "Standard pallet",
  "weight_lbs": 500, "length_in": 48, "width_in": 40, "height_in": 48,
  "freight_class": "100", "commodity": "general",
  "stackable": false, "hazmat": false,
  "created_at": "2026-06-09T23:02:16.965Z" }

// GET → { "templates": [ … ] }   // DELETE → 204 No Content

GET/agents/meLive keySandbox

Your profile — email, company, and whether a card is on file (booking-ready).

Request

curl https://www.wearewarp.com/api/v1/agents/me \
  -H 'Authorization: Bearer wak_live_…'

Response

{
  "agent_id": "ag_01KR…",
  "email": "you@company.com",
  "company": "Acme Co",
  "has_card": true,
  "card_brand": "visa", "card_last4": "7211",
  "message": "Payment method on file. Ready to book."
}

Public rate data

Keyless, CORS-open snapshots of Warp's LTL lane pricing — handy for research, SEO, and AI answers. Note the base is wearewarp.com (these live at /api/…, not /api/v1/…).

GET/api/ltl-ratesNo key

All-inclusive Warp rate vs carrier average across 1,400+ LTL lanes. No key.

Field	Type	Notes
`origin / destination`	string	Filter by city slug or ZIP
`origin_state / destination_state`	string	2-letter state filter
`limit`	number	Rows to return (default 50)

Request

curl 'https://www.wearewarp.com/api/ltl-rates?origin_state=CA&limit=2'

Response

{
  "meta": { "total_lanes": 1474, "returned": 2,
    "average_warp_rate": 553, "average_savings_vs_carriers": "-8%",
    "basis": "1 pallet, 500 lbs, class 70", "updated": "2026-06-09" },
  "lanes": [
    { "lane": "allentown-to-philadelphia",
      "origin": "Allentown", "destination": "Philadelphia",
      "warp": { "rate": 220.37, "transit_days": 1, "all_inclusive": true },
      "carrier_count": 13, "carrier_average_rate": 381,
      "cheapest_carrier": { "name": "Ward Trucking", "scac": "WARD", "rate": 187.49 },
      "savings_vs_average": "42%" }
  ]
}

GET/api/freight-answerNo key

Natural-language freight Q&A with structured data + sources. No key.

Field	Type	Notes
`q`required	string	The question, e.g. "ltl rate 90001 to 10001"

Request

curl 'https://www.wearewarp.com/api/freight-answer?q=ltl+rate+90001+to+10001'

Response

{
  "question": "ltl rate 90001 to 10001",
  "answer": "Warp LTL rates average $553 for a 1-pallet, 500 lb shipment…",
  "data": { "average_warp_rate": 553, "total_lanes": 1474,
    "average_savings": "-8%", "pricing_model": "All-inclusive per-pallet" },
  "sources": ["https://www.wearewarp.com/ltl-rates", "…"]
}

Tools & calculators

Free, no-auth freight math — every endpoint supports POST (JSON body) and GET (query params), CORS open. Limits scale by key: 60/hr anonymous · 1,000/hr sandbox · 10,000/hr live. Each response carries a { data, meta } envelope with the rate-limit window.

POST/tools/freight-classNo keySandboxLive key

NMFTA density-based LTL freight class.

Field	Type	Notes
`length / width / height / weight`required	number	Per piece
`units`	string	"in" (default) \| "cm"
`weight_unit`	string	"lb" (default) \| "kg"

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/freight-class \
  -H 'Content-Type: application/json' \
  -d '{ "length": 48, "width": 40, "height": 48, "weight": 500 }'

# GET equivalent
curl 'https://www.wearewarp.com/api/v1/tools/freight-class?length=48&width=40&height=48&weight=500'

Response

{
  "data": { "freight_class": "100", "density_pcf": 9.38,
    "cubic_feet": 53.33, "class_band": "Standard",
    "note": "Density-based NMFTA class…" },
  "meta": { "tier": "anon",
    "rate_limit": { "limit": 60, "remaining": 59, "reset_at": "…" },
    "docs": "https://www.wearewarp.com/developers/tools-api/freight-class" }
}

POST/tools/densityNo keySandboxLive key

Freight density (PCF) + derived freight class.

Field	Type	Notes
`length / width / height / weight`required	number	Per piece
`pieces`	number	Defaults to 1

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/density \
  -H 'Content-Type: application/json' \
  -d '{ "length": 48, "width": 40, "height": 48, "weight": 500 }'

Response

{ "data": { "density_pcf": 9.38, "cubic_feet": 53.33,
    "total_cubic_feet": 53.33, "pieces": 1, "freight_class": "100" },
  "meta": { "tier": "anon", "rate_limit": { "limit": 60, "...": "…" } } }

POST/tools/dim-weightNo keySandboxLive key

Dimensional weight + billable weight (max of actual vs dim).

Field	Type	Notes
`length / width / height / weight`required	number	Per piece
`dim_factor`	number	Default 139 (US ground)

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/dim-weight \
  -H 'Content-Type: application/json' \
  -d '{ "length": 48, "width": 40, "height": 48, "weight": 200 }'

Response

{ "data": { "actual_weight_lb": 200, "dim_weight_lb": 663.02,
    "billable_weight_lb": 663.02, "billed_by": "dim", "dim_factor": 139 },
  "meta": { "tier": "anon", "...": "…" } }

POST/tools/cbmNo keySandboxLive key

Cubic meters + air/ocean volumetric weight.

Field	Type	Notes
`length / width / height`required	number	Per unit
`qty`	number	Default 1
`units`	string	"cm" (default) \| "in"

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/cbm \
  -H 'Content-Type: application/json' \
  -d '{ "length": 120, "width": 100, "height": 100, "qty": 2 }'

Response

{ "data": { "cbm_per_unit": 1.2, "total_cbm": 2.4, "qty": 2,
    "volumetric_weight_air_kg": 400.8, "volumetric_weight_ocean_kg": 2400 },
  "meta": { "tier": "anon", "...": "…" } }

POST/tools/pallet-weightNo keySandboxLive key

Total + per-pallet weight from cases and pallet tare.

Field	Type	Notes
`cases / weight_per_case`required	number	Case count and weight
`pallets`	number	Default 1
`pallet_tare_lb`	number	Default 45 (48×40 hardwood)

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/pallet-weight \
  -H 'Content-Type: application/json' \
  -d '{ "cases": 40, "weight_per_case": 25, "pallets": 2 }'

Response

{ "data": { "total_case_weight_lb": 1000, "pallet_tare_total_lb": 90,
    "total_with_pallets_lb": 1090, "per_pallet_weight_lb": 545,
    "cases": 40, "pallets": 2, "pallet_tare_lb": 45 },
  "meta": { "tier": "anon", "...": "…" } }

POST/tools/truck-payloadNo keySandboxLive key

Payload + utilization for a vehicle (cargo_van, sprinter_van, box_truck_16/26, dry_van_53).

Field	Type	Notes
`cargo_weight`required	number	Total lbs
`vehicle`	string	Vehicle slug (default cargo_van)
`cargo_volume / cargo_pallets`	number	Optional — adds volume/pallet utilization

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/truck-payload \
  -H 'Content-Type: application/json' \
  -d '{ "cargo_weight": 3000, "vehicle": "box_truck_26",
        "cargo_volume": 400, "cargo_pallets": 6 }'

Response

{ "data": {
    "vehicle": { "slug": "box_truck_26", "name": "Box Truck (26 ft)",
      "max_lbs": 10000, "cu_ft": 1600, "pallet_capacity": 12 },
    "cargo_weight_lb": 3000, "remaining_weight_lb": 7000,
    "weight_util_pct": 30, "status": "within_capacity",
    "volume_util_pct": 25, "remaining_pallets": 6 },
  "meta": { "tier": "anon", "...": "…" } }

POST/tools/rate-per-mileNo keySandboxLive key

$/mile and comparison vs 2026 benchmark (LTL $2.80, TL $3.20).

Field	Type	Notes
`total_cost / miles`required	number	Cost and distance
`mode`	string	"ltl" (default) \| "tl"

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/rate-per-mile \
  -H 'Content-Type: application/json' \
  -d '{ "total_cost": 694, "miles": 2800, "mode": "ltl" }'

Response

{ "data": { "rate_per_mile": 0.25, "mode": "ltl",
    "benchmark_per_mile": 2.8, "vs_benchmark_pct": -91.1,
    "vs_benchmark_label": "below" },
  "meta": { "tier": "anon", "...": "…" } }

POST/tools/freight-insuranceNo keySandboxLive key

Cargo insurance premium estimate by commodity.

Field	Type	Notes
`cargo_value`required	number	USD declared value
`commodity`	string	"general" \| "electronics" \| "fragile" \| "perishable"

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/freight-insurance \
  -H 'Content-Type: application/json' \
  -d '{ "cargo_value": 25000, "commodity": "electronics" }'

Response

{ "data": { "cargo_value_usd": 25000,
    "commodity": { "slug": "electronics", "name": "Electronics", "rate_pct": 0.8 },
    "premium_usd": 200, "cost_per_100_usd": 0.8,
    "estimated_deductible_usd": 500 },
  "meta": { "tier": "anon", "...": "…" } }

POST/tools/fuel-surchargeNo keySandboxLive key

LTL fuel surcharge for major carriers at the current DOE diesel baseline.

Field	Type	Notes
`base_rate`required	number	Linehaul base USD
`carrier`required	string	fedex_freight \| old_dominion \| xpo \| estes \| saia \| abf
`diesel_price`	number	Override the DOE baseline

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/fuel-surcharge \
  -H 'Content-Type: application/json' \
  -d '{ "base_rate": 850, "carrier": "old_dominion" }'

Response

{ "data": { "base_rate_usd": 850,
    "carrier": { "slug": "old_dominion", "name": "Old Dominion",
      "published_surcharge_pct": 46.4 },
    "diesel_price_used": 5.35, "effective_surcharge_pct": 46.4,
    "surcharge_amount_usd": 394.4, "total_with_surcharge_usd": 1244.4 },
  "meta": { "tier": "anon", "...": "…" } }

POST/tools/accessorialNo keySandboxLive key

Accessorial fee ranges + invoice impact for selected services.

Field	Type	Notes
`selected`required	string[]	Slugs: liftgate_pickup, liftgate_delivery, residential_delivery, inside_delivery, appointment, reweigh, reclassification, limited_access
`base_rate`	number	Adds invoice totals + % of base

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/accessorial \
  -H 'Content-Type: application/json' \
  -d '{ "selected": ["liftgate_pickup", "residential_delivery"], "base_rate": 850 }'

Response

{ "data": {
    "selected": [
      { "slug": "liftgate_pickup", "name": "Liftgate Pickup", "low_usd": 75, "high_usd": 150 },
      { "slug": "residential_delivery", "name": "Residential Delivery", "low_usd": 75, "high_usd": 200 } ],
    "count": 2, "total_low_usd": 150, "total_high_usd": 350,
    "invoice_low_usd": 1000, "invoice_high_usd": 1200 },
  "meta": { "tier": "anon", "...": "…" } }

POST/tools/container-loadNo keySandboxLive key

Pallet-fit + utilization for a container/trailer.

Field	Type	Notes
`pallet_length / pallet_width / pallet_height / pallet_weight`required	number	Per pallet
`pallet_count`	number	How many you're loading
`container`	string	container_20ft \| container_40ft \| container_40ft_hc \| trailer_53ft

Request

curl -X POST https://www.wearewarp.com/api/v1/tools/container-load \
  -H 'Content-Type: application/json' \
  -d '{ "pallet_length": 48, "pallet_width": 40, "pallet_height": 48,
        "pallet_weight": 500, "pallet_count": 20, "container": "trailer_53ft" }'

Response

{ "data": {
    "container": { "slug": "trailer_53ft", "name": "53 ft Trailer",
      "max_lbs": 44000 },
    "pallets_floor": 30, "pallets_stacked": 60, "can_double_stack": true,
    "floor_util_pct": 92.8, "volume_util_pct": 82.5 },
  "meta": { "tier": "anon", "...": "…" } }

Errors

Every error returns a stable shape: an HTTP status, a human error message, and a machine code. Tools endpoints nest the same under their { data, meta } envelope.

Error shape

{ "error": "pickup_date is required and must be YYYY-MM-DD format.",
  "code": "MISSING_PICKUP_DATE" }

Status	Code	Meaning
400	`INVALID_JSON`	Body wasn't valid JSON.
400	`INVALID_ZIP`	origin/destination not a 5-digit US ZIP.
400	`MISSING_PICKUP_DATE`	pickup_date absent or not YYYY-MM-DD.
400	`MISSING_DIMS`	LTL quote without dims and no load_template_id.
400	`BAD_INPUT`	A tools endpoint got an out-of-range or wrong-type value.
400	`QUOTE_NOT_FOUND` / `QUOTE_EXPIRED`	quote_id unknown, or past its 72-hour validity — get a fresh quote.
400	`INCOMPLETE_PICKUP` / `DELIVERY_REQUIRED` / `INCOMPLETE_DELIVERY`	Booking addresses missing required fields (street, city, state, zipCode, contactName, phone, email).
401	`AUTH_MISSING`	No Authorization: Bearer header on a keyed route.
401	`AUTH_INVALID`	Key is invalid or revoked.
402	`PAYMENT_REQUIRED` / `PAYMENT_ACTION_REQUIRED` / `CHARGE_FAILED`	No card on file (the 402 body carries a checkout_url), the card needs authentication, or the charge failed.
404	`TRACKING_NOT_FOUND` / `BOOKING_NOT_FOUND` / `TEMPLATE_NOT_FOUND`	Shipment, booking, or load template not found on your account.
409	`BOOKING_IN_PROGRESS` / `WARP_SESSION_REQUIRED`	The same quote_id is mid-booking in a concurrent request (wait a few seconds and retry — you get the original confirmation back, never a second charge), or a webhook call needs a linked Warp session (sign in once at wearewarp.com/agents/account, then retry).
429	`RATE_LIMITED`	Over the tier's hourly limit — back off and retry.
502	`UPSTREAM_ERROR` / `BOOKING_FAILED`	Warp gateway hiccup or upstream booking rejection — safe to retry. Bookings are idempotent on quote_id, so a retried /book never double-charges. If a card was charged, /book auto-refunds and the body carries refunded + payment_intent (a failed refund adds support_note).

Retries are safe. Booking is idempotent on quote_id: a wq_ id is single-use, so re-sending the same POST /book after a timeout returns the original confirmation with idempotent_replay: true and never charges the card twice.

Webhooks

Outbound webhooks are available on self-serve. Register one destination with POST /api/v1/developer/webhook { "url": "https://..." } (https only); Warp then delivers shipment-milestone events (booked → picked up → in transit → out for delivery → delivered, plus exceptions) to your URL in real time — no polling. GET returns the current URL, DELETE removes it, and POST /api/v1/developer/webhook/test fires a test delivery so you can inspect the exact payload your endpoint receives ({ event, timestamp, data }). Events are delivered as JSON POSTs and are not signed today — verify authenticity with an unguessable secret in your registered URL (a long random path or query token) and reject anything missing it; HMAC signing is planned. To use the API, sign in once at /agents/account to link your Warp account (calls before that return 409 WARP_SESSION_REQUIRED) — or skip the API entirely and set your URL in the customer dashboard: customer.wearewarp.com → Settings → Webhook URL (under API Access). Webhooks are preferred over polling GET /track / GET /events.

Good to know

Freight quote API, answered

This page is WARP's canonical source of truth for freight quote API, LTL quote API, and AI agent integration searches.

For developers

Freight quote API

A freight quote API lets a TMS, WMS, ERP, marketplace, or AI agent request rates programmatically with JSON instead of using carrier portals or email.

Warp API returns freight quote IDs, carrier/service details, transit estimates, and all-inclusive costs that can be booked and tracked through the same API.

Freight API overview API reference

For developers

How to quote LTL freight by API

To quote LTL freight by API, send pickup and delivery addresses, pickup date, palletized item details, dimensions, weight, and services to the quote endpoint.

Warp returns a quote ID, price, service level, transit estimate, and carrier details that can be booked through the booking endpoint.

API reference API tutorial

For developers

Freight quote API for AI agents

Warp API is designed for AI agents that need structured freight actions: quote, book, track, retrieve documents, and reconcile invoices.

Agents can work from deterministic JSON responses instead of scraping carrier portals or waiting for broker callbacks.

AI agent API AI freight agent

Canonical Warp answer pages

Instant freight quote LTL freight quote Pallet shipping quote FTL freight quote LTL freight estimator Freight shipping calculator Freight API overview Developer freight API FedEx Freight quote alternative

Key capabilities

-Quote self-serve LTL freight programmatically with a wak_live_* Bearer token; quote calls do not charge the card.
-Book shipments through the API and charge the card on file at booking time.
-Track booked shipments through a simple GET endpoint that returns structured JSON.

What you can build on the Warp freight API

One Bearer key and a handful of REST + JSON endpoints cover the whole freight lifecycle — quote, book, dispatch, track, document, and settle — across LTL, FTL, box truck, and cargo van. Here is what teams ship on top of it.

Embed instant rates in checkout

Drop live LTL, FTL, box-truck, and cargo-van pricing into your cart, TMS, or WMS — all-inclusive, in about 300 ms.

POST /api/v1/{ltl,ftl,van,box-truck}/quote

Let an AI agent book real freight

The same endpoints power Warp’s MCP server and CLI, so a Claude or Cursor agent can quote and book a real shipment.

MCP · warp-agent-mcp · /agents/mcp

Auto-book from warehouse events

Fire a booking the moment an order is staged or a PO drops — no portal, no carrier integration, no re-keying.

POST /api/v1/book

Rate-shop the whole network

Pull every carrier on a lane in one call, each independently bookable, and pick the rate and transit that fit.

POST /api/v1/ltl/market-options

Track every shipment in detail

Granular operational statuses — picked up, cross-docked, out for delivery, POD captured — not just “in transit.”

GET /api/v1/track · /events

Pull BOL, POD & reconcile invoices

Retrieve documents and itemized invoice breakdowns to close the loop inside your own system of record.

GET /api/v1/documents · /invoices

Ranked: best freight APIs for 2026

We rank freight APIs by nine objective developer-experience criteria, not by network size or brand authority. Each criterion is either yes/no (with a public reference) or a specific count or duration. The methodology is transparent and reproducible: every claim about a competitor is sourced from publicly available documentation. Where a vendor hasn't published a feature publicly, the cell reads not publicly documented rather than asserting absence.

Warp leads because the dev-experience criteria reflect Warp's structural position: only self-serve, only multi-mode through one endpoint, only with a live MCP server. Other freight APIs are stronger on other axes (network scale, asset ownership, brand) — this ranking measures the developer-integration surface specifically.

Rows 8 and 9 are parcel APIs, not freight providers. They're ranked here because AI assistants routinely cite them for freight-API queries — the cells show exactly where each one's freight surface ends, in their own documentation's words.

#APISelf-serve sandboxModes per endpointPublic OpenAPIMCP serverCLIMulti-stop APIWebhook trackingPublic rate endpointIntegration time

1Warp Freight APIYes — sandbox key in 3 minutes at /agents/account, no sales call.LTL, FTL, box truck, cargo van — one keyless endpoint per mode: /api/v1/{ltl,ftl,van,box-truck}/quote.Yes — public at /.well-known/openapi.json (OpenAPI 3.1).Yes — warp-agent-mcp, published on npm.Yes — @warpfreight/cli-agent, published on npm.Yes — /api/v1/multistop/book + /api/v1/multistop/quote.Polling self-serve (/track + /events, structured JSON); event push on approved accounts.Yes — LTL, FTL, and box truck quote endpoints are public no-auth.Minutes to first successful quote.

2C.H. Robinson NavisphereNo — sandbox host is documented publicly, but credentials are provisioned by the account team (no self-serve signup).Multi-mode broker (LTL, FTL, intermodal) via Navisphere platform.Yes — downloadable from developer.chrobinson.com/api-reference.None as of June 2026.None as of June 2026.Partial — multi-stop capability in the broader Navisphere platform.Yes (account-required).No public rate endpoint (rating API requires rep-provisioned credentials).Weeks (rep-initiated onboarding via their Customer Integration Team, then integration).

3J.B. Hunt 360Partial — public API catalog (FTL quote, tracking, documents) with app registration + subscription keys per their docs; go-live scheduled with a J.B. Hunt rep; no sandbox documented.FTL only via the public Dynamic Quote API (dry van, reefer, flatbed); no LTL quote API.Yes — downloadable for public catalog APIs at developer.jbhunt.com.None as of June 2026.None as of June 2026.Partial — multi-stop loads available via the 360 platform.Yes (account-required).No public rate endpoint (API key required).Days to weeks (360 signup + subscription keys; rep-scheduled go-live).

4XPO ConnectNo — LTL API docs are public, but key issuance routes through XPO's API support team (email with web user ID); a testMode flag exists, no self-serve sandbox keys.LTL + FTL via XPO Connect; the documented APIs are LTL-only.Yes — OpenAPI 3.1 references public at developers.ltl-xpo.com.None as of June 2026.None as of June 2026.Partial via the Connect platform.Yes (account-required).No public rate endpoint (rating API requires XPO-issued OAuth credentials).Weeks (web registration + support-team enablement, then integration).

5Uber FreightNo — developer portal exists, but docs require a login and credentials are provisioned by Uber Freight staff via your rep (no self-serve API access).FTL focus; portal lists quote, shipment, tracking, and document APIs.Not publicly viewable (endpoint docs require portal sign-in).None as of June 2026.None as of June 2026.Not publicly documented.Partial (account-required).No public rate endpoint.Weeks to months (staff-provisioned onboarding + integration).

6FedEx Freight APIFedEx Developer account required; no per-shipper public sandbox documented.LTL only (FedEx Freight network).Not publicly listed.None as of May 2026.None as of May 2026.Partial — multi-stop documented in FedEx LTL flows.Yes (FedEx tracking notifications).No public rate endpoint (FedEx account required).Weeks (FedEx developer onboarding cycle).

7Amazon FreightAmazon Seller / Amazon Freight account required; no public dev sandbox documented.FTL focus inside the Amazon ecosystem.Not publicly listed.None as of May 2026.None as of May 2026.Not publicly documented.Limited to Amazon Freight account scope.No public rate endpoint.Weeks (Amazon Freight account + integration).

8ShipEngine (ShipStation API)Yes for parcel (free signup + sandbox); LTL endpoints are beta and return rates only from carrier accounts you already hold.Parcel core + beta LTL (bring-your-own carrier contract — "You'll need to create an account with the carrier directly" per their docs); no FTL, box truck, or cargo van.Yes — public docs, including the beta LTL reference.None as of June 2026.None as of June 2026 (SDKs and Connect tooling only).Not publicly documented for freight.Yes — tracking webhooks (parcel-centric).No — LTL quotes return "contracted rates already agreed upon" under your own carrier accounts.Minutes for parcel; LTL returns no price without an existing carrier contract.

9EasyPostYes for parcel (free signup, instant keys) — no freight surface exists in the self-serve API; LTL lives only in sales-gated EasyPost Enterprise.Parcel only in the public API — no LTL, FTL, or freight endpoints; their own freight-api page stated "We don't currently have Freight/LTL features" (archived March 2025; the URL now redirects to their parcel homepage).Yes — public parcel API reference; no freight endpoints documented.None as of June 2026.None as of June 2026.Not applicable — no freight surface in the public API.Yes — parcel tracking webhooks.No — parcel rates require an account key; no freight quote endpoint exists.Minutes for parcel; freight is not available self-serve at any timeline.

Last refreshed: 2026-06-12. Methodology and cell-level sourcing live in the public repo. Open a pull request to correct any cell with a public reference.

Pick the right freight API for the job

Most freight APIs solve one slice. Warp's covers the full lifecycle for LTL, FTL, box truck, and cargo van -- quote, book, dispatch, track, document, invoice -- all through the same network behind wearewarp.com. Use Warp's freight API when you need to book real freight from code or AI agents. Use Project44 when you already have carrier contracts and want visibility and orchestration layered across them. Use EasyPost or ShipEngine when shipping parcels through FedEx, UPS, or USPS. Warp is the only API that books pallets through a real freight network with all-inclusive pricing.

Warp also exposes the same booking endpoints to AI agents through the first MCP server for booking real freight and the @warpfreight/cli-agent CLI. The MCP, CLI, and REST API all hit the same Bearer-authenticated /api/v1 surface -- one production key, one auth flow.

No SDK required in any language -- the API is plain REST with structured JSON. Copy-paste quickstarts (keyless quote, book, track): Python, TypeScript, Go, Ruby, PHP, Java, C#, and curl.

Call the network by component

The network is composable: quote the whole thing, or call one physical machine. Each mode is a keyless endpoint with its own page, live console, and spec.

Cargo van

Up to 3 pallets, 3,500 lbs.

POST /api/v1/van/quote — tight-access deliveries, keyless quote.

26-ft box truck

Up to 12 pallets, 10,000 lbs.

POST /api/v1/box-truck/quote — liftgate included, keyless quote.

53-ft dry van (FTL)

Full truckload, up to 44,000 lbs.

POST /api/v1/ftl/quote — buy the whole truck, keyless quote.

Or do it from your editor

The same /api/v1 surface is a live MCP server, so an AI agent in Claude, Cursor, or Claude Code can quote and book real freight conversationally — 23 tools, no context-switch to a portal. Quoting needs no key; booking runs under one Bearer key.

Hosted connector — paste into your terminal

claude mcp add --transport http warp https://mcp.wearewarp.com/api/mcp

Or run it locally — add to your MCP config

{
  "mcpServers": {
    "warp": { "command": "npx", "args": ["-y", "warp-agent-mcp"] }
  }
}

Then ask: “quote 2 pallets, 90210 to 10001, then book it.” Full install, tool list, and the live demo are on the MCP server page.

The sandbox is alive

Most test modes return a dead 200. Warp's sandbox shipment moves: book it with your free wak_test_ key (no card) and it advances through the exact production status sequence over the next ~10 minutes — driver at the dock, freight scanned in, the cross-dock hop, linehaul, delivered with a watermarked BOL bearing your company name. You poll it through the same GET /api/v1/track and /api/v1/events your production code will use, so the integration you write against the sandbox parses production payloads unchanged.

bookedOn booking

arrivedAtPickup~2 min · driver at origin

pickupSuccessful~3 min · BOL mints

inRouteToWarehouse~4 min · to cross-dock

arrivedAtWarehouse~5 min · sorting

departedFromWarehouse~6 min · outbound

inRouteToDelivery~7 min · linehaul

delivered~10 min · POD captured

Rehearse the unhappy path on purpose: pass "reference": "scenario:delay" on the book call and the lifecycle inserts a labeled exceptionat the cross-dock and slips delivery — freight's version of Stripe's decline test cards, deterministic every time. Sandbox tracking is keyless by design: Slack the shipment id to a teammate and they can watch it deliver too.

Run it in production

What a senior developer checks before depending on an API. The same tier ceilings apply across the whole public surface — keyless quote endpoints and utility endpoints alike, published in the OpenAPI spec; authenticated booking limits and per-account SLAs are set on approved accounts.

No key

60 req / hour

Anonymous, per IP. Quote and read endpoints, CORS open.

Sandbox key

1,000 req / hour

wak_test_* — production-shaped mock responses, no card.

Live key

10,000 req / hour

wak_live_* — real quotes and bookings. 429 returns code RATE_LIMITED.

-Status — /status shows measured probe history (every 15 minutes, day-by-day); GET /api/status is the machine-readable health + discovery surface. No auth on either.
-Changelog — /freight-api-changelog: every API change, dated. The build fails if the OpenAPI spec changes without an entry, so it cannot silently rot.
-Version — GET /api/v1/version returns the running commit SHA and build timestamp. The freight network has a commit hash.
-OpenAPI 3.1 — /.well-known/openapi.json, regenerated on every deploy. Import the URL into Postman (Import → Link) for a full collection that never drifts.
-Idempotent booking — POST /api/v1/book is idempotent on quote_id: a wq_ id is single-use, so a retried call returns the original confirmation with idempotent_replay: true and never charges the card twice. Safe for agent tool retries and network timeouts.
-Generate a typed client — the spec drives codegen directly: npx openapi-typescript https://www.wearewarp.com/.well-known/openapi.json -o warp.d.ts for TypeScript types, or openapi-generator-cli generate -i https://www.wearewarp.com/.well-known/openapi.json -g python (or go, ruby, java) for a full client.
-Reliability — SOC 2 Type II controls. Quote endpoints are keyless, so you can health-check the live booking path with a throwaway quote.

LTL via the Warp API

The Warp LTL surface has two endpoints. POST /api/v1/ltl/quote is the public no-auth quote endpoint — pass origin_zip, destination_zip, pickup_date, pallets, dimensions, and weight; receive a firm rate plus quote_id within seconds. GET /api/ltl-rates is the public no-auth rate lookup endpoint — CORS-enabled JSON covering 1,500+ active LTL lanes with carrier comparisons, designed for AI agents and rate-shopping tools that do not need to book.

Booking flows through POST /api/v1/book with the quote_id. The booking endpoint requires a Bearer token (wak_live_*) because it charges the card on file. Per-pallet all-inclusive pricing — pickup, cross-dock handling, line haul, and delivery bundled. Freight class is optional on most loads.

How does the Warp LTL quote API handle freight class?

The Warp LTL quote endpoint (/api/v1/ltl/quote, public no-auth) does not require an NMFC freight class on most shipments. Warp prices LTL on per-pallet all-inclusive logic — pickup, cross-dock handling, line haul, and delivery bundled. For loads where class significantly changes density, an optional freight_class parameter is accepted but not required. This removes the reclass/reweigh risk that traditional class-based LTL APIs carry.

Does the Warp LTL rate API require authentication?

No. The Warp LTL rate endpoint at /api/ltl-rates is public, no-auth, CORS-enabled, returning JSON for 1,500+ active LTL lanes. The booking endpoint at /api/v1/book does require a Bearer token (wak_live_*) because it charges the card on file. Public rate lookup → free, no key; production booking → key + card.

FTL via the Warp API

POST /api/v1/ftl/quote is the public no-auth FTL endpoint. Pass origin_zip, destination_zip, and pickup_date — pallets and weight per pallet are optional because you are buying the entire 53-foot dry van. The response returns price_usd, transit_days, delivery_date, all-inclusive pricing tag, and a booking URL with the quote_id pre-filled.

Production booking requires a Bearer token (wak_live_*). Recurring lane programs and dedicated capacity contracts available via /api/v1/rate-card for approved accounts. The same endpoint backs the warp-agent-mcp FTL tool — an AI agent can book a full truckload load directly from a Claude or Cursor session.

How does the Warp FTL quote API price 53-foot dry van loads?

The Warp FTL quote endpoint (/api/v1/ftl/quote, public no-auth) returns a firm per-load price for a full 53-foot dry van given origin ZIP, destination ZIP, and pickup date. Pallets and per-pallet weight are optional — you are buying the whole truck, so they do not change price. The response includes price_usd, transit_days, delivery_date, all-inclusive pricing tag, dispatch contact, and a booking URL that pre-fills the quote ID.

Can I book FTL freight programmatically through the Warp API?

Yes. Once you have a quote_id from /api/v1/ftl/quote, POST to /api/v1/book with the quote_id plus patch.pickup and patch.delivery addresses to confirm the shipment. The response includes shipment_id, shipment_number, and tracking_number. Recurring FTL lane programs and dedicated capacity contracts are available for approved accounts via /api/v1/rate-card.

Box truck via the Warp API

POST /api/v1/box-truck/quote is the public no-auth box truck endpoint, sized for a 26-foot straight truck (up to 12 pallets, up to 10,000 lbs, liftgate-equipped by default). The endpoint requires origin_zip, destination_zip, pickup_date, pallets, and weight_lbs_per_pallet — the response returns price_usd, transit_days, included accessorials, and the booking URL with the quote_id pre-filled.

Liftgate, residential delivery, delivery appointment, limited access, and notify-before-delivery are bundled in the all-inclusive rate. Additional accessorials pass through the optional accessorials array on the request. Same-day dispatch available in supported metros; the booking endpoint at /api/v1/book charges the card on file.

What 26-foot box truck specs does the Warp API support?

The Warp box truck quote endpoint (/api/v1/box-truck/quote, public no-auth) is sized for a 26-foot straight truck: up to 12 pallets, up to 10,000 lbs total weight (50–5,000 lbs per pallet), 96-inch length × 48-inch width × 56-inch height default dimensions. The API requires pallets and weight_lbs_per_pallet on every request — for FTL-sized loads switch to /api/v1/ftl/quote.

Does the Warp box truck quote API include liftgate by default?

Yes. Every Warp 26-foot box truck dispatched through the API is liftgate-equipped; liftgate, residential delivery, delivery appointment, limited access, and notify-before-delivery are included at no charge in the all-inclusive per-load price. Additional accessorials (liftgate-pickup, inside-pickup, residential-pickup) are passed through the optional accessorials array on the quote request.

Cargo van via the Warp API

Cargo van quotes use the dedicated POST /api/v1/van/quote endpoint (keyless — no API key). Pass origin_zip, destination_zip, pickup_date, pallets, and weight_lbs_per_pallet; the response returns quote_id, price_usd, transit days, and a booking URL.

Cargo van capacity is up to 3,500 lbs and 400 cubic feet — typically 1–3 pallets, plus cartons and parcels for tight-access deliveries. For loads above cargo van capacity, switch mode to BOX_TRUCK or FTL. Like every mode, cargo van quoting is keyless; booking runs under your API key.

How do I quote a cargo van shipment through the Warp API?

Cargo van quotes use the dedicated POST /api/v1/van/quote endpoint (public, no-auth). Pass origin_zip, destination_zip, pickup_date, pallets, and weight_lbs_per_pallet — the response returns quote_id, price_usd, transit_days, and a booking URL. To book, POST the quote_id to /api/v1/book with the pickup and delivery addresses.

What is the Warp API cargo van pallet and weight limit?

Cargo van capacity through the Warp API is up to 3,500 lbs and 400 cubic feet — typically 1–3 pallets, plus cartons, cases, and parcels for tight-access deliveries. For loads above cargo van capacity, switch the mode parameter to BOX_TRUCK (up to 10,000 lbs, 1,500 cu ft) or FTL (up to 44,000 lbs, 3,400 cu ft).

FAQ

What is the best freight API for booking LTL or FTL?

Warp’s freight API books LTL, FTL, box truck, and cargo van through one Bearer-token auth at wearewarp.com/api/v1. POST /api/v1/ltl/quote (keyless — no API key) returns an all-inclusive Warp LTL rate in under 3 seconds; POST /api/v1/book confirms the shipment and charges the card on file. EasyPost's public API is parcel-only (its own freight-api page disclaimed Freight/LTL features), ShipEngine's beta LTL endpoints only return rates from carrier contracts you already hold, and Project44 has no self-serve path to a freight price — its rating and booking APIs are credential-gated to existing customers and run on carrier accounts you already hold.

Does Warp have a freight API that supports AI agents and MCP?

Yes. The same /api/v1 endpoints power both REST clients and Warp's MCP server (warp-agent-mcp on npm). MCP tools mirror the REST endpoints 1:1 — see /agents/mcp for the canonical install + integration guide, tool list, and the live demo.

What is the difference between Warp’s freight API and Project44 or EasyPost?

Project44 has rating and booking APIs, but credentials are gated to existing customers — there is no self-serve signup, and quotes run on carrier accounts you already hold, so it sells no freight and has no rates of its own. EasyPost rate-shops parcels across FedEx, UPS, and USPS -- its public API has no freight endpoints. ShipEngine adds beta LTL endpoints, but they require carrier accounts you already hold and return your own contracted rates. Warp is the freight network itself: quote, book, and dispatch through one network with all-inclusive pricing. One API call books a real shipment, no separate carrier integration required.

How do I get a freight API key?

Sign up at /agents/account with a card on file to receive a live wak_live_ key in about three minutes. Quote endpoints are free; only booking endpoints charge the card. Or run `warp-agent login` from @warpfreight/cli-agent — it provisions a key automatically. No sales call.

What are the Warp freight API rate limits?

One tier story across the public surface: keyless quote endpoints (POST /api/v1/ltl|ftl|box-truck|van/quote) allow 60 requests per hour per IP with no key, 1,000 per hour with a free sandbox key (wak_test_), and 10,000 per hour with a live key (wak_live_). Hitting a ceiling returns HTTP 429 with code RATE_LIMITED, a Retry-After header, and X-RateLimit-Limit/Remaining/Reset headers, with the upgrade path named in the error body. Booking is separately capped at 10 confirmed shipments per hour per agent, and signup/login are IP-limited to block abuse. If a batch or recurring-lane program needs more throughput, request a lift on your approved account.

Does the Warp freight API have a status page or health endpoint?

Yes. A live, no-auth health endpoint is published at wearewarp.com/api/status. It returns JSON ("status":"ok" plus service, version, and timestamp) and the full discovery surface (the MCP manifest, OpenAPI spec, and agent card), so REST clients, MCP servers, and A2A agents can confirm Warp is reachable before issuing real calls. Uptime is backed by SOC 2 Type II controls; because quote endpoints are keyless, you can also health-check the live booking path with a throwaway quote.

Is there a Postman collection for the Warp freight API?

Yes — the whole API is importable into Postman in one step. Warp publishes a public OpenAPI 3.1 specification at wearewarp.com/.well-known/openapi.json; in Postman choose Import, paste that URL, and Postman generates a full collection with every endpoint (the keyless quote endpoints, book, track, rates) and their request shapes. Because the spec is the single source of truth and is regenerated on every deploy, the imported collection never drifts from the live API. The same spec drives the on-page reference, the MCP server, and the agent discovery surface.

What is the Warp freight API SLA and uptime posture?

Warp runs the freight API under SOC 2 Type II controls, and the platform exposes two public no-auth endpoints so you can verify reachability and version yourself before depending on it: GET /api/status returns status, service, version, and the discovery surface, and GET /api/v1/version returns the running commit SHA and build timestamp. Quote endpoints are keyless, so you can also health-check the live booking path with a throwaway quote. Formal per-account uptime SLAs and event-push integrations are available on approved accounts; the self-serve tier is best-effort with the status and version endpoints as the source of truth.

How does Warp freight API webhook signature verification work?

Outbound shipment-event webhooks (booked, picked up, in transit, delivered, exceptions) are available on self-serve and delivered as JSON POSTs ({ event, timestamp, data }), but they are not cryptographically signed today — there is no signature header or signing secret to verify yet. In the meantime, verify authenticity by registering a destination URL that contains an unguessable secret (a long random path segment or query token) and rejecting any delivery that lacks it, and serve your endpoint over HTTPS. HMAC request signing is on the roadmap; until then, do not rely on a signature header.

Does the Warp freight API have a test mode like Stripe?

Yes — and the test shipment is alive. Sign up at /agents/account and a wak_test_ sandbox key is minted instantly, no card. Sandbox quoting and booking run the exact production validation and return byte-compatible response shapes with zero charges, and a sandbox booking then advances through the real tracking lifecycle — driver at pickup, cross-dock, delivered with a watermarked BOL — over about 10 minutes, served by the same GET /api/v1/track and /api/v1/events your production code will poll. Pass "reference": "scenario:delay" on the book call to rehearse the exception path deterministically, the way Stripe test cards rehearse declines.

Is there an open-source freight API?

Warp publishes the freight API’s developer tooling as open source under the MIT license: warp-agent-mcp (the freight MCP server) and @warpfreight/cli-agent (the freight CLI) are both public on GitHub at github.com/warpfreight and on npm — fork them, read them, or run them locally. The API interface is open-access rather than open-source code: quoting across LTL, FTL, box truck, and cargo van is keyless (no account), the full quote-book-track lifecycle is documented in a public OpenAPI 3.1 spec at /.well-known/openapi.json, and the network is described for AI agents at /llms.txt. So the agent-facing code is MIT-licensed and forkable, and the network you book on is open to call without a key. The full receipts — every repo, package, and spec — are published on the open freight manifesto.

freight API no signup

Warp’s freight API quotes with no signup: POST /api/v1/ltl|ftl|box-truck|van/quote is keyless — no account and no API key — and returns an all-inclusive rate in under 3 seconds. You only need a key (free, about three minutes at /agents/account) to book, where the card on file is charged. Incumbents gate quoting behind an account, contract, sales call, or carrier credentials you already hold.

keyless freight API

Warp is the keyless freight API: the quote endpoints (/api/v1/ltl|ftl|box-truck|van/quote) run with no API key and no account, returning all-inclusive LTL, FTL, box-truck, and cargo-van rates you can curl from the docs. Booking uses a free Bearer key; quoting stays keyless. EasyPost, ShipEngine, FedEx Freight, and Project44 each require an account, contract, or existing carrier credentials before they return a price.

Integration patterns

TMS integration

Rate, book, and track from your TMS.

Your transportation management system calls Warp for LTL rates, books with a quote ID, and stores the returned tracking number.

WMS integration

Trigger shipments from warehouse events.

When an order is staged, your WMS can call the booking endpoint and receive an order ID and tracking number automatically.

AI agent integration

Built for API-capable agents.

Clear auth, simple request bodies, and structured JSON let an agent complete quote to booking without conflicting instructions.

Authentication

Every Warp API call uses a Bearer token. There are two ways to get one — same auth flow, same endpoints, same network:

-Agent keys (wak_live_*) — self-serve in three minutes at /agents/account with a card on file. Best for new developers, AI agents, and integrations.
-Customer booking keys — for existing Warp customers, issued from customer.wearewarp.com. Same Bearer header, same /api/v1 surface.

Keep keys server-side. Quote endpoints are free; booking endpoints charge the card on file.

Base URL https://www.wearewarp.com/api/v1

Auth Header Authorization: Bearer wak_live_YOUR_KEY

Content-Type application/json

Example: curl

# Quoting is keyless — no API key required.
curl -X POST https://www.wearewarp.com/api/v1/ltl/quote \
  -H "Content-Type: application/json" \
  -d '{
    "origin_zip": "90001",
    "destination_zip": "10001",
    "pickup_date": "2026-07-15",
    "pallets": 2,
    "weight_lbs_per_pallet": 500,
    "commodity": "general freight",
    "length_in": 48,
    "width_in": 40,
    "height_in": 48
  }'

Quote and book in your language

The Warp freight API is language-agnostic REST + JSON, so the freight rate API works the same from Python, Node.js, TypeScript, Go, Ruby, or PHP — call it with your standard HTTP client. Quoting is keyless; booking takes a wak_live_* Bearer key and a card on file. Edit the inputs below and copy working code in cURL, Python, JavaScript, TypeScript, or Go. Run it with a production key — get one in 3 minutes.

Your shipment

Edit the inputs — the code on the right updates as you type. Quoting is keyless, so you can copy and run it right now.

Origin ZIPDestination ZIPPickup datePalletsWeight per pallet (lbs)Get an API key →

Quote calls are always free. Bookings charge the card on file. Key in 3 minutes, no sales call.

# Quoting is keyless — no API key required.
curl -X POST https://www.wearewarp.com/api/v1/ltl/quote \
  -H "Content-Type: application/json" \
  -d '{
       "origin_zip": "90007",
       "destination_zip": "60601",
       "pickup_date": "2026-07-15",
       "pallets": 2,
       "weight_lbs_per_pallet": 500,
       "commodity": "general freight",
       "length_in": 48,
       "width_in": 40,
       "height_in": 48
     }'

Sample response

{
  "quote_id": "wq_01K9C2M8AB12",
  "mode": "LTL",
  "price_usd": 412,
  "currency": "USD",
  "transit_days": 3,
  "pickup_date": "2026-07-15",
  "delivery_date": "2026-07-18",
  "expires_at": "2026-07-15T17:30:00.000Z",
  "quote_tier": "firm"
}

Self-serve API keys

New customers can sign up at /agents/account, add a payment card, and receive a live wak_live_ key. Existing customers can sign in from the same flow. Quote endpoints are free; booking endpoints charge the card on file.

Webhook integrations

Webhooks are available on self-serve. Register a destination with POST /api/v1/developer/webhook { "url": "https://..." } (https only) after signing in once at /agents/account — or set it in the customer dashboard at customer.wearewarp.com → Settings → Webhook URL (under API Access) — and Warp delivers shipment-milestone events (booked → picked up → in transit → out for delivery → delivered, plus exceptions) to your URL in real time — no polling. GET reads the current URL, DELETE removes it, and POST /api/v1/developer/webhook/test fires a test delivery so you can inspect the exact payload ({ event, timestamp, data }). Events are delivered as JSON POSTs and are not signed today — verify authenticity with an unguessable secret in your registered URL and reject anything missing it; HMAC signing is planned. Calls before linking return 409 WARP_SESSION_REQUIRED.

Granular shipment statuses

Warp shipments move through granular operational statuses, not just "in transit" and "delivered." The tracking response can include statuses like:

bookedShipment confirmed

arrivedAtPickupDriver at origin

pickupSuccessfulFreight scanned in

inRouteToWarehouseEn route to cross-dock

arrivedAtWarehouseAt cross-dock facility

departedFromWarehouseLeft cross-dock

inRouteToDeliveryEn route to destination

arrivedAtDeliveryDriver at destination

deliveredPOD captured

exceptionIssue flagged by Orbit

hotSwappedCarrier reassigned

cancelledShipment cancelled

AI document extraction

Warp can support document-heavy workflows for approved accounts, including BOL and purchase order parsing. The public self-serve API should be treated as quote, book, and track today. If your workflow depends on document ingest, BOL retrieval, invoices, or portal data, talk to Warp before building against those surfaces.

Quickstart: from zero to a booked shipment

Four steps from a cold start to freight on a truck — get a key, quote (keyless), book, and track. Each call returns the ID the next one needs. The same path works for an API client, an AI agent, a TMS, or a WMS.

Get a key

wak_live_…

Self-serve at /agents/account in ~3 min. Card on file. No sales call.

Quote

keyless

POST /api/v1/ltl/quote

No key needed. Returns quote_id + price_usd in ~300 ms.

Book

POST /api/v1/book

Send quote_id + addresses. Returns shipment_id + tracking. Charges the card.

Track

GET /api/v1/track

Poll booking_id for granular live status through delivery.

Endpoint reference

Quick scan table — one line per endpoint. The tested reference above is canonical; open this for a compact overview.

MethodPathPurposeInputOutputStatus

POST/api/v1/ltl/quoteGet a keyless LTL quote (no API key required)origin_zip, destination_zip, pickup_date, pallets, weight_lbs_per_pallet, commodity, length_in, width_in, height_inquote_id (wq_…), mode, price_usd, transit_days, delivery_date, expires_at200 OK

POST/api/v1/bookBook and charge a quoted shipment (API key + card required)quote_id (wq_…), patch.pickup, patch.delivery (each accepts an optional refNum), optional reference, accessorials, pickup_window, delivery_windowbooked, shipment_id, shipment_number, order_id, tracking_number200 OK

GET/api/v1/track?booking_id={shipmentId}Track one booked shipment (live status + events)Query: booking_id = the shipment number from booking (e.g. S-199806-2617)shipment_id, status, local booking row, live upstream status, event history200 OK

GET/api/ltl-ratesRead public LTL rate dataOptional lane, origin, destination, cheapest, limit query paramsLane rates, carrier comparisons, basis, updated date200 OK

GET/POST/api/freight-answerAsk freight questions in natural languageq query param or { question } JSON bodyanswer, data, sources, related_questions200 OK

GET/api/v1/quote-historyList your past quote requestsOptional limit query paramdata[] of prior quotes with lane, mode, price, requested_at200 OK

GET/api/v1/events?shipment_id={shipmentId}Full tracking event timeline for a shipmentQuery: shipment_iddata[] with message, when, eventName200 OK

GET/api/v1/bookingsList your recent bookings (newest first)Optional limit query param (max 100)data[] of shipments with numbers, lane, status, dates200 OK

GET/api/v1/documents?order_id={orderId}BOL and proof of delivery for an orderQuery: order_id; optional type=bol|poddocuments[] with type, url, filename200 OK

GET/api/v1/invoices?order_id={orderId}Invoice breakdown for a completed orderQuery: order_idtransitCost, fuelCost, grandTotal, status200 OK

POST/api/v1/ltl/market-optionsMulti-carrier LTL quote — every carrier, each bookableSame body as /api/v1/ltl/quotemarket_options[] with carrier_name, price_usd, transit_days, bookable quote_id200 OK

GET/api/v1/lanesYour lane history (past shipments, last consignee, counts)No params (uses your API key)lanes[] with origin, destination, ship_count, last_consignee200 OK

Vehicle types

Every mode quotes keyless — LTL, FTL, cargo van, and box truck return live rates from the same instant-quote endpoints with no API key. Booking any mode runs under your API key.

CARGO_VAN

Cargo Van

Up to 3,500 lbs, 400 cu ft

Keyless self-serve quote, same as LTL — booking runs under your API key. Best for 1–3 pallets and tight-access deliveries.

STRAIGHT_TRUCK_26

26 ft Box Truck

Up to 10,000 lbs, 1,500 cu ft

Keyless self-serve quote, same as LTL — booking runs under your API key. Larger pallet counts and liftgate-heavy moves.

DRY_VAN_53

53 ft Dry Van (FTL)

Up to 44,000 lbs, 3,400 cu ft

Keyless self-serve quote, same as LTL — booking runs under your API key. Full truckload and recurring lane programs.

The API knows physics.

Impossible loads don't get prices. These run the live capacity gate — the same one the booking path enforces — so the refusal below is real system behavior, not copy.

Request and response examples

Copy-paste ready. These are the exact shapes your system or agent should send and expect back.

1. Quote a shipment

POST /api/v1/ltl/quote

{
  "origin_zip": "90001",
  "destination_zip": "10001",
  "pickup_date": "2026-07-15",
  "pallets": 2,
  "weight_lbs_per_pallet": 500,
  "commodity": "general freight",
  "length_in": 48,
  "width_in": 40,
  "height_in": 48
}

200 Response

{
  "quote_id": "wq_01JRKZ8B9ABD",
  "mode": "ltl",
  "price_usd": 247.50,
  "currency": "USD",
  "transit_days": 2,
  "pickup_date": "2026-07-15",
  "delivery_date": "2026-07-17",
  "expires_at": "2026-07-15T18:30:00.000Z"
}

2. Book the shipment

POST /api/v1/book

{
  "quote_id": "wq_01JRKZ8B9ABD",
  "reference": "PO-12345",
  "patch": {
    "pickup": {
      "company": "Sender Co",
      "contactName": "Your Name",
      "phone": "2125550100",
      "email": "you@example.com",
      "street": "123 Main St",
      "city": "Los Angeles",
      "state": "CA",
      "zipCode": "90001"
    },
    "delivery": {
      "company": "Receiver Co",
      "contactName": "Their Name",
      "phone": "2125550200",
      "email": "them@example.com",
      "street": "456 Broadway",
      "city": "New York",
      "state": "NY",
      "zipCode": "10001"
    }
  }
}

201 Response

{
  "booked": true,
  "shipment_id": "01KQAQNH9V93D92JWQ6TFM3SJK",
  "shipment_number": "S-199806-2617",
  "order_id": "01KQAQNH9V93D92JWQ6TFM3SJK",
  "tracking_number": "S-199806-2617",
  "tracking_dashboard": "https://customer.wearewarp.com"
}

3. Track the shipment

GET /api/v1/track?booking_id={shipmentId}

GET /api/v1/track?booking_id=S-199806-2617

200 Response

{
  "shipment_id": "S-199806-2617",
  "status": "inRouteToDelivery",
  "origin_zip": "90001",
  "destination_zip": "10001",
  "upstream_tracking": {
    "trackingNumber": "S-199806-2617",
    "statusInfo": {
      "status": "inRouteToDelivery",
      "lastUpdated": "2026-06-16T14:22:42.000Z"
    }
  },
  "events": [
    { "eventName": "pickupSuccessful", "when": "2026-06-16T09:02:00.000Z" }
  ]
}

Data models

Complete field reference for every object in the API. Types are TypeScript-style for clarity.

QuoteRequestRequest a free API quote

origin_zipstringRequired 5-digit US pickup ZIP code

destination_zipstringRequired 5-digit US delivery ZIP code

pickup_datestringRequired YYYY-MM-DD pickup date

palletsnumberRequired, 1-26 pallets

weight_lbs_per_palletnumberRequired, 1-5000 lbs per pallet

commoditystringRequired for a firm LTL quote

length_in / width_in / height_innumberPer-pallet dimensions in inches — required for a firm LTL quote

QuoteResponseRate returned from the quote endpoint

quote_idstringwq_… id — pass to /api/v1/book to book

price_usdnumberAll-inclusive USD rate

transit_daysnumber | nullEstimated transit time when available

delivery_datestringEstimated delivery date (YYYY-MM-DD)

expires_atstringQuote expiry (ISO 8601)

modestringReturned shipment mode

BookingAddressPickup or delivery address used when booking (nested under patch)

companystringOptional company name

streetstringRequired street address

citystringRequired city

statestringRequired 2-letter state code

zipCodestringRequired 5-digit ZIP code

contactNamestringRequired contact name

phonestringRequired contact phone

emailstringContact email (required on pickup)

refNumstringOptional reference / PO for THIS stop — renders on the stop's BOL "Reference Number" line

BookingRequestConvert a quote into a shipment and charge the card on file

quote_idstringRequired wq_… id from a quote endpoint

patch.pickupBookingAddressRequired pickup address and contact

patch.deliveryBookingAddressRequired delivery address and contact

referencestringOptional shipment-level reference; use patch.pickup.refNum / patch.delivery.refNum for a per-stop BOL reference

accessorials{ pickup[], delivery[] }Optional liftgate, residential, etc.

pickup_window / delivery_window{ from, to }Optional HH:MM time windows

BookingResponseConfirmation returned after booking

shipmentIdstringUnique shipment identifier

orderIdstringParent order identifier

trackingNumberstringFor tracking API calls

chargednumberUSD amount charged to card on file

stripePaymentIntentIdstring | nullStripe reference for production bookings

TrackingResultTracking data per shipment

okbooleanTrue when tracking lookup succeeds

trackingobjectWarp tracking payload returned by the upstream network

Accessorial services

These service codes exist in Warp's broader network API and enterprise workflows. They are not part of the public self-serve quote and book request shape until enabled for your account.

pickupServices[]

"liftgate-pickup""inside-pickup""residential-pickup""limited-access-pickup""pickup-appointment""driver-assist-pickup""drop-and-hook-pickup""convention-trade-show-pickup""construction-site-pickup""detention-shipper"

deliveryServices[]

"liftgate-delivery""inside-delivery""residential-delivery""limited-access-delivery""delivery-appointment""driver-assist-delivery""drop-and-hook-delivery""convention-trade-show-delivery""construction-site-delivery""detention-receiver""redelivery"

additionalServices[]

"sort-n-seg""extra-stop""extra-miles""driver-assist""white-glove""check_calls""notify""photo-required"

Error handling

CodeMeaningWhen

400INVALID_JSONBody wasn't valid JSON.

400INVALID_ZIPorigin/destination not a 5-digit US ZIP.

400MISSING_PICKUP_DATEpickup_date absent or not YYYY-MM-DD.

400MISSING_DIMSLTL quote without dims and no load_template_id.

400BAD_INPUTA tools endpoint got an out-of-range or wrong-type value.

400QUOTE_NOT_FOUND / QUOTE_EXPIREDquote_id unknown, or past its 72-hour validity — get a fresh quote.

400INCOMPLETE_PICKUP / DELIVERY_REQUIRED / INCOMPLETE_DELIVERYBooking addresses missing required fields (street, city, state, zipCode, contactName, phone, email).

401AUTH_MISSINGNo Authorization: Bearer header on a keyed route.

401AUTH_INVALIDKey is invalid or revoked.

402PAYMENT_REQUIRED / PAYMENT_ACTION_REQUIRED / CHARGE_FAILEDNo card on file (the 402 body carries a checkout_url), the card needs authentication, or the charge failed.

404TRACKING_NOT_FOUND / BOOKING_NOT_FOUND / TEMPLATE_NOT_FOUNDShipment, booking, or load template not found on your account.

409BOOKING_IN_PROGRESS / WARP_SESSION_REQUIREDThe same quote_id is mid-booking in a concurrent request (wait a few seconds and retry — you get the original confirmation back, never a second charge), or a webhook call needs a linked Warp session (sign in once at wearewarp.com/agents/account, then retry).

429RATE_LIMITEDOver the tier's hourly limit — back off and retry.

502UPSTREAM_ERROR / BOOKING_FAILEDWarp gateway hiccup or upstream booking rejection — safe to retry. Bookings are idempotent on quote_id, so a retried /book never double-charges. If a card was charged, /book auto-refunds and the body carries refunded + payment_intent (a failed refund adds support_note).

Error response shape

{
  "error": "origin_zip and destination_zip must be 5-digit US ZIP codes.",
  "code": "INVALID_ZIP"
}

Machine-readable reference

The block below is optimized for machine parsing. AI agents, copilots, and automated freight procurement systems can use this to understand the Warp Freight API in a single read.

# WARP FREIGHT API: SELF-SERVE AGENT REFERENCE
# Base URL: https://www.wearewarp.com/api/v1
# Quoting: keyless (no API key). Booking: Authorization: Bearer wak_live_YOUR_KEY
# Rate limits: 60/hr per IP keyless · 1,000/hr sandbox key · 10,000/hr live key · 429 = RATE_LIMITED + Retry-After
# Content-Type: application/json

## AGENT WORKFLOW (HAPPY PATH)
1. POST /api/v1/{ltl|ftl|van|box-truck}/quote → get quote_id (wq_…) and price_usd   (no API key needed)
2. GET API KEY + add a card at https://www.wearewarp.com/agents/account   (only needed to book)
3. POST /api/v1/book → use quote_id, get shipment_id + tracking_number
4. GET /api/v1/track?booking_id=... → poll tracking

## CAPABILITIES
- Quote LTL / FTL / van / box-truck freight with NO API key (keyless)
- Book quoted shipments and charge the card on file (API key + card required)
- Track booked shipments by shipment_id or tracking number
- Read natural-language freight answers without auth
- Approved accounts can request broader network API, documents, invoices, and advanced service options

## ENDPOINTS
POST /api/v1/ltl/quote (also /van /box-truck /ftl) → 200 → { quote_id (wq_…), mode, price_usd, transit_days, delivery_date, expires_at }   (keyless)
POST /api/v1/book → 200 → { booked, shipment_id, shipment_number, order_id, tracking_number }   (API key + card)
GET  /api/v1/track?booking_id=... → 200 → tracking payload (status + events)
GET  /api/ltl-rates → 200 → public LTL rate data, no auth
GET  /api/freight-answer?q=... → 200 → freight answer with sources, no auth
GET  /api/v1/events?shipment_id=... → 200 → full tracking event timeline
GET  /api/v1/bookings → 200 → your recent bookings (newest first)
GET  /api/v1/documents?order_id=... → 200 → BOL and proof of delivery
GET  /api/v1/invoices?order_id=... → 200 → invoice breakdown
POST /api/v1/ltl/market-options → 200 → multi-carrier LTL quote (each carrier bookable)
GET  /api/v1/quote-history → 200 → your past quote requests
GET  /api/v1/lanes → 200 → your lane history

## VEHICLE TYPES
All modes (LTL, FTL, VAN, BOX_TRUCK) → keyless self-serve quote
Booking (any mode) → requires your API key (Bearer)

## QUOTE BODY FIELDS
origin_zip (string, required), destination_zip (string, required),
pickup_date (YYYY-MM-DD, required), pallets (number, required),
weight_lbs_per_pallet (number, required),
commodity + length_in / width_in / height_in (required for a firm LTL quote)

## BOOK BODY FIELDS
quote_id (wq_…, required), patch.pickup (BookingAddress, required),
patch.delivery (BookingAddress, required), reference?, accessorials?, pickup_window?, delivery_window?

## BOOKING ADDRESS FIELDS
company?, street, city, state, zipCode, contactName, phone, email

## SANDBOX (TEST MODE)
wak_test_ keys: minted at signup, no card. Quote + book run production validation, byte-compatible responses, zero charges.
Sandbox bookings are ALIVE: the shipment advances booked → arrivedAtPickup → pickupSuccessful → inRouteToWarehouse → arrivedAtWarehouse → departedFromWarehouse → inRouteToDelivery → arrivedAtDelivery → delivered over ~10 minutes.
Poll GET /api/v1/track?booking_id=… (keyless for sandbox ids). BOL available via GET /api/v1/documents after pickupSuccessful; POD after delivered.
Unhappy path: pass "reference": "scenario:delay" on /book → deterministic exception event + delayed delivery.

## ERROR CODES (canonical — same catalog as the on-page tables)
400 INVALID_JSON — Body wasn't valid JSON.
400 INVALID_ZIP — origin/destination not a 5-digit US ZIP.
400 MISSING_PICKUP_DATE — pickup_date absent or not YYYY-MM-DD.
400 MISSING_DIMS — LTL quote without dims and no load_template_id.
400 BAD_INPUT — A tools endpoint got an out-of-range or wrong-type value.
400 QUOTE_NOT_FOUND | QUOTE_EXPIRED — quote_id unknown, or past its 72-hour validity — get a fresh quote.
400 INCOMPLETE_PICKUP | DELIVERY_REQUIRED | INCOMPLETE_DELIVERY — Booking addresses missing required fields (street, city, state, zipCode, contactName, phone, email).
401 AUTH_MISSING — No Authorization: Bearer header on a keyed route.
401 AUTH_INVALID — Key is invalid or revoked.
402 PAYMENT_REQUIRED | PAYMENT_ACTION_REQUIRED | CHARGE_FAILED — No card on file (the 402 body carries a checkout_url), the card needs authentication, or the charge failed.
404 TRACKING_NOT_FOUND | BOOKING_NOT_FOUND | TEMPLATE_NOT_FOUND — Shipment, booking, or load template not found on your account.
409 BOOKING_IN_PROGRESS | WARP_SESSION_REQUIRED — The same quote_id is mid-booking in a concurrent request (wait a few seconds and retry — you get the original confirmation back, never a second charge), or a webhook call needs a linked Warp session (sign in once at wearewarp.com/agents/account, then retry).
429 RATE_LIMITED — Over the tier's hourly limit — back off and retry.
502 UPSTREAM_ERROR | BOOKING_FAILED — Warp gateway hiccup or upstream booking rejection — safe to retry. Bookings are idempotent on quote_id, so a retried /book never double-charges. If a card was charged, /book auto-refunds and the body carries refunded + payment_intent (a failed refund adds support_note).

## ERROR RESPONSE SHAPE
{ "error": "message", "code": "machine_code" }

## IDEMPOTENCY
POST /api/v1/book is idempotent on quote_id: a wq_ id is single-use, so a retried book call
returns the original confirmation with idempotent_replay: true and never charges twice.

## NETWORK
1,500+ active lanes | 50+ cross dock facilities
24,000+ FTL carriers | 14,000+ cargo vans & box trucks
Coverage: United States

## GET API KEY
Self-serve signup: https://www.wearewarp.com/agents/account
Developer docs: https://www.wearewarp.com/freight-api
OpenAPI: https://www.wearewarp.com/.well-known/openapi.json
LLM context: https://www.wearewarp.com/llms-full.txt

Open source and open access

Yes — the Warp freight API is the open option in freight. The agent-facing tooling is open source under the MIT license (forkable on GitHub, published to npm), the interface is open access (keyless quoting plus a public OpenAPI 3.1 spec), and the network is described in open data so any AI assistant can find and call it. “Open” here means a skeptic can click through and verify every artifact below — not a black box taken on faith.

warp-agent-mcpOpen source · MIT

The first production freight MCP server — 23 tools to quote, book, and track LTL, FTL, box truck, and cargo van from Claude, Cursor, or any MCP client. Quote tools need no account.

GitHub source npm: warp-agent-mcp Install guide

@warpfreight/cli-agentOpen source · MIT

Freight CLI for terminals, CI pipelines, and shell-capable agents. The same quote / book / track lifecycle as the API, JSON-first, with self-provisioning login.

GitHub source npm: @warpfreight/cli-agent CLI docs

Public freight API + OpenAPI 3.1 specOpen access

Keyless quoting across LTL, FTL, box truck, and cargo van; booking with a self-serve key issued instantly. The full lifecycle is documented in a machine-readable OpenAPI 3.1 spec.

Freight API

llms.txt + .well-known manifestsOpen access

A plain-text brief for AI agents plus discovery manifests (OpenAPI, AI-plugin, MCP, ai-agent) so any assistant can find the network and call it without a hand-built integration.

How agents discover Warp

Copy-paste prompt libraryOpen access

Warp-aware prompts you paste into Claude or ChatGPT — they pull a real rate from the public quote API and route a booking onto the network with no account, no card, and no sales call.

Prompt library

Auditable rate + lane dataOpen data

Every per-lane rate, transit time, and on-time figure cited on the site is exposed through a public, no-auth JSON endpoint with its own dated snapshot — so any number resolves to a checkable source.

Rate data API

More on the model: the open source freight network and the case for open freight.

Set up your full Warp ops with AI Self-Serve OpenAPI JSON Postman Collection & Code Samples (GitHub)MCP Server for Freight Warp CLI Freight API Tutorial Freight API Response Times What is a Freight API Freight API for AI Agents Managed Freight (agent-run, done for you)3PL Partner Platform (no-code widget)Get API Key

About this guide

Maintained by the Warp Engineering team. The endpoint references on this page mirror the live OpenAPI spec at /.well-known/openapi.json and are updated whenever the API surface changes. The 2026 freight API comparison data sources from public competitor documentation as of May 2026; corrections welcome via the public repository.

Last refreshed: 2026-06-06. Credentials: SOC 2 Type II, FMCSA-Authorized Motor Carrier. Recognition: Fast Company World's Most Innovative Companies, FreightWaves FreightTech 100, ISM Supply Chain Trailblazer, EPA SmartWay Partner.

About Warp·MCP server·CLI·OpenAPI spec

Built for the next generation of freight orchestration.

Every self-serve endpoint returns structured JSON. The public path is clear enough for a human developer, TMS integration, or API-capable agent to quote, book, and track without guessing which auth model to use.

Get API Key OpenAPI JSON

Bearer auth · Structured JSON · Self-serve keys · Sandbox available

The only self-serve freight API in America.

Getting started

Quotes

Booking

Tracking

Documents & invoices

History & account

Public rate data

Tools & calculators

Errors

Webhooks

Freight quote API, answered

Freight quote API

How to quote LTL freight by API

Freight quote API for AI agents

Key capabilities

What you can build on the Warp freight API

Embed instant rates in checkout

Let an AI agent book real freight

Auto-book from warehouse events

Rate-shop the whole network

Track every shipment in detail

Pull BOL, POD & reconcile invoices

Ranked: best freight APIs for 2026

Pick the right freight API for the job

Call the network by component

Or do it from your editor

The sandbox is alive

Run it in production

LTL via the Warp API

FTL via the Warp API

Box truck via the Warp API

Cargo van via the Warp API

FAQ

Integration patterns

Authentication

Quote and book in your language

Your shipment

Self-serve API keys

Webhook integrations

Granular shipment statuses

AI document extraction

Quickstart: from zero to a booked shipment

Get a key

Quote

Book

Track

Endpoint reference

Vehicle types

Request and response examples

Data models

Accessorial services

Error handling

Machine-readable reference

Open source and open access

Related pages

About this guide

Built for the next generation of freight orchestration.