LogoDispatch
API v2.4 · 99.97% uptime · All systems operational

ship.rate()→$4.23ship.book()→PRO#882741ship.track()→IN_TRANSIT

One API. Every carrier. Zero portals.

RESTful endpoints that let logistics teams rate, book, track, and settle freight without ever touching a portal. Built for the engineers wiring shipment logic into ERPs.

Explore the Docs
87msAvg Response
150+Carrier Coverage
99.97%Uptime SLA
< 1 dayAvg Integration

Connected Carriers & Partners

Samsara·
project44·
FedEx·
UPS·
USPS·
Echo·
XPO·
Samsara·
project44·
FedEx·
UPS·
USPS·
Echo·
XPO·

// competitive_analysis.json

Why engineering teams
choose the API path.

Legacy TMS platforms were built for dispatchers, not developers. Dispatch was built for engineers who need freight in production, not a portal to click through.

Capability
DISPATCHAPI-first
Legacy TMSManual Broker
Integration Time
< 1 dayvs 6 months
3–6 months
6–12 months
Carrier Coverage
150+ carrierslive
20–40 carriers
1–5 carriers
Rate Shopping Speed
87ms avgp99 < 200ms
3–8 seconds
Hours / phone
Real-Time Tracking
Webhook pushevent-driven
Polling only
Manual check
Settlement Automation
Automated
Partial
Manual
EDI Replacement
REST + Webhooks
EDI required
EDI required
API-First Architecture
Native
Portal-first
None
Uptime SLA
99.97%guaranteed
99.5%
N/A

Ready to ditch the portal?

Get your API key and ship your first rate request in under 10 minutes.

// live_integration.sh

Real code.
Real response.

This isn't a demo sandbox. Every snippet below is a live API call against production. Copy, paste, ship.

Avg response time

87ms

Rate from 150+ carriers simultaneously
Book and get PRO# in one call
Webhook-push tracking events
Automated freight settlement
dispatch.sh/v2
1# Rate a shipment — ship.rate()
2curl -X POST https://api.dispatch.sh/v2/rate \
3  -H "Authorization: Bearer dk_live_xxxxx" \
4  -H "Content-Type: application/json" \
5  -d '{
6    "origin": { "zip": "90210", "country": "US" },
7    "destination": { "zip": "10001", "country": "US" },
8    "weight_lbs": 142,
9    "dims": { "l": 24, "w": 18, "h": 12 },
10    "service_levels": ["GROUND", "EXPRESS_2D"]
11  }'
12
13# Response — 200 OK · 87ms
14{
15  "request_id": "req_9f2a1b3c",
16  "rates": [
17    { "carrier": "FedEx", "service": "GROUND",      "amount": 4.23, "currency": "USD", "transit_days": 5 },
18    { "carrier": "UPS",   "service": "EXPRESS_2D",  "amount": 18.91, "currency": "USD", "transit_days": 2 }
19  ]
20}
1█

// performance_metrics.json

Production speed,
not demo speed.

Average API response time

0ms

Across all carrier rating calls · Last 30 days

Uptime

0.00%

Carriers

0+

Endpoint Latency
Endpointp50p95p99
ship.rate()64ms142ms198ms
ship.book()91ms187ms244ms
ship.track()38ms79ms112ms
ship.settle()103ms201ms289ms

Time to first shipment

From zero to production freight. Measured in reality, not marketing copy.

Legacy TMS
24 weeks

Portal setup, EDI mapping, carrier onboarding

Custom Integration
12 weeks

Internal eng team, carrier APIs, error handling

Dispatch APIrecommended
7 hours

npm install, configure, ship first rate call

06 weeks12 weeks24 weeks

One engineer. One afternoon. Production freight.

Install the SDK, set your API key, make a rate call. No carrier contracts to negotiate, no EDI mapping sessions, no portal training. Just a 200 OK and a list of rates.

// ready_to_ship.sh

Your first 200 OK
is one afternoon away.

Stop scheduling portal demos. Stop waiting for carrier onboarding. Get an API key, make a rate call, and have freight in production before end of day.

Explore the Docs
🔒SOC 2 Type II
⚡Free tier · No CC
📦150+ carriers
🌐99.97% uptime SLA