Shipping platform
Add Freight Shipping to Your Platform
Your users need to ship freight. You don't want to become a freight company. Warp's API lets you embed quoting, booking, and tracking into your platform. Your users get freight capabilities. You get a new revenue stream. Nobody builds carrier integrations.
3 API calls from quote to tracking number · White label ready · Cargo van, box truck, LTL, FTL
Why platforms add freight
Shopify turned parcel shipping into a platform feature. Nobody has done this well for freight. The opportunity is wide open.
New revenue stream
Take a margin on every shipment.
You call the Warp API and get all inclusive rates. Add your margin. Charge your users. The difference is pure revenue. Every user who ships through your platform generates recurring freight revenue for you.
Stickier product
Shipping is a daily workflow.
When your users book freight inside your platform every day, switching costs go through the roof. Shipping data, tracking history, carrier preferences, all locked into your product. Churn drops.
Competitive advantage
Your competitors do not have this.
Most SaaS platforms in logistics, warehousing, and e-commerce punt on freight. They tell users to call a broker. You can offer quoting, booking, and tracking natively. That is a feature your competitors cannot match without building what you are about to embed.
How to embed freight in your platform
Three integration patterns. Each one is a single API call. Your frontend stays yours. Warp handles carrier management, dispatching, cross docking, and settlement behind the scenes.
1. Embedded quoting
Your user enters origin, destination, and cargo details in your UI. Your backend calls the Warp quoting API. Rates come back instantly. You add your margin and display them. Your user never leaves your platform.
Your backend calls POST /freights/quote
// Your user enters origin, destination, cargo in YOUR UI.
// Your backend calls Warp API. Returns rates instantly.
const response = await fetch(
"https://api.wearewarp.com/api/v1/freights/quote",
{
method: "POST",
headers: {
"Content-Type": "application/json",
"apikey": process.env.WARP_API_KEY
},
body: JSON.stringify({
pickupDate: ["2025-06-10"],
pickupInfo: {
zipCode: "90001",
city: "Los Angeles",
state: "CA"
},
deliveryInfo: {
zipCode: "85001",
city: "Phoenix",
state: "AZ"
},
listItems: [{
name: "Pallet",
length: 48, width: 40, height: 48,
sizeUnit: "in",
totalWeight: 800, weightUnit: "lb",
quantity: 2, packaging: "pallet"
}]
})
}
);
const { data } = await response.json();
// data.quoteId, data.totalCost, data.transitDays
// Show these rates in YOUR platform UI.
// Add your margin before displaying to your user.2. Embedded booking
Your user selects a rate. Your backend calls the Warp booking API with the quote ID. A tracking number comes back. Your user sees a confirmed shipment in your platform. Warp dispatches the carrier.
Your backend calls POST /freights/booking
// Your user selects a rate. Your backend books it.
const booking = await fetch(
"https://api.wearewarp.com/api/v1/freights/booking",
{
method: "POST",
headers: {
"Content-Type": "application/json",
"apikey": process.env.WARP_API_KEY
},
body: JSON.stringify({
quoteId: data.quoteId,
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",
length: 48, width: 40, height: 48,
sizeUnit: "in",
totalWeight: 800, weightUnit: "lb",
quantity: 2, packaging: "pallet"
}]
})
}
);
const shipment = await booking.json();
// shipment.data.trackingNumber → show to your user
// shipment.data.shipmentId → store in your database3. Embedded tracking
Webhook events flow from Warp to your platform in real time. Your user sees live tracking, status updates, and delivery confirmation inside your product. No polling. No manual status checks.
Warp pushes events to your webhook endpoint
// Warp pushes status events to YOUR webhook endpoint.
// Your users see live tracking without you polling anything.
app.post("/webhooks/warp", (req, res) => {
const event = req.body;
// event.status: "pickupSuccessful", "inRouteToDelivery",
// "arrivedAtDelivery", "delivered", etc.
// event.trackingNumber: matches the shipment
// event.location: { city, state, timestamp }
// event.documents: BOL, POD URLs when available
// Update your platform's shipment record
await db.shipments.update({
where: { trackingNumber: event.trackingNumber },
data: {
status: event.status,
lastLocation: event.location,
updatedAt: new Date()
}
});
// Notify your user in real time
await notify(shipment.userId, {
message: `Shipment ${event.trackingNumber}: ${event.status}`
});
res.status(200).send("ok");
});Who is doing this
Platform companies across logistics and commerce are embedding freight as a native feature. Here are the patterns we see.
E-commerce platforms
Freight for B2B orders.
Parcel shipping is solved. But when your merchants sell pallets, crates, or oversized goods, they need LTL and FTL. Embed freight quoting and booking so your B2B sellers can ship heavy goods without leaving your marketplace.
WMS vendors
Outbound shipping from the warehouse.
When an order is packed and staged, your WMS can trigger a freight booking automatically. Tracking numbers flow back into the warehouse record. No separate TMS needed. No manual broker calls.
ERP systems
Logistics inside the business system.
Purchase orders, inventory, and financials already live in your ERP. Add freight shipping so your users can book a carrier, track delivery, and reconcile invoices without switching tools.
Marketplace platforms
Connect buyers and carriers.
Your marketplace connects buyers and sellers. Add freight so buyers can get instant shipping quotes at checkout, book the move, and track delivery. You take a margin on every transaction.
Revenue model
Simple economics. You call the Warp API and get all inclusive rates that cover carrier cost, fuel, insurance, and cross docking. Add your margin. Charge your users whatever you want. You pay Warp the base rate. The spread is yours.
Step 1
Get the Warp rate.
POST /freights/quote returns an all inclusive price. This is your cost basis. It includes carrier, fuel, cross dock fees, and insurance.
Step 2
Add your margin.
Mark up the rate before showing it to your user. 10%, 20%, flat fee, whatever your business model calls for. Warp does not see or control your markup.
Step 3
Charge your user.
Your user pays you. You pay Warp the base rate. The difference is revenue. Every shipment your users book through your platform generates margin for you.
The network underneath
When your platform calls the Warp API, it taps into a real freight network. Not a rate aggregator. Not a load board wrapper. A network with physical infrastructure, local 3rd-party carriers, cross dock facilities, and an AI backbone called Orbit that handles dispatching, exception management, and carrier selection.
Physical infrastructure
50+ cross dock facilities.
1,500+ active lanes across the United States. LTL freight moves through Warp cross docks for consolidation and linehaul optimization. FTL and final mile move direct.
Carrier network
20,000+ local 3rd-party carriers.
9,000+ cargo vans and box trucks for final mile. Regional and national carriers for linehaul. Every carrier is vetted, insured, and performance tracked.
Our AI backbone, Orbit
Automated dispatching and exception handling.
Orbit matches freight to carriers, optimizes routes, detects exceptions before they become problems, and hot swaps carriers when needed. Your platform gets reliable freight execution without managing any of it.
Frequently asked questions
How do I embed freight shipping into my SaaS platform?
Call the Warp quoting API from your backend when your user needs a freight rate. Display rates in your own UI. When they book, call the Warp booking API. Webhook events push tracking updates to your platform automatically. Your users never leave your product.
Can I add a margin on freight rates and charge my users?
Yes. You call the Warp API and receive all inclusive rates. Add your margin before displaying rates to your users. You charge your users whatever you want. You pay Warp the base rate. The difference is your revenue.
Can I white label the freight shipping experience?
Yes. Warp is a headless freight API. Your users interact with your UI, your brand, your workflows. Warp handles carrier management, dispatching, tracking, and settlement behind the scenes. Your users never see the Warp brand unless you want them to.
What freight modes does the Warp API support?
Cargo van, 26 ft box truck, LTL (less than truckload), and FTL (full truckload). Omit the vehicle type in your API call and Warp auto selects the right asset based on item dimensions and weight.
What does the integration look like for my users?
Your users enter origin, destination, and cargo details in your platform. They see freight rates, select one, and book. They track shipments and receive delivery confirmation, all inside your product. The Warp API handles everything behind the scenes: carrier selection, dispatching, cross docking, and proof of delivery.
Your platform. Freight built in. Revenue from day one.
Three API calls. White label ready. Your users get freight shipping. You get a new revenue stream. Warp handles the carriers, the cross docks, and the exceptions.
1,500+ lanes · 50+ cross docks · 20,000+ carriers · Cargo van, box truck, LTL, FTL