Integrations Catalog

Connects to the freight stack you already run.

Routevein integrates with your TMS, ELD, carrier network, and broker API — via EDI 204/990/214/210 or REST. Your TMS stays in place. Routevein plugs in as the optimization layer. We don't require a middleware platform, an iPaaS subscription, or a systems integrator to connect. Most integrations go live in 1–3 days.

TMS Core

Transportation Management Systems

Oracle OTM

TMS Core

EDI: 204 / 990 / 214 / 210

Connection: Native API connector + AS2 EDI

MercuryGate TMS

TMS Core

EDI: 204 / 990 / 214 / 210

Connection: Native API connector + SFTP EDI

McLeod Software

TMS Core

EDI: 204 / 990 / 214

Connection: REST API + AS2 EDI

TMW Suite

TMS Core

EDI: 204 / 990 / 214

Connection: REST API + SFTP EDI

ELD & HOS

Electronic Logging Devices

Samsara

ELD & HOS

Data: Real-time HOS cycle state, driver location

Connection: Samsara Fleet API (REST/webhook)

Motive (KeepTruckin)

ELD & HOS

Data: Driver HOS logs, drive time remaining

Connection: Motive API (REST)

Geotab

ELD & HOS

Data: HOS exceptions, vehicle telematics

Connection: Geotab MyAdmin SDK

Carrier Networks

Visibility & Tender Routing

project44

Carrier Network

Data: Real-time shipment tracking, ETA predictions

Connection: project44 API (REST)

MacroPoint

Carrier Network

Data: GPS-based load tracking

Connection: MacroPoint REST API

Broker APIs

Rate Shopping & Auto-tender

Uber Freight

Broker API

Data: Spot rate quotes, lane capacity

Connection: Uber Freight API (REST)

Loadsmart

Broker API

Data: Instant FTL/LTL pricing, auto-tender

Connection: Loadsmart API (REST)

Echo Global Logistics

Broker API

Data: LTL consolidation rates

Connection: Echo API (REST)

API Reference

REST API

Routevein exposes a REST API for programmatic access to the VRP solver. Bearer token auth, JSON request/response. POST a stop list with time windows, vehicle constraints, and HOS parameters — receive an optimized route plan in under 90 seconds. EDI and REST are not mutually exclusive: most deployments use both.

# POST /v1/routes/optimize
# Authorization: Bearer <api_token>
# Content-Type: application/json

{
  "depot": { "lat": 41.877, "lng": -87.636 },
  "vehicles": [
    { "id": "TRK-001", "capacity_lbs": 44000,
      "driver_id": "DRV-0041" }
  ],
  "stops": [
    { "id": "STOP-01", "lat": 41.923,
      "lng": -87.691,
      "window_open": "08:00",
      "window_close": "10:30",
      "service_min": 30 }
  ],
  "constraints": { "hos_enforce": true }
}
Request API Access