REST API · Webhooks · Every plan

Freight tracking API for brokers' own systems

Create a load from your TMS and CarrierView texts the driver a tracking link. Read status, live positions and history back over REST, and get new positions pushed to your endpoint by webhook. Tracking runs through the driver's phone — no ELD integration.

See the quickstart

API access is included on every plan, including Free.

POST /api/loads

REST

{
  "load_id": "48213",
  "driver_phone": "+15551234567",
  "mc_number": "882140",
  "locations": [
    { "type": "pickup",
      "address": "Dallas, TX",
      "dateFrom": "2026-10-06 08:00",
      "dateTo": "2026-10-06 12:00" },
    { "type": "destination",
      "address": "Memphis, TN",
      "dateFrom": "2026-10-07 08:00",
      "dateTo": "2026-10-07 17:00" }
  ]
}
// driver gets a text with the tracking link

What the API does

Load tracking, from your own software

Keep the CarrierView dashboard, or never open it: the same loads, positions and messages are available to your TMS, customer portal or BI over a token-authenticated REST API.

Create

Start tracking when the load is booked

POST /api/loads with the driver's phone and the stops; the driver gets a text with a link to the free driver app or an app-less browser tracker.

Read

Status, positions and history

List loads (active, future, past), read one load with its stops and arrival times, its last position, or its full position history.

Push

Webhooks to your endpoint

Every new position and every driver chat message arrives as a POST, plus events for loads added or edited in the dashboard and for deleted loads.

Quickstart

From token to tracked load in four calls

Get a token

Create a load

POST /api/loads with Authorization: Bearer <token>. Store the id from the response.

Read it back

GET /api/loads/{id} for status and stops, or /last-position and /positions-history.

Add webhooks

Profile → Webhooks, or PUT /api/webhook/new-position-sent with your webhook_url.

What comes back

Responses and webhook payloads, trimmed

Every response wraps its data as {"success": true, "data": …}. The full field reference is in the Documentation page of your dashboard after sign-up.

GET /api/loads/18342

{
  "success": true,
  "data": {
    "id": 18342,
    "load_id": "48213",
    "client_url": "https://carrierview.com/client/loads/18342?…",
    "route_started": true,
    "track_driver": { "phone": "+15551234567", "last_request_time_utc": 1791366300, … },
    "locations": [ { "type": "pickup", "arrived": true, "arrived_utc": 1791295200, … }, … ],
    "last_position": { "latitude": 34.75, "longitude": -92.29, "created_at_utc": 1791366300, … }
  }
}

webhook → your endpoint

// new position — POST to your new-position URL
{
  "load": { "id": 18342, "load_id": "48213", … },
  "position": {
    "latitude": 34.75,
    "longitude": -92.29,
    "address": "I-40 E, Little Rock, AR",
    "late_secs": 0,
    "created_at_utc": 1791366300
  }
}

Before you go live

Integration notes worth knowing

Send the token as a Bearer header. Keep it out of URLs and logs.
60 requests per minute. Over the limit you get HTTP 429; the driver text-message endpoint allows 5 per minute.
Check success, not only the status code. Validation and permission errors come back as success: false with an error_code.
Creating a load isn't idempotent. Each successful call creates a load and texts the driver — store the returned id and don't retry blindly.
Webhooks are one POST each, with a short timeout and no signature. Answer fast, treat them as notifications and reconcile by reading the load.
PATCH /api/loads/{id} replaces values. Send the full emails, dispatchers and MC number you want kept.

Pricing

Public pricing, from $0

API access is included on every plan, including Free. Plans are priced by simultaneous active tracks — no per-call or per-load fees.

Free — $0

1 active track

Base — $100/mo

10 active tracks

Pro — $200/mo

30 active tracks

Enterprise — $500/mo

100 active tracks

No per-load fees, no demo wall, no contract. See full pricing →

FAQ

Freight tracking API, answered

Is there a freight tracking API for freight brokers?

Yes. CarrierView's REST API lets a broker's TMS or portal create loads, read each load's tracking status, last position and position history, and message the driver — and webhooks push new positions and driver chat messages to your endpoint. Tracking itself runs through the driver's phone, by app or app-less browser link.

How do I get an API key?

Sign up, then generate an API token in your profile (Profile → API Token). Tokens belong to a manager or admin user with a verified email. Send the token in the Authorization header as a Bearer token.

Does the driver need to install an app for API-created loads?

No. When you create a load, the driver gets a text message with a link: they can install the free CarrierView Driver app or track straight from the phone's browser with nothing installed.

Which webhooks does the API send?

Three, each with one URL per company: every new position, every chat message from the driver, and load events — loads added or edited in the web dashboard, and deleted loads. For tracking progress on API-created loads, use the new-position webhook or poll the load.

What does the API cost?

API access is included on every plan, including Free. Plans are priced by active tracks: Free $0 (1), Base $100/mo (10), Pro $200/mo (30), Enterprise $500/mo (100) — no per-call or per-load fees.

Get started

Track your next load free

No demo required. The Free plan includes one active track — try CarrierView on a real load before you roll it out to the team.

See pricing

Prefer to talk first?