The only self-serve freight API in America.

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.

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.

Last refreshed: 2026-05-19. 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 have already booked elsewhere and need post-tender visibility. 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.

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/freight/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.

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.

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/freight/book charges the card on file.

Cargo van via the Warp API

Cargo van quotes use the unified POST /api/v1/freight/quote endpoint with mode="VAN". There is no dedicated /cargo-van/quote endpoint — cargo van shares the multi-mode quote surface. Pass origin and destination ZIPs, pickup date, and shipment details; the response returns quoteId, carrier, rate, transit days, and the 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. Cargo van is available for approved production workflows; the public self-serve default remains LTL.

FAQ

Integration patterns

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.

curl -X POST https://www.wearewarp.com/api/v1/freight/quote \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer wak_live_YOUR_KEY" \
  -d '{
    "pickupZip": "90001",
    "deliveryZip": "10001",
    "pickupDate": "2026-06-15",
    "pallets": 2,
    "weightPerPallet": 500
  }'

Try the API

Edit the inputs and copy working code in cURL, Python, JavaScript, TypeScript, or Go. Run it with a production key — get one in 60 seconds.

# Get a production key first: https://www.wearewarp.com/agents/account
curl -X POST https://www.wearewarp.com/api/v1/freight/quote \
  -H "Authorization: Bearer wak_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "pickupZip": "90007",
       "deliveryZip": "60601",
       "pickupDate": "2026-06-15",
       "pallets": 2,
       "weightPerPallet": 500
     }'

{
  "ok": true,
  "quotes": [
    {
      "quoteId": "PRICING_01K9_AB12",
      "carrier": "Warp",
      "rate": 412,
      "transitDays": 3,
      "mode": "LTL"
    }
  ]
}

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 not part of the public self-serve API yet. Use GET /api/v1/freight/track/{shipmentId} to poll shipment status after booking. Enterprise and approved-account integrations can request event push workflows through Warp, but those should not be treated as self-serve copy-paste endpoints until they are enabled on your account.

Granular shipment statuses

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

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.

Agent quickstart

Three calls from quote to tracking. This is the self-serve happy path for an API client, AI agent, TMS, WMS, or internal tool. Each step returns the ID needed for the next call.

Endpoint reference

Vehicle types

The public self-serve path is LTL-first. Additional vehicle workflows are available for approved production accounts and should be confirmed before launch.

Request and response examples

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

{
  "pickupZip": "90001",
  "deliveryZip": "10001",
  "pickupDate": "2026-06-15",
  "pallets": 2,
  "weightPerPallet": 500
}

{
  "ok": true,
  "quotes": [{
    "quoteId": "PRICING_abc123",
    "carrier": "Warp Technology",
    "rate": 247.50,
    "transitDays": 2,
    "mode": "LTL"
  }]
}

{
  "quoteId": "PRICING_abc123",
  "pickupDate": "2026-06-15",
  "pallets": 2,
  "weightPerPallet": 500,
  "pickup": {
    "company": "Sender Co",
    "contact": "Your Name",
    "phone": "2125550100",
    "email": "you@example.com",
    "street": "123 Main St",
    "city": "Los Angeles",
    "state": "CA",
    "zip": "90001"
  },
  "delivery": {
    "company": "Receiver Co",
    "contact": "Their Name",
    "phone": "2125550200",
    "email": "them@example.com",
    "street": "456 Broadway",
    "city": "New York",
    "state": "NY",
    "zip": "10001"
  }
}

{
  "ok": true,
  "trackingNumber": "S-199806-2617",
  "orderId": "01KQAQNH9V93D92JWQ6TFM3SJK",
  "shipmentId": "01KQAQNH9V93D92JWQ6TFM3SJK",
  "charged": 247.50,
  "stripePaymentIntentId": "pi_..."
}

GET /api/v1/freight/track/S-199806-2617

{
  "ok": true,
  "tracking": {
    "trackingNumber": "S-199806-2617",
    "statusInfo": {
      "status": "inRouteToDropoff",
      "lastUpdated": "2026-06-16T14:22:42.000Z"
    }
  }
}

Data models

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

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.

Error handling

{
  "error": "pickupZip, deliveryZip, pickupDate, pallets, and weightPerPallet are required.",
  "code": "BAD_REQUEST"
}

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
# Auth: Authorization: Bearer wak_live_YOUR_KEY
# Content-Type: application/json

## AGENT WORKFLOW (HAPPY PATH)
1. GET API KEY at https://www.wearewarp.com/agents/account
2. POST /api/v1/freight/quote → get quoteId and rate
3. POST /api/v1/freight/book → use quoteId, get shipmentId + trackingNumber
4. GET /api/v1/freight/track/{shipmentId} → poll tracking payload

## CAPABILITIES
- Quote self-serve LTL freight with a Bearer API key
- Book quoted shipments and charge the card on file
- Track booked shipments by shipmentId or tracking number
- Read public LTL rate data and natural language freight answers without auth
- Approved accounts can request broader network API, documents, invoices, and advanced service options

## ENDPOINTS
POST /api/v1/freight/quote → 200 → { ok, quotes: [{ quoteId, carrier, rate, transitDays, mode }] }
POST /api/v1/freight/book → 200 → { ok, trackingNumber, orderId, shipmentId, charged }
GET  /api/v1/freight/track/{shipmentId} → 200 → { ok, tracking }
GET  /api/ltl-rates → 200 → public LTL rate data, no auth
GET  /api/freight-answer?q=... → 200 → freight answer with sources, no auth
POST /api/v1/warp/freights/tracking → 200 → live status + location for one or more shipments
GET  /api/v1/warp/freights/events/{shipmentId} → 200 → full event timeline
GET  /api/v1/warp/freights/shipments → 200 → paginated shipment list
GET  /api/v1/warp/freights/documents/{orderId} → 200 → BOL and proof of delivery
GET  /api/v1/warp/freights/invoices/{orderId} → 200 → invoice breakdown
POST /api/v1/warp/freights/freight-quote → 200 → multi-carrier quote options
POST /api/v1/warp/freights/quote → 200 → raw Warp quote with FTL and accessorial support

## VEHICLE TYPES
LTL → public self-serve default
FTL, VAN, BOX_TRUCK → approved production workflows; confirm before launch

## QUOTE BODY FIELDS
pickupZip (string, required), deliveryZip (string, required),
pickupDate (YYYY-MM-DD, required), pallets (number, required),
weightPerPallet (number, required), mode? ("LTL"|"FTL"|"VAN"|"BOX_TRUCK")

## BOOK BODY FIELDS
quoteId (string, required), pickup (BookingAddress, required),
delivery (BookingAddress, required), pickupDate?, pallets?, weightPerPallet?, promoCode?

## BOOKING ADDRESS FIELDS
company?, street, city, state, zip, contact, phone, email

## ERROR CODES
200 OK, 400 Bad Request, 401 Unauthorized, 402 No Card/Card Declined,
404 Not Found, 429 Rate Limited, 500/502 Upstream or Server Error

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

## NETWORK
1,500+ active lanes | 50+ cross dock facilities
20,000+ carriers | 9,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