Getting started with Driver API

Driver API uses the same API-token exchange as the rest of the MendriX REST API — if you’ve already set up authentication for another integration, you can reuse the same token and login flow here. See Authentication for the full flow; the short version:

1. Create an API token in the TMS (Custom Link dialog → Api Tokens).
2. Exchange it for a short-lived access token at POST /account/login-api-token.
3. Send Authorization: Bearer ACCESS_TOKEN on every Driver API call.

One driver/operator at a time

An API token is scoped to your administration/client data as a whole, not to any single driver — it has no built-in notion of “which driver.” Most Driver API endpoints (tasks, planning, rides) return data for one operator, selected with an operatorId query parameter.

Polling multiple drivers

If you manage devices for several drivers, call the same endpoint once per operatorId — there’s no single call that returns tasks for every operator at once. Keep a list of the operator Ids your integration is responsible for and loop over it.

Retrieve tasks for one operator

Manual (curl)

BASE="https://<your-client-name>.api.mendrix.cloud/api"
API_TOKEN="$MENDRIX_API_TOKEN"          # never hard-code secrets
OPERATOR_ID="104"                       # the operator/driver you want

# 1. Log in with the API token
ACCESS_TOKEN=$(curl -s -X POST "$BASE/account/login-api-token" \
  -H "Content-Type: application/json" \
  -d "{\"token\": \"$API_TOKEN\"}" \
  | jq -r '.data.items[0].access')

# 2. Retrieve this operator's planned tasks
curl "$BASE/driver-api/tasks/?operatorId=$OPERATOR_ID" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Accept: application/json"

n8n

1. API credentials (Set node or n8n credential) — store your API token.
2. Login (HTTP Request node) — POST {{BASE}}/account/login-api-token with { "token": "..." }, extract data.items[0].access.
3. Get tasks (HTTP Request node) — GET {{BASE}}/driver-api/tasks/ with query parameter operatorId set to the driver you want, and header Authorization: Bearer {{ $json.access }}.

Looping over multiple operators

To poll several drivers on a schedule, add a Split In Batches (or Loop Over Items) node feeding a list of operator Ids into the “Get tasks” call, one operatorId per iteration.

Next steps

• Browse every endpoint in the interactive reference — rides, goods, tracking positions, chat, packaging, and questionnaires all follow the same auth and operatorId pattern.
• See Authentication for token lifetime, revocation, and refresh.