Freight API: Quote, book, track, settle.

Key capabilities

• -Quote freight programmatically. Get rates for LTL, FTL, cargo van, and box truck in one call.
• -Book shipments and receive tracking numbers without leaving your system.
• -Track every shipment in real time. Pull event history, invoices, and proof of delivery.
• -Omit the vehicle type and Warp selects the right asset for your freight automatically.

Integration patterns

Authentication

All requests require an API key passed as a header. Content type is always JSON. Base URL is the same for all endpoints.

curl -X POST https://api.wearewarp.com/api/v1/freights/quote \
  -H "Content-Type: application/json" \
  -H "apikey: YOUR_API_KEY" \
  -d '{
    "pickupDate": ["2026-03-15"],
    "pickupInfo": { "zipCode": "90001" },
    "deliveryInfo": { "zipCode": "85001" },
    "listItems": [{
      "name": "Pallet",
      "length": 48, "width": 40, "height": 48,
      "sizeUnit": "in",
      "totalWeight": 800, "weightUnit": "lb",
      "quantity": 2, "packaging": "pallet"
    }]
  }'

Self-serve API keys

Generate API keys directly from the developer section of your Warp dashboard, no sales call required. Each key is scoped to your organization and can be rotated or revoked at any time. For enterprise accounts with multiple teams, create separate keys per integration (TMS, WMS, internal tools) with independent rate limits and audit trails.

Webhook integrations

Instead of polling the tracking endpoint, register webhook URLs in your Warp dashboard and receive real-time status events pushed directly to your TMS, WMS, or ERP. Warp pushes events as shipments move through each status, from booked through arrivedAtPickup, pickupSuccessful, inRouteToWarehouse, arrivedAtWarehouse, departedFromWarehouse, arrivedAtDelivery, to delivered, each with timestamps, GPS coordinates, and scan data. Webhook payloads include the full event object so your system can update status, trigger alerts, and close out orders without any manual intervention.

Granular shipment statuses

Every Warp shipment moves through 12+ granular statuses, not just "in transit" and "delivered." Your system receives each status change with timestamps and GPS coordinates:

AI document extraction

For teams processing hundreds of BOLs, purchase orders, and shipping documents weekly, Warp's AI extraction engine auto-parses uploaded PDFs and populates order fields automatically: origin, destination, item dimensions, weight, reference numbers, and service requirements. No manual data entry. The extraction templates learn your document formats over time, and every auto-parsed order goes through a review step before booking. API-based document submission is available for teams that want to automate the entire ingest-to-book workflow: upload a PDF to the document endpoint, receive structured order data back, and book it programmatically.

Agent quickstart

Five calls from quote to proof of delivery. This is the happy-path workflow for an AI agent or automated system. Each step returns the IDs needed for the next call.

Endpoint reference

Vehicle types

Three vehicle codes. Warp picks the right one if you omit it.

Request and response examples

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

{
  "pickupDate": ["2026-03-15"],
  "pickupInfo": {
    "zipCode": "90001",
    "city": "Los Angeles",
    "state": "CA",
    "street": "123 Warehouse Blvd",
    "contactName": "Dispatch Team",
    "phone": "3105551234"
  },
  "deliveryInfo": {
    "zipCode": "85001",
    "city": "Phoenix",
    "state": "AZ",
    "street": "456 Distribution Dr",
    "contactName": "Receiving Dock",
    "phone": "6025551234"
  },
  "listItems": [{
    "name": "Pallet - Retail Goods",
    "length": 48, "width": 40, "height": 48,
    "sizeUnit": "in",
    "totalWeight": 800, "weightUnit": "lb",
    "quantity": 2,
    "packaging": "pallet",
    "stackable": false
  }],
  "shipmentType": "LTL"
}

{
  "data": {
    "quoteId": "01HG9W6CMAWHNWTVXDKW9QYFS9",
    "carrierCode": "WTCH",
    "carrierName": "Warp Technology",
    "serviceLevel": "standard",
    "transitDays": 2,
    "totalCost": 485.00,
    "pickupWindow": { "from": "08:00", "to": "17:00" },
    "deliveryWindow": { "from": "08:00", "to": "17:00" }
  }
}

{
  "quoteId": "01HG9W6CMAWHNWTVXDKW9QYFS9",
  "pickupInfo": {
    "zipCode": "90001",
    "city": "Los Angeles",
    "state": "CA",
    "street": "123 Warehouse Blvd",
    "contactName": "Dispatch Team",
    "phone": "3105551234",
    "specialInstruction": "Dock 4, call 30 min before arrival"
  },
  "deliveryInfo": {
    "zipCode": "85001",
    "city": "Phoenix",
    "state": "AZ",
    "street": "456 Distribution Dr",
    "contactName": "Receiving Dock",
    "phone": "6025551234",
    "specialInstruction": "Receiving hours 7am-3pm"
  },
  "listItems": [{
    "name": "Pallet - Retail Goods",
    "length": 48, "width": 40, "height": 48,
    "sizeUnit": "in",
    "totalWeight": 800, "weightUnit": "lb",
    "quantity": 2,
    "packaging": "pallet",
    "stackable": false
  }],
  "deliveryServices": ["delivery-appointment"]
}

{
  "data": {
    "shipmentId": "shp_01HGA2K9MNPQ4RV8XW3YZ5TJ6",
    "shipmentNumber": "WRP-2026-031542",
    "orderId": "ord_01HGA2K9MNPQ4RV8XW3YZ5TK7",
    "trackingNumber": "WARP1234567890",
    "shipmentType": "LTL",
    "status": "CONFIRMED"
  }
}

{
  "trackingNumbers": ["WARP1234567890"]
}

{
  "data": [{
    "trackingNumber": "WARP1234567890",
    "status": "IN_TRANSIT",
    "currentLocation": {
      "city": "Barstow",
      "state": "CA",
      "timestamp": "2026-03-16T08:42:00Z"
    },
    "estimatedDelivery": "2026-03-17T14:00:00Z",
    "events": [
      {
        "status": "PICKED_UP",
        "location": "Los Angeles, CA",
        "timestamp": "2026-03-15T10:15:00Z",
        "description": "Freight picked up from origin"
      },
      {
        "status": "IN_TRANSIT",
        "location": "Barstow, CA",
        "timestamp": "2026-03-16T08:42:00Z",
        "description": "In transit to destination"
      }
    ]
  }]
}

Data models

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

Accessorial services

Pass these string values in the pickupServices, deliveryServices, or additionalServices arrays on your quote or booking request.

Error handling

{
  "error": {
    "code": "INVALID_REQUEST",
    "message": "pickupInfo.zipCode is required",
    "details": [
      { "field": "pickupInfo.zipCode", "issue": "required" }
    ]
  }
}

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: AGENT REFERENCE
# Base URL: https://api.wearewarp.com/api/v1
# Auth: Header "apikey: <your-api-key>"
# Content-Type: application/json

## AGENT WORKFLOW (HAPPY PATH)
1. POST /freights/quote → get quoteId and totalCost
2. POST /freights/booking → use quoteId, get shipmentId + trackingNumber
3. POST /freights/tracking → poll status using trackingNumber
4. GET /freights/events/{shipmentId} → full event history
5. GET /freights/invoices/{orderId} → settlement data
6. GET /freights/documents/{orderId} → BOL, POD files

## CAPABILITIES
- Quote freight (LTL, FTL, cargo van, box truck) in one API call
- Book shipments programmatically with tracking number returned
- Track shipment status and location in real time
- Retrieve invoices and documents (BOL, POD) by order ID
- Multi-stop FTL quoting and booking
- 20+ accessorial services priced at quote time
- Vehicle type auto-selection when vehicleType is omitted

## ENDPOINTS
POST /freights/quote → 200 → { quoteId, carrierCode, serviceLevel, transitDays, totalCost }
POST /freights/booking → 201 → { shipmentId, trackingNumber, orderId, status }
POST /freights/tracking → 200 → [{ trackingNumber, status, currentLocation, events }]
GET  /freights/shipments → 200 → [{ shipmentId, shipmentType, status, pickupInfo, deliveryInfo }]
GET  /freights/events/{shipmentId} → 200 → [{ status, location, timestamp, description }]
GET  /freights/invoices/{orderId} → 200 → { lineItems, totals, charges }
GET  /freights/documents/{orderId} → 200 → [{ type, url, metadata }]
POST /freights/quote/multi-stops → 200 → { quoteId, totalCost, stops }
POST /freights/booking/multi-stops → 201 → { shipmentId, trackingNumber }
GET  /freights/quote-history → 200 → [{ quoteId, totalCost, status, expiresAt }]

## VEHICLE TYPES
CARGO_VAN → Cargo van (urgent, <3500 lbs, fastest dispatch)
STRAIGHT_TRUCK_26 → 26ft box truck (<10000 lbs, white-glove capable)
DRY_VAN_53 → 53ft dry van / FTL (<44000 lbs, recurring lanes)

## SHIPMENT TYPES
LTL → Less-than-truckload (pallet freight, cross dock network)
FTL → Full truckload (dedicated trailer, direct lanes)
omit → Warp auto-selects based on item dimensions and weight

## QUOTE BODY FIELDS
pickupDate (string[]), pickupInfo (StopInfo), deliveryInfo (StopInfo),
listItems (BookShipmentItem[]), shipmentType? ("LTL"|"FTL"),
vehicleType? ("CARGO_VAN"|"STRAIGHT_TRUCK_26"|"DRY_VAN_53"),
pickupServices? (string[]), deliveryServices? (string[]),
additionalServices? (string[])

## STOP INFO FIELDS
zipCode, city, state, street, contactName, phone, email?, specialInstruction?, window?

## ITEM FIELDS (BookShipmentItem)
name, length, width, height, sizeUnit ("in"|"cm"),
totalWeight, weightUnit ("lb"|"kg"), quantity,
packaging, stackable (bool), temperature_limit?

## PICKUP SERVICES
"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"

## DELIVERY SERVICES
"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"

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

## ERROR CODES
200 OK, 201 Created, 400 Bad Request, 401 Unauthorized,
403 Forbidden, 404 Not Found, 422 Unprocessable, 429 Rate Limited, 500 Server Error

## ERROR RESPONSE SHAPE
{ "error": { "code": "string", "message": "string", "details": [{ "field": "string", "issue": "string" }] } }

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

## GET API KEY
Contact: https://www.wearewarp.com/book-a-meeting
Full docs: https://developer.wearewarp.com/docs/freight/
LLM context: https://www.wearewarp.com/llms-full.txt