#Mertrack API

Telematics API for fleet and asset tracking. The Mertrack API is a JSON-over-HTTP interface to the Mertrack telematics platform. Everything the web portal can do — read positions and tracks, manage devices and geofences, generate reports, run field-service workflows — is available here as a plain POST call.

Getting startedMake your first call in five minutes. AuthenticationSession hashes and long-lived API keys. Backend APIFormats, data types, conventions. Endpoint indexEvery call, alphabetically.

#Base URL

Every call is made against a single base URL:

https://api.mergroup.be

The full URL of a call is the base URL plus the call path, for example https://api.mergroup.be/tracker/list.

#Quick start

#Get a session hash

Authenticate with the same credentials you use for the portal. The response contains a hash that authenticates every subsequent call.

curl -X POST 'https://api.mergroup.be/user/auth' \
    -H 'Content-Type: application/json' \
    -d '{"login": "you@example.com", "password": "your_password"}'

{
  "success": true,
  "hash": "22eac1c27af4be7b9d04da2ce1af111b"
}

For production integrations, create an API key instead — it does not expire and survives password changes. See Authentication.

#List your objects

curl -X POST 'https://api.mergroup.be/tracker/list' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b"}'

{
  "success": true,
  "list": [
    {
      "id": 123456,
      "label": "1-ABC-123",
      "group_id": 0,
      "source": {
        "id": 234567,
        "device_id": "352093087326913",
        "model": "telfmb920",
        "blocked": false
      }
    }
  ]
}

The id you get here is the tracker_id used by nearly every other call.

#Read where an object is

curl -X POST 'https://api.mergroup.be/tracker/get_state' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "tracker_id": 123456}'

https://api.mergroup.be/tracker/get_state?hash=22eac1c27af4be7b9d04da2ce1af111b&tracker_id=123456

#Request and response conventions

Transport — POST with a JSON body is the recommended form. application/x-www-form-urlencoded and GET with query parameters are also accepted; use GET only for read-only calls with small parameters.
Authentication — pass hash as a parameter, or send the header Authorization: NVX <hash>.
Responses — always application/json, including for errors. Success responses carry "success": true.
Errors — failures carry "success": false and a status object with a numeric code. See error codes.
Compatibility — new fields are added over time. Ignore fields your client does not know, and treat missing fields as null.

{
  "success": false,
  "status": {
    "code": 102,
    "description": "Wrong login or password"
  }
}

#What you can build

Data retrievalTracks, points, sensor readings and reports. Device managementRegister devices, send commands, read BLE tags. Places & geofencesZones, POIs and place-based logic. Rules & notificationsAlerts, push messages and event history. Fleet managementVehicles, drivers, service works and tags. Field serviceTasks, forms and check-ins for mobile teams. WebSocketLive positions and events without polling. Full referenceEvery resource, parameter and error.

#Support

Questions about access, rate limits or a specific integration: support@mergroup.be.