Setting a Driver List in Device Manager
Written by Sean Withers
Updated at April 23rd, 2026
Table of Contents
Set the Driver List
The Set the Driver List API call sends a list of valid Driver ID codes to a device. The device checks this list when a Driver ID tag or code is presented, which allows the asset to respond only to authorised drivers.
This is commonly used as part of a broader Driver ID and immobilisation workflow. Depending on device configuration, the device can buzz until a valid Driver ID is scanned, or only toggle its output when a valid Driver ID is presented. For the wider workflow, see Driver ID and Immobilization with Powered Devices.
Support Documentation:
You can also set the Driver List by CSV import in the Device Manager web app under Device Operations > Set Drivers.
The API returns true when the request is valid.
Required Fields
The request requires the following fields:
- ID Type (1 = DMRFID, 2 = iButton, 7 = Wiegand)
- IdData
- Flags
- Layout
IdData Format
The IdData field must use one of the following formats:
-
DMRFID (1) - serial must contain 5 bytes (10 hex characters).
-
iButton (2) - serial must contain 5 to 6 bytes (typically 12 hex characters).
- Wiegand (7) - serial must include the bit length as the first byte.
If you are choosing a reader type or tag format, see Driver ID Options.
Example cURL
curl -X POST 'https://api.oemserver.com/v1.0/driverlist/set/310056' -H 'Authorization: Basic user/pass' -H 'Content-Type: application/json' --data-raw '{"Drivers":[{"IdType":7,"IdData":"FBI0UA==","Flags":"01"},{"IdType":1,"IdData":"001CB70A7B","Flags":"01"}],"Layout":0}'In this example, the payload sends two drivers and specifies the layout used for the Driver List.
Driver List Memory Allocation and Limits
Maximum Number of Drivers per Layout
All Digital Matter devices allocate a fixed 128 kB (131,072 bytes) partition for storing the Driver List. The maximum number of drivers that can be stored depends on the selected layout:
| Layout | Bytes per Entry | Max Drivers |
|---|---|---|
| Short | 8 bytes | 16,375 |
| Long | 32 bytes | 4,093 |
| Short + Name | 40 bytes | 3,275 |
Driver List Memory and GPS Logging
The number of drivers stored in the Driver List does not affect how many GPS records a device can store while it is out of coverage.
Driver List data and GPS log data are stored in separate fixed memory partitions. Because these partitions are independent, adding or removing drivers does not reduce the space available for trip history or GPS records.
When the Driver List Partition Is Full
If the Driver List reaches its storage limit:
- Additional drivers beyond the allocated partition size are not saved.
- Write attempts beyond the partition boundary are ignored automatically by the device.
- The list is effectively truncated once it reaches its defined storage limit.
This means the request may still be accepted, but entries beyond the device limit will not be retained.
Next Steps
For the broader installation and immobilisation workflow, see Driver ID and Immobilization with Powered Devices. To compare supported reader and tag types, see Driver ID Options. If you also manage drivers in Telematics Guru, see Driver Management in TG.
