A device is a physical tracker identified by IMEI or serial number. Each device becomes a vehicle (veh_…) for the Tracking API; replacing a faulty tracker keeps the vehicle.
| Endpoint | Purpose | Scope |
|---|---|---|
GET /devices | List devices. Filters: identifier, fleet_id, customer_id, service_status and more. | devices.read |
POST /devices | Register your own (BYOD) device: identifier_type (imei/serial), identifier, manufacturer and model (as listed in Supported devices), optional fleet_id, label, registration_plate, vin. | devices.write |
GET /devices/{id} · PATCH /devices/{id} | Read a device (ownership, fleet, service, connectivity, SIM) or update its vehicle identity. | devices.read · devices.write |
POST /device-claims · GET /device-claims/{id} | Claim a supplied device with evidence (order reference); reviewed by Fleetalyse. | devices.write · devices.read |
Identifiers
- IMEI: digits only; 14 digits get the Luhn check digit added, 15 digits must pass the Luhn check. Spaces and dashes are removed.
- Serial numbers: upper-cased, spaces and dashes removed.
- An identifier can have one active owner per mode. Registering one that is already owned elsewhere answers
409 CONFLICTwithout saying by whom.
Ownership states
| State | Meaning |
|---|---|
pending_verification | Waiting for Fleetalyse checks (claims, identifiers already known elsewhere). |
verified | Yours; can be activated. |
rejected / released / transferred | Not (or no longer) yours. Tracking data for those periods stays with the owner at the time. |
Service state, connectivity (online/offline/unknown, refreshed about every 5 minutes) and SIM state are separate fields — a vehicle can be offline and still have an active, charged service.
Check your models against Supported devices before you sell a service.