The open source freight API
Most freight APIs are gated behind broker relationships. Rates come from opaque carrier contracts. Documentation requires NDA sign-off. Warp's freight API is publicly documented, openly accessible, and built on transparent all-inclusive pricing. Quote, book, and track freight with standard REST calls — no broker margin, no EDI, no gatekeeping.
Why most freight APIs are not actually open
Freight technology has an access problem. Carrier APIs require established business relationships and volume commitments before they give you credentials. Broker APIs often surface rates with hidden margin baked in — you see a number but not what the carrier actually charges. EDI integrations require specialized translation software, VAN subscriptions, and months of setup.
An open freight API should work the way public APIs work in other industries: documented, accessible, and honest about what things cost. Warp's API is that. The OpenAPI specification is public. Rates are all-inclusive with no hidden fees. Any developer can start building without a sales call.
Quote freight with a single API call
The quote endpoint accepts origin ZIP, destination ZIP, pallet count, and weight. It returns all-inclusive rates across LTL, box truck, and cargo van with transit times and booking tokens.
curl
curl -X POST https://api.wearewarp.com/api/v1/freights/quote \
-H "Authorization: Bearer $WARP_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"originZip": "90001",
"destZip": "85001",
"pallets": 2,
"weightLbs": 800
}'CLI for terminal and scripted workflows
The Warp CLI wraps the REST API for shell-based workflows, CI/CD pipelines, and AI coding tools. Install via npm, authenticate once.
terminal
$ warp quote --origin 90001 --dest 85001 --pallets 2 --weight 800 MODE RATE TRANSIT TOKEN LTL $485.00 2 days qt_01HG9W6CMA...
Open vs. closed: what the API difference means in practice
Traditional broker API
Opaque by design.
Rates include broker margin. Documentation requires NDA. Access requires volume commitments. Integration projects run 3–6 months. Carrier data stays inside the broker's system.
EDI carrier integration
Built for batch, not real-time.
Asynchronous file exchange. Requires EDI translation software, AS2 or VAN connections, and carrier-specific mapping. Quotes take hours, not milliseconds.
Warp API
Open and synchronous.
Public docs, transparent pricing, JSON responses. Quote in under 200ms. Book instantly. Webhooks for every scan event. Works with any HTTP client. No broker margin.
What you can build on the Warp API
The API covers the full freight lifecycle: quoting, booking, tracking, invoices, documents, and exceptions. Common integration patterns:
TMS integration
Connect your platform.
Push Warp rates into your existing TMS alongside legacy carriers. Shippers see Warp options at booking without changing their workflow.
E-commerce checkout
Real-time freight rates.
Pull per-pallet LTL rates at checkout for B2B orders. Show all-inclusive pricing with no hidden surcharges added after delivery.
AI agent
Freight-aware LLMs.
The Warp MCP server connects Claude Code, Cursor, and any MCP-compatible AI tool directly to the freight network. Ship freight with natural language.
Related pages
Frequently asked questions
Is the Warp freight API open source?
Warp's REST API is publicly documented with no registration wall, no gatekeeping, and no forced broker relationship. The API specification is public (OpenAPI format). The server-side implementation is proprietary, but everything a developer needs to build on the API is openly accessible.
What can I do with the Warp freight API?
Quote freight across LTL, FTL, box truck, and cargo van. Book shipments programmatically. Get real-time tracking with webhook events for every scan. Pull invoices, BOLs, and proof of delivery documents. All via standard REST with JSON responses.
How is the Warp API different from an EDI freight integration?
EDI is asynchronous, batch-oriented, and requires specialized translation software. Warp's REST API is synchronous, returns structured JSON, and works with any HTTP client. Quotes come back in under 200ms. Booking confirms instantly. No AS2, no VAN, no EDI mapping software required.
Do I need a freight broker relationship to use the API?
No. The Warp API gives you direct access to the freight network — no broker in the middle extracting margin. Rates are all-inclusive with no hidden fees. You see exactly what freight costs, and that price does not change after pickup.
Is there a CLI in addition to the REST API?
Yes. The Warp CLI wraps the REST API for terminal-based and scripted workflows. Install via npm, authenticate once, and run freight operations from the command line. Works in CI/CD pipelines and is compatible with AI coding tools like Claude Code and Cursor.
How do I get started with the Warp freight API?
Full documentation is at developer.wearewarp.com. The quickstart walks through your first quote and booking with curl, Python, and Node.js in under 5 minutes.