Trax Public API

Trax Public API

Your fleet's data — vehicles, drivers, trips, safety events, maintenance and more — as clean JSON you can read (and write, where allowed) over HTTPS. One login, one predictable response shape, 117 operations.

Start in 5 minutes API Reference OpenAPI spec

In plain words

What this is

The Trax Public API hands you your fleet's data as JSON. You ask for what you want — list my devices, trips for this vehicle last week, this month's safety events — over ordinary HTTPS, and get it back in a consistent shape.

You only ever see your own company's data. Access is by OAuth credentials Zenduit issues you; every request is automatically scoped to your company, so there is no way to read another tenant's records.

There are two ways to use it. Developers call it directly from code or a tool like Postman. Everyone else can let an AI assistant do the calling — the same data, asked in plain language.

Read + write JSON · snake_case 117 operations Tenant-isolated

5-minute quickstart

From zero to your first answer

Base URL for this environment: https://trax-public-api.zendu.one/v1

1. Get credentials

Credentials (a client_id / client_secret pair) are issued by Zenduit — not self-service. Ask your Zenduit representative for API access and the scopes your integration needs.

2. Trade them for a token

Request

curl -sS 'https://service-prod.zendu.one/Public/OAuth/Token' \
  -d grant_type=client_credentials \
  -d client_id=<client_id> \
  -d client_secret=<client_secret> \
  -d scope='devices:read trips:read'

Response

{
  "access_token": "eyJhbGciOiJ…",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "devices:read trips:read"
}

The token lasts about an hour. Send it as Authorization: Bearer <token> on every call.

3. Make your first call

Request

curl -sS 'https://trax-public-api.zendu.one/v1/devices?limit=2' \
  -H 'Authorization: Bearer <token>'

Response

{
  "data": [
    { "id": "3f2b8c…", "name": "Truck 12",
      "status": "active", "is_ignition_on": true,
      "speed_kmh": 82.4 },
    { "id": "9a71de…", "name": "Van 4",
      "status": "active", "is_ignition_on": false,
      "speed_kmh": 0 }
  ],
  "meta": { "request_id": "req_8kd2", "count": 2,
    "has_more": true, "next_cursor": "eyJpZCI6…" }
}

Every response has the same two parts: data (what you asked for) and meta (a request id, and for lists the paging info). That's it — you're in. Try a recipe next.

Recipes

Things you can actually ask

Real questions, the request that answers each, and what comes back. Using an AI assistant? The bold question is basically your prompt. (Values below are illustrative.)

Which vehicles are out on the road right now?

List devices and read ignition + speed to see what's moving.

Request

GET https://trax-public-api.zendu.one/v1/devices
  ?fields=name,is_ignition_on,speed_kmh,last_known_location

Response

{ "data": [
  { "name": "Truck 12", "is_ignition_on": true,
    "speed_kmh": 82.4,
    "last_known_location": { "lat": 43.6529, "lng": -79.3849 } },
  { "name": "Van 4", "is_ignition_on": false, "speed_kmh": 0,
    "last_known_location": { "lat": 43.6487, "lng": -79.3853 } }
], "meta": { "count": 2, "has_more": true } }

Show a vehicle's trips from last week

You have a name, not an id — resolve it first, then window the trips.

Request

# 1) find the vehicle by name
GET https://trax-public-api.zendu.one/v1/devices?name=Truck%2012&fields=name

# 2) list its trips for a date range
GET https://trax-public-api.zendu.one/v1/trips
  ?device_id=3f2b8c…&from=2026-09-01&to=2026-09-08

Response (step 2)

{ "data": [
  { "id": "t_5521", "device_id": "3f2b8c…",
    "driver_id": "d_88",
    "start_time": "2026-09-02T13:14:05Z",
    "end_time": "2026-09-02T14:02:41Z",
    "distance_km": 47.3, "max_speed_kmh": 96.1 }
], "meta": { "count": 1, "has_more": false } }

What safety events happened this week?

List safety events in a date window; each links a device, driver and rule.

Request

GET https://trax-public-api.zendu.one/v1/safety-events
  ?from=2026-09-08&to=2026-09-11

Response

{ "data": [
  { "id": "se_2290", "device_id": "3f2b8c…",
    "driver_id": "d_88", "rule_id": "r_harsh_brake",
    "status": "reviewed",
    "occurred_at": "2026-09-09T08:41:22Z",
    "speed_kmh": 61.0 }
], "meta": { "count": 1, "has_more": false } }

What maintenance is on the books?

List maintenance requests; add ?status= to filter to the state you care about.

Request

GET https://trax-public-api.zendu.one/v1/maintenance-requests?limit=1

Response

{ "data": [
  { "id": "mr_431", "service_number": "WO-10231",
    "status": "open", "odometer_km": 184250,
    "total_cost": 512.40,
    "created_at": "2026-09-05T16:00:00Z" }
], "meta": { "count": 1, "has_more": true } }

How did a driver do last month?

Fetch a driver's aggregated summary over a date range — no trip-by-trip math.

Request

GET https://trax-public-api.zendu.one/v1/summaries/driver/d_88
  ?from=2026-08-01&to=2026-08-31

Response

{ "data": {
  "driver_id": "d_88", "driver_name": "A. Rivera",
  "distance_km": 3184.7, "avg_speed_kmh": 54.2,
  "avg_trip_dist_km": 22.1, "after_hours_pct": 6.4
}, "meta": { "request_id": "req_9f0e" } }
Core concepts

The handful of things worth knowing

Pagination

Lists return up to ?limit= rows (default 100, max 1000). For the next page, pass the previous response's meta.next_cursor back as ?cursor=; meta.has_more tells you when to stop.

GET https://trax-public-api.zendu.one/v1/trips?limit=100
# → meta.next_cursor: "eyJpZCI6…", meta.has_more: true
GET https://trax-public-api.zendu.one/v1/trips?limit=100&cursor=eyJpZCI6…

Fields

Each resource returns a sensible default set of fields. Ask for more with a comma-separated ?fields= — only allow-listed fields are ever returned, so internal columns never leak.

Include

Some resources can expand a related resource inline with ?include= (e.g. ?include=groups on devices), saving a second round trip.

Filtering & resolving names

Filter lists by the fields a resource supports (?device_id=, ?status=, …). Ids aren't human-friendly, so if you only have a name, resolve it first: devices, zones and groups filter by ?name=; drivers by ?username=. Trips, safety events, locations and summaries only accept ids — so it's a two-step lookup (see the trips recipe above).

Date windows & caps

Date-based lists (trips, safety events, maintenance, diagnostics, locations, IFTA) default to the last 30 days when from/to are both omitted, and most cap a single range at 31 days — ask for more and you get a 400; page through longer spans yourself.

Errors

Every error uses the same shape, with a request_id you can quote to support:

{ "error": { "code": "not_found", "message": "…", "request_id": "req_…" } }

Rate limiting

Requests are rate-limited per client. Over the limit you get 429 with a Retry-After header plus X-RateLimit-* counters — wait the stated seconds and retry.

Scopes

Each credential is granted a set of scopes, and every endpoint states the one it needs. Omit scope when fetching a token to receive everything your client is allowed.

devices:readRead devices and their live status
devices:writeCreate devices, update device metadata, and assign/remove drivers
drivers:readRead drivers
drivers:writeCreate, update and delete drivers, and reset a driver's password
trips:readRead trips
safety:readRead safety events
coaching:readRead driver coaching sessions
rules:readRead rules
zones:readRead zones / geofences
zones:writeCreate, update and delete geofence zones
groups:readRead groups
groups:writeCreate, update and delete groups
faults:readRead vehicle faults and the fault-code catalog
maintenance:readRead maintenance requests and repair orders
maintenance:writeCreate, update and cancel maintenance requests and repair orders
diagnostics:readRead diagnostic readings
locations:readRead historical vehicle locations
forms:readRead forms, submissions and schedules
forms:writeDeactivate forms; send (dispatch) a form to drivers/groups
products:readRead products
products:writeCreate, update and delete products
jobs:readRead dispatch jobs
jobs:writeCreate dispatch jobs; update job metadata; delete dispatch jobs
summaries:readRead driver and vehicle summaries
ifta:readRead IFTA / state-mileage summaries
files:readGet a download URL for an uploaded file
files:writeUpload files
media:readRead camera media — live/historical stream URLs, recordings, and media task status
media:writeRequest camera media (video/snapshot jobs) and wake devices
geocoding:readReverse-geocode coordinates to addresses and the company's containing zones
tts:writeSend a text-to-speech audio message to StreamMax cameras

Environments

The environments this API is available in (all /v1-prefixed). The examples on this page automatically use the host you're viewing them on.

Productionhttps://trax-public-api.zendu.one/v1
Devhttps://trax-public-api-dev.zendu.one/v1
No code

Use it with an AI assistant

Every read endpoint here is also exposed as a tool on our MCP server, so you can point Claude, n8n, or any MCP-capable assistant at your fleet and just ask — "which vehicles need service?", "who had harsh-braking events this week?" — no code required. The assistant makes the calls; your data stays scoped to your company.

MCP setup guide →

Reference map

Everything you can access

Grouped by area. Full field-level detail for each resource — every field, filter and relationship — lives in the Entity Reference.

Vehicles & devices3 resources
  • DevicesYour vehicles and trackers — identity and status.Fields →
  • Device statusWhere a vehicle is right now — position, speed, ignition.Fields →
  • Tracker typesThe hardware-model catalog.Fields →
People2 resources
  • DriversYour drivers (credentials never exposed).Fields →
  • UsersAll platform users; filter to just drivers.Fields →
Trips & telematics3 resources
  • TripsCompleted trips — distance, duration, speed.Fields →
  • LocationsHistorical breadcrumbs for a vehicle.Fields →
  • DiagnosticsSensor / telemetry time-series.Fields →
Safety5 resources
  • Safety eventsHarsh-driving and rule violations.Fields →
  • Coaching sessionsAI and manual driver coaching deliveries.Fields →
  • RulesThe safety-rule definitions behind those events.Fields →
  • ZonesGeofences used to scope location rules.Fields →
  • CommentsNotes attached to records (often safety events).Fields →
Maintenance & faults4 resources
  • Maintenance requestsVehicle service requests.Fields →
  • Repair ordersRepair orders with curated totals.Fields →
  • Vehicle faultsFaults raised on a device, with triage state.Fields →
  • Fault codesThe shared diagnostic-code catalog.Fields →
Dispatch & field ops5 resources
Analytics2 resources
  • Driver & vehicle summariesAggregated rollups over a date range.Fields →
  • IFTA summariesDistance by vehicle × jurisdiction × month.Fields →
Organization & maps2 resources
  • GroupsThe hierarchy that scopes everything else.Fields →
  • Custom mapsIndoor / web map overlays.Fields →
Media & utilities3 resources
  • Media (video & camera)Live / historical streams, recordings, clip requests.Fields →
  • GeocodingTurn coordinates into an address and zone.Fields →
  • Text-to-SpeechSend a spoken message to a device.Fields →