FMS APIs

https://www.fmsdocumentation.com/apis/
Admin
FMS APIs provide a comprehensive set of REST API endpoints for managing fleet operations including...
Tokens:65,805
Snippets:507
Trust Score:6.3
Update:5 months ago
Show doc for...
Tokens:
Raw
### Example Get Last Assignation by ObjectID

Source: https://www.fmsdocumentation.com/apis/driver-assignations-api

An example of a request to get the last driver assignation for a specific object, including a sample API key.

```http
GET /driver/assignations/last?version=1&byObjectId=7bf8990c-dba6-11e9-bdfc-1ff21de66015&api_key=L6fwb1xODwA95qF7ybXJ4S2cSM49h1Wj
HOST: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

--------------------------------

### Geozones List API Request Example

Source: https://www.fmsdocumentation.com/apis/geozones-list-api

Demonstrates the structure of a GET request to the Geozones List API, including required and optional parameters like api_key, version, limit, and continuation_token.

```http
GET /geozones?api_key=<...>&version=1&limit=<...>&continuation_token=<...> HTTP/1.1
Host: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

--------------------------------

### Example Get Last Assignation by DriverID

Source: https://www.fmsdocumentation.com/apis/driver-assignations-api

An example of a request to get the last driver assignation for a specific driver, including a sample API key.

```http
GET /driver/assignations/last?version=1&byDriverId=240afea1-84ae-43ec-8139-f13cfa2f3094&api_key=L6fwb1xODwA95qF7ybXJ4S2cSM49h1Wj
HOST: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

--------------------------------

### GET All Objects Groups Response Example

Source: https://www.fmsdocumentation.com/apis/objects-groups-api/get-objects-groups-api

This is an example of the response structure when retrieving all object groups. It includes a `continuation_token` for further pagination and an `items` array containing details of each group.

```json
{
    "continuation_token": 1,
    "items": [
        {
            "id": "id12312ds32",
            "name": "name",
            "objects_ids": [
                "dfdasdf564asdf",
                "jhggf+hj564gf6",
                "dsaf45d6asd546"
            ]
        },
        ...
    ]
}
```

--------------------------------

### Specific Driver Response Example - JSON

Source: https://www.fmsdocumentation.com/apis/driver-api-v2

This is an example of a JSON response when requesting information for a specific driver. Parameters without values will return 'null'.

```json
{
    "id": "ABC123",
    "first_name": "Driver",
    "last_name": null,
    "address": "Lithuania, Vilnius",
    "phone": "+3700000000",
    "identifiers": [
        {
            "identifier": "343234323432342",
            "type": "DLT"
        },
        {
            "identifier": "123456789",
            "type": "TACHOGRAPH"
        },
        {
            "identifier": "3AC64785D2FF",
            "type": "WIRELESS"
        },
        {
            "identifier": "123456789",
            "type": "IBUTTON"
        }
    ]
}
```

--------------------------------

### GET Request by Object - Full Example

Source: https://www.fmsdocumentation.com/apis/ecodriving-api

Use this endpoint to retrieve ecodriving data for a specific object. Ensure you provide a valid object ID, API key, and the desired time range.

```http
GET /ecodriving/object?id=<...>&version=<...>&api_key=<...>from_datetime=<...>&to_datetime=<...> HTTP/1.1
Host: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

--------------------------------

### Driver API v2 Response Example

Source: https://www.fmsdocumentation.com/apis/driver-api-v2

This is an example of a successful response when requesting driver data. It includes a count of drivers, a continuation token for pagination, and an array of driver items, each with their details and identifiers.

```json
{
"count": 100, 
"continuation_token": 123,
"items": [
    {
    "id": "ABC123",
    "first_name": "Driver",
    "last_name": null,
    "address": "Lithuania, Vilnius",
    "phone": "+3700000000",
    "identifiers": [
        {
            "identifier": "343234323432342",
            "type": "DLT"
        },
        {
            "identifier": "123456789",
            "type": "TACHOGRAPH"
        },
        {
            "identifier": "3AC64785D2FF",
            "type": "WIRELESS"
        },
        {
            "identifier": "123456789",
            "type": "IBUTTON"
        }
    ]
    },
...
]
}
```

--------------------------------

### GET Request by Driver - Full Example

Source: https://www.fmsdocumentation.com/apis/ecodriving-api

Use this endpoint to retrieve ecodriving data for a specific driver. Ensure you provide a valid driver ID, API key, and the desired time range.

```http
GET /ecodriving/driver?id=<...>&version=<...>&api_key=<...>from_datetime=<...>&to_datetime=<...> HTTP/1.1
Host: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

--------------------------------

### Creating Drivers

Source: https://www.fmsdocumentation.com/apis/driver-management-api

This section describes how to create a new driver and provides examples of potential validation errors.

```APIDOC
## Creating Drivers

This endpoint is used to create a new driver. It accepts driver details in the request body. Validation errors may occur if the provided data does not meet the specified criteria.

### Request Body Example (Illustrative - actual request body not provided in source)
```json
{
  "firstName": "John",
  "lastName": "Doe",
  "phone": "1234567890",
  "identifiers": [
    { "identifier": "some_ibutton_id", "type": "IBUTTON" },
    { "identifier": "some_tachograph_id", "type": "TACHOGRAPH" }
  ]
}
```

### Response Examples

#### Validation Failed (422)
This response indicates that the provided data failed validation. The `fieldValidationErrors` array details the specific fields and reasons for failure.

```json
{
    "code": 422,
    "message": "Validation failed, see 'fieldValidationErrors' for more details",
    "field_validation_errors": [
        {
            "field": "phone",
            "reason": "size must be between 0 and 30",
            "rejected_value": "13245678903216549870123456789032123212321"
        },
        {
            "field": "identifiers",
            "reason": "length for IBUTTON must be between 1 and 20",
            "rejected_value": "[identifier: 1351465465413241324134135135135135413.2132463521321525555, type: IBUTTON]"
        },
        {
            "field": "firstName",
            "reason": "must not be empty",
            "rejected_value": "<null value>"
        }
    ]
}
```

```json
{
    "code": 422,
    "message": "Validation failed, see 'fieldValidationErrors' for more details",
    "field_validation_errors": [
        {
            "field": "identifiers",
            "reason": "There can only be one entry for each identifier type.",
            "rejected_value": "[{ identifier: abc, type: IBUTTON }, { identifier: fgs, type: IBUTTON }, { identifier: 1234567A, type: IBUTTON }, { identifier: 1234567A1234567A, type: TACHOGRAPH }, { identifier: 1234567A1234F, type: TACHOGRAPH }]"
        }
    ]
}
```

### Error Parameters

Parameter| Description  
---|---  
code| Validation error code  
Possible values:  
409 - another driver with the same identifier already exists  
422 - the value is invalid  
message| Error message:  
Possible values:  
Another driver with identifier [] already exists (error code 409)  
Validation failed, see 'fieldValidationErrors' for more details (error code 422)  
field_validation_errors| Array for validation errors  
field| The field with invalid value(s)  
reason| Why the value is invalid. Refer to the parameter description for accepted parameter value ranges.  
rejected_value| The rejected value(s)  
```

--------------------------------

### Fuel Events API Request Example

Source: https://www.fmsdocumentation.com/apis/fuel-events-api

This is an example of a GET request to the fuel-events endpoint. Ensure you replace placeholders like <..> with actual values. The API has limitations on request rate and the maximum period for data retrieval.

```http
GET fuel-events?object_id=<..>&from_datetime=<..>&to_datetime=<..>&version=1&api_key=<..>&limit=<..>&continuation_token=<..> HTTP/1.1
Host: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

--------------------------------

### Get All Objects

Source: https://www.fmsdocumentation.com/apis/object-api

Retrieves information for all existing client objects.

```APIDOC
## GET /objects

### Description
Retrieves a list of all existing client objects.

### Method
GET

### Endpoint
/objects

### Parameters
#### Query Parameters
- **version** (String) - Required - Version of the API, currently only version=1 is available.
- **api_key** (String) - Required - User identification key.

### Request Example
```
GET /objects?version=1&api_key=<your_api_key>
```

### Response
#### Success Response (200)
- **id** (String) - Object identifier.
- **name** (String) - Visible vehicle name.
- **imei** (String) - Vehicle hardware IMEI code.
- **vehicle_params** (Object) - Contains vehicle-specific parameters.
  - **vin** (String) - VIN of object.
  - **make** (String) - Vehicle brand.
  - **model** (String) - Vehicle brand model.
  - **plate_number** (String) - Plate number of object.

#### Response Example
```json
[
    {
        "id": "abc123",
        "name": "AAA 000",
        "imei": "123456789123",
        "vehicle_params": {
            "vin": null,
            "make": null,
            "model": null,
            "plate_number": null
        }
    },
    {
        "id": "def456",
        "name": "BBB 111",
        "imei": "987654321098",
        "vehicle_params": {
            "vin": "XYZ123",
            "make": "Toyota",
            "model": "Camry",
            "plate_number": "ABC-123"
        }
    }
]
```
```

--------------------------------

### Trips API Request Example

Source: https://www.fmsdocumentation.com/apis/trips-api

This is an example of a GET request to the Trips API. Ensure all required parameters like objectId, version, and api_key are provided. Date-time formats should strictly follow the ISO 8601 standard.

```http
GET /objects/{objectId}/trips?version=1&from_datetime=<..>&to_datetime=<..>&continuation_token=<..>&limit=<..>&api_key=<..> HTTP/1.1
HOST:api.fm-track.com
Content-Type:application/json;charset=UTF-8
```

--------------------------------

### GET Objects Group by ID Response Example

Source: https://www.fmsdocumentation.com/apis/objects-groups-api/get-objects-groups-api

Example response for retrieving a single object group by its ID. The response contains the group's `id`, `name`, and a list of `objects_ids` belonging to that group.

```json
{
    "id": "id12312ds32",
    "name": "name",
    "objects_ids": [
        "dfdasdf564asdf",
        "jhggf+hj564gf6",
        "dsaf45d6asd546"
    ]
}
```

--------------------------------

### Create Driver Response Example

Source: https://www.fmsdocumentation.com/apis/driver-management-api

A successful response when creating a driver includes the unique driver ID and all provided details.

```json
{
    "id": "ABC123",
    "first_name": "Driver",
    "last_name": "McDriver",
    "address": "Lithuania, Vilnius",
    "phone": "+3700000000",
    "identifiers": [
        {
            "identifier": "343234323432342",
            "type": "DLT"
        },
        {
            "identifier": "0123456789",
            "type": "TACHOGRAPH"
        },
        {
            "identifier": "3AC64785D2FF",
            "type": "WIRELESS"
        },
        {
            "identifier": "123456789",
            "type": "IBUTTON"
        }
    ]
}
```

--------------------------------

### GET Request for Driver Time Table Report

Source: https://www.fmsdocumentation.com/apis/driver-time-table-report-api

This is the base GET request structure for fetching driver time table data. Ensure all required parameters are correctly formatted.

```http
GET /drivertimetable/{type}-{identifier}?api_key=<..>&time_range_year=<..>&timezone=<..>&time_range_month=<..>&business_hours_start=<..>&business_hours_end=<..>&status_available_as_working_time=<..>&version=<..>
Host: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

--------------------------------

### Edit Objects Group Response Example

Source: https://www.fmsdocumentation.com/apis/objects-groups-api/edit-objects-groups-api

This is an example of a successful response when editing an object group. It returns the updated group ID, name, and the list of object IDs that now belong to the group.

```json
{
    "id": "6f63d04a",
    "name": "xfds",
    "objects_ids": [
        "3d5a92ce",
        "1f34d706",
        "15a5e322"
    ]
}
```

--------------------------------

### Get All Client Objects

Source: https://www.fmsdocumentation.com/apis/object-api

This endpoint retrieves information for all objects associated with a client. It requires the API key and the version parameter, which must be '1'.

```http
GET /objects?version=1&api_key=<…> HTTP/1.1
HOST: api.fm-track.com
Content-Type:application/json;charset=UTF-8
```

--------------------------------

### Geozones List API Response Example

Source: https://www.fmsdocumentation.com/apis/geozones-list-api

Illustrates the JSON structure of a successful response from the Geozones List API, showing pagination details and a list of geozone items with their properties.

```json
{
    "continuation_token": 1,
    "items": [
        {
            "id": "d4e18901",
            "name": "asdada",
            "notes": "aaa fff",
            "type": "POINT",
            "circle": {
                "latitude": 54.689538538142585,
                "longitude": 25.270938071441606,
                "radius": 250.0
            }
        },
        ...
    ]
}
```

--------------------------------

### Get List of Objects with Last Coordinate (v2)

Source: https://www.fmsdocumentation.com/apis/object-last-coordinate-api

Use this endpoint to retrieve a list of objects visible to a user under a specific client. Location is provided as coordinates. If no coordinate data is available, `last_coordinate` will be empty. This example uses curl for testing.

```Shell
curl -X GET "https://api.fm-track.com/objects-last-coordinate?version=2&api_key=r5B5p-CgBlEOpb11HqjZbfbUEI_LTjO9" \
-H "Accept: application/json"
```

--------------------------------

### Driver Status API Response Structure

Source: https://www.fmsdocumentation.com/apis/driver-status-api

This is an example of the JSON response structure you can expect when querying the Driver Status API. It includes continuation tokens for pagination, driver details, and a list of activity items with their respective start and end times, duration, and location.

```json
{
  "continuation_token": "2022-08-29T12:05:34.770Z",
  "driver_id": "string",
  "items": [
    {
      "activity": "DRIVING",
      "duration": 0,
      "end_point": {
        "lat": 0,
        "lon": 0
      },
      "end_time": "2022-08-29T12:05:34.770Z",
      "object_id": "string",
      "plate_number": "string",
      "start_point": {
        "lat": 0,
        "lon": 0
      },
      "start_time": "2022-08-29T12:05:34.770Z"
    }
  ]
}
```

--------------------------------

### Real-time data request for all objects (curl)

Source: https://www.fmsdocumentation.com/apis/object-coordinates-streaming-api-v3

Use this command to initiate a real-time data stream for all objects accessible to your API key. Replace `<…>` with your API key.

```bash
curl -N –http2 "https://api.fm-track.com/object-coordinates-stream?version=3&api_key=<…>"
```

--------------------------------

### GET Request for Driver Time Analysis

Source: https://www.fmsdocumentation.com/apis/driver-time-analysis-api

Use this GET request to retrieve the current time analysis data for a specific driver. Ensure the driverId and api_key are correctly provided.

```HTTP
GET /drivers/{driverId}/current-time-analysis?version=1&api_key=<…>  
HOST:api.fm-track.com  
Content-Type:application/json;charset=UTF-8
```

--------------------------------

### Request All Drivers (v2)

Source: https://www.fmsdocumentation.com/apis/driver-api-v2

Use this endpoint to retrieve a list of all drivers. Parameters like `limit`, `continuation_token`, `identifier_type`, and `identifier` can be used to filter and paginate the results. Ensure your `api_key` is valid.

```http
GET /drivers?version=2&api_key=<...>&limit=<...>&continuation_token=<...>&identifier_type=<...>&identifier=<...>
HOST: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

--------------------------------

### Example Tire Data Structure

Source: https://www.fmsdocumentation.com/apis/object-coordinates-history-api-v3

This snippet shows the structure of tire data returned by the API, including sensor status, pressure, temperature, and fault detection.

```json
{
            "tire01": {
              "tire_pressure_threshold_detection": "2",
              "tire_sensor_electrical_fault": "2",
              "tire_status": "1",
              "tire_temperature": "39.5",
              "tire_air_leakage_rate": "2001.0",
              "tire_pressure": "400",
              "tire_sensor_enable_status": "0",
              "tire_location": "23",
              "tire_extended_tire_pressure_support": "3"
            },
            "tire36": {
              "tire_pressure_threshold_detection": "2",
              "tire_sensor_electrical_fault": "2",
              "tire_status": "1",
              "tire_temperature": "39.5",
              "tire_air_leakage_rate": "2036.0",
              "tire_pressure": "400",
              "tire_sensor_enable_status": "0",
              "tire_location": "23",
              "tire_extended_tire_pressure_support": "3"
            }
         }
```

--------------------------------

### Creating a Driver

Source: https://www.fmsdocumentation.com/apis/driver-management-api

This endpoint allows you to create a new driver in the system. It requires essential driver details and can optionally include various identification types.

```APIDOC
## POST /management/driver

### Description
Creates a new driver with the provided details.

### Method
POST

### Endpoint
/management/driver?version=1&api_key=<...>

### Parameters
#### Query Parameters
- **version** (String) - Required - Version of the API
- **api_key** (String) - Required - User identification key

#### Request Body
- **first_name** (String) - Required - The driver’s first name. Maximum length: 250
- **last_name** (String) - Optional - The driver’s last name. Maximum length: 250
- **address** (String) - Optional - The driver's address. Maximum length: 250
- **phone** (String) - Optional - The driver's telephone number. Maximum length: 30
- **identifiers** (Array) - Optional - Container for identification codes
  - **identifier** (String) - Identifiers - Identification code. Length (TACHOGRAPH): 10-16, Length (DLT): 15-18, Maximum length (WIRELESS, IBUTTON): 20. All codes must be unique among all of the user's existing drivers.
  - **type** (String) - Identifiers - Identification code type. Possible values: DLT, TACHOGRAPH, WIRELESS, IBUTTON

### Request Example
```json
{
    "first_name": "Driver",
    "last_name": "McDriver",
    "address": "Lithuania, Vilnius",
    "phone": "+3700000000",
    "identifiers": [
        {
            "identifier": "343234323432342",
            "type": "DLT"
        },
        {
            "identifier": "0123456789",
            "type": "TACHOGRAPH"
        },
        {
            "identifier": "3AC64785D2FF",
            "type": "WIRELESS"
        },
        {
            "identifier": "123456789",
            "type": "IBUTTON"
        }
    ]
}
```

### Response
#### Success Response (200)
- **id** (String) - Driver identifier
- **first_name** (String) - The driver’s first name
- **last_name** (String) - The driver’s last name
- **address** (String) - The driver's address
- **phone** (String) - The driver's telephone number
- **identifiers** (Array) - Container for identification codes
  - **identifier** (String) - Identification code
  - **type** (String) - Identification code type. Possible values: DLT, TACHOGRAPH, WIRELESS, IBUTTON

#### Response Example
```json
{
    "id": "ABC123",
    "first_name": "Driver",
    "last_name": "McDriver",
    "address": "Lithuania, Vilnius",
    "phone": "+3700000000",
    "identifiers": [
        {
            "identifier": "343234323432342",
            "type": "DLT"
        },
        {
            "identifier": "0123456789",
            "type": "TACHOGRAPH"
        },
        {
            "identifier": "3AC64785D2FF",
            "type": "WIRELESS"
        },
        {
            "identifier": "123456789",
            "type": "IBUTTON"
        }
    ]
}
```

#### Error Response (409 Conflict)
- **code** (Integer) - HTTP status code
- **message** (String) - Error message describing the conflict

#### Error Response Example (409 Conflict)
```json
{
    "code": 409,
    "message": "Another driver with identifier [123456789] already exists."
}
```

#### Error Response (422 Unprocessable Entity)
- **code** (Integer) - HTTP status code
- **message** (String) - Validation failed, see 'fieldValidationErrors' for more details
- **field_validation_errors** (Array) - Details about validation errors
```

--------------------------------

### Request for all drivers

Source: https://www.fmsdocumentation.com/apis/driver-api-v2

This endpoint retrieves a list of drivers. It supports filtering and pagination using query parameters.

```APIDOC
## GET /drivers

### Description
Retrieves a list of drivers with optional filtering and pagination.

### Method
GET

### Endpoint
/drivers

### Parameters
#### Query Parameters
- **version** (String) - Required - Version of the API. Currently '2'.
- **api_key** (String) - Required - User identification key.
- **limit** (Number) - Optional - How many drivers should be included in the response. Default value: 100. Maximum value: 1000.
- **continuation_token** (Number) - Optional - Used for pagination to retrieve subsequent sets of results.
- **identifier_type** (String) - Optional - Identification type, used to get specific driver data. Possible values: DLT, TACHOGRAPH, WIRELESS, IBUTTON.
- **identifier** (String) - Optional - Identification code, used to get specific driver data.

### Request Example
```
GET /drivers?version=2&api_key=<...>&limit=<...>&continuation_token=<...>&identifier_type=<...>&identifier=<...>
HOST: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

### Response
#### Success Response (200)
- **count** (Number) - How many records are included in the response.
- **continuation_token** (Number) - Displays from which record the data is shown if the record limit was reached.
- **items** (Array) - Container for all drivers.
  - **id** (String) - Driver identifier.
  - **first_name** (String) - The driver’s first name.
  - **last_name** (String) - The driver’s last name.
  - **address** (String) - The driver's address.
  - **phone** (String) - The driver's telephone number.
  - **identifiers** (Array) - Container for identification codes.
    - **identifier** (String) - Identification code.
    - **type** (String) - Identification code type. Possible values: DLT, TACHOGRAPH, WIRELESS, IBUTTON.

#### Response Example
```json
{
  "count": 100,
  "continuation_token": 123,
  "items": [
    {
      "id": "ABC123",
      "first_name": "Driver",
      "last_name": null,
      "address": "Lithuania, Vilnius",
      "phone": "+3700000000",
      "identifiers": [
        {
          "identifier": "343234323432342",
          "type": "DLT"
        },
        {
          "identifier": "123456789",
          "type": "TACHOGRAPH"
        },
        {
          "identifier": "3AC64785D2FF",
          "type": "WIRELESS"
        },
        {
          "identifier": "123456789",
          "type": "IBUTTON"
        }
      ]
    }
  ]
}
```
```

--------------------------------

### Get Objects Groups API

Source: https://www.fmsdocumentation.com/apis/objects-groups-api

Retrieves a list of object groups.

```APIDOC
## GET /objects/groups

### Description
Retrieves a list of all available object groups.

### Method
GET

### Endpoint
/objects/groups

### Response
#### Success Response (200)
- **groups** (array) - A list of object groups.
```

--------------------------------

### TPMS Data Support Example

Source: https://www.fmsdocumentation.com/apis/object-coordinates-history-api-v3

This snippet illustrates the structure for TPMS data, including extended tire pressure support. It shows how various tire parameters are represented.

```json
"tire_extended_tire_pressure_support": "3"
```

```json
"tire07": {
                        "tire_pressure_threshold_detection": "2",
                        "tire_sensor_electrical_fault": "2",
                        "tire_status": "1",
                        "tire_temperature": "39.5",
                        "tire_air_leakage_rate": "2007.0",
                        "tire_pressure": "400",
                        "tire_sensor_enable_status": "0",
                        "tire_location": "23",
                        "tire_extended_tire_pressure_support": "3"
                    }
```

```json
"tire08": {
                        "tire_pressure_threshold_detection": "2",
                        "tire_sensor_electrical_fault": "2",
                        "tire_status": "1",
                        "tire_temperature": "39.5",
                        "tire_air_leakage_rate": "2008.0",
                        "tire_pressure": "400",
                        "tire_sensor_enable_status": "0",
                        "tire_location": "23",
                        "tire_extended_tire_pressure_support": "3"
                    }
```

```json
"tire09": {
                        "tire_pressure_threshold_detection": "2",
                        "tire_sensor_electrical_fault": "2",
                        "tire_status": "1",
                        "tire_temperature": "39.5",
                        "tire_air_leakage_rate": "2009.0",
                        "tire_pressure": "400",
                        "tire_sensor_enable_status": "0",
                        "tire_location": "23",
                        "tire_extended_tire_pressure_support": "3"
                    }
```

```json
"tire10": {
                        "tire_pressure_threshold_detection": "2",
                        "tire_sensor_electrical_fault": "2",
                        "tire_status": "1",
                        "tire_temperature": "39.5",
                        "tire_air_leakage_rate": "2010.0",
                        "tire_pressure": "400",
                        "tire_sensor_enable_status": "0",
                        "tire_location": "23",
                        "tire_extended_tire_pressure_support": "3"
                    }
```

```json
"tire11": {
                        "tire_pressure_threshold_detection": "2",
                        "tire_sensor_electrical_fault": "2",
                        "tire_status": "1",
                        "tire_temperature": "39.5",
                        "tire_air_leakage_rate": "2011.0",
                        "tire_pressure": "400",
                        "tire_sensor_enable_status": "0",
                        "tire_location": "23",
                        "tire_extended_tire_pressure_support": "3"
                    }
```

```json
"tire12": {
                        "tire_pressure_threshold_detection": "2",
                        "tire_sensor_electrical_fault": "2",
                        "tire_status": "1",
                        "tire_temperature": "39.5",
                        "tire_air_leakage_rate": "2012.0",
                        "tire_pressure": "400",
                        "tire_sensor_enable_status": "0",
                        "tire_location": "23",
                        "tire_extended_tire_pressure_support": "3"
                    }
```

```json
"tire13": {
                        "tire_pressure_threshold_detection": "2",
                        "tire_sensor_electrical_fault": "2",
                        "tire_status": "1",
                        "tire_temperature": "39.5",
                        "tire_air_leakage_rate": "2013.0",
                        "tire_pressure": "400",
                        "tire_sensor_enable_status": "0",
                        "tire_location": "23",
                        "tire_extended_tire_pressure_support": "3"
                    }
```

--------------------------------

### Get Last Assignation

Source: https://www.fmsdocumentation.com/apis/driver-assignations-api

Retrieves the latest driver assignment for a given object or driver.

```APIDOC
## GET /driver/assignations/last

### Description
Retrieves the most recent driver assignment associated with either a specific object or a specific driver.

### Method
GET

### Endpoint
/driver/assignations/last?version=1&api_key=<...>

### Parameters
#### Query Parameters
- **version** (string) - Required - Version of API
- **api_key** (string) - Required - User identification key
- **byDriverId** (string) - Required - Driver identifier, External driver ID. Either `byDriverId` or `byObjectId` must be provided.
- **byObjectId** (string) - Required - Object identifier, External object ID. Either `byDriverId` or `byObjectId` must be provided.

### Request Example (by Object ID)
```
GET /driver/assignations/last?version=1&byObjectId=7bf8990c-dba6-11e9-bdfc-1ff21de66015&api_key=L6fwb1xODwA95qF7ybXJ4S2cSM49h1Wj
HOST: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

### Request Example (by Driver ID)
```
GET /driver/assignations/last?version=1&byDriverId=240afea1-84ae-43ec-8139-f13cfa2f3094&api_key=L6fwb1xODwA95qF7ybXJ4S2cSM49h1Wj
HOST: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

### Response
#### Success Response (200)
- **driver_id** (string) - Driver identifier, External driver ID
- **object_id** (string) - Object identifier, External object ID
- **event_type** (string) - Event type
- **datetime** (string) - Datetime of START or STOP event

#### Response Example
```json
{
    "object_id":"7bf8990c-dba6-11e9-bdfc-1ff21de66015",
    "driver_id":"240afea1-84ae-43ec-8139-f13cfa2f3094",
    "event_type":"START",
    "datetime":"2021-07-01T08:50:23.893Z"
}
```

#### Error Responses
- **400 Bad Request**: Missing or invalid `byDriverId` or `byObjectId` parameter.
- **404 Not Found**: Object or Driver ID not found.
```

--------------------------------

### TPMS Tire Pressure

Source: https://www.fmsdocumentation.com/apis/object-coordinates-history-api-v3

Reports the current pressure of the tire. Example value is 400 units.

```json
"tire_pressure": "400"
```

--------------------------------

### Create Driver Request

Source: https://www.fmsdocumentation.com/apis/driver-management-api

Use this endpoint to add a new driver to the system. Ensure all required fields are provided and identifiers are unique.

```http
POST /management/driver?version=1&api_key=<...>
HOST: api.fm-track.com
Content-Type: application/json;charset=UTF-8


BODY:
    {
    "first_name": "Driver",
    "last_name": "McDriver",
    "address": "Lithuania, Vilnius",
    "phone": "+3700000000",
    "identifiers": [
        {
            "identifier": "343234323432342",
            "type": "DLT"
        },
        {
            "identifier": "0123456789",
            "type": "TACHOGRAPH"
        },
        {
            "identifier": "3AC64785D2FF",
            "type": "WIRELESS"
        },
        {
            "identifier": "123456789",
            "type": "IBUTTON"
        }
    ]
}
```

--------------------------------

### TPMS Tire Temperature

Source: https://www.fmsdocumentation.com/apis/object-coordinates-history-api-v3

Reports the temperature of the tire in Celsius. Example value is 39.5 degrees.

```json
"tire_temperature": "39.5"
```

--------------------------------

### Real-time data request for a specific object (curl)

Source: https://www.fmsdocumentation.com/apis/object-coordinates-streaming-api-v3

Use this command to initiate a real-time data stream for a single object. Replace `<...>` with your actual object ID and API key.

```bash
curl -N –http2 "https://api.fm-track.com/object-coordinates-stream?version=3&object_id=<…>&api_key=<…>"
```

--------------------------------

### Driver Status API Request Example

Source: https://www.fmsdocumentation.com/apis/driver-status-api

Use this endpoint to retrieve driver status information for a specified period. Ensure you include all required parameters like driver ID, date range, and API key.

```http
GET /driverstate/{driverId}?from_datetime=<...>&to_datetime=<...>&continuation_token=<..>&limit=<..>&version=1&api_key=<..> HTTP/1.1
Host: api.fm-track.com
Content-Type: application/json;charset=UTF-8
```

```http
GET /driverstate/{driverId}?from_datetime=<...>&to_datetime=<...>&continuation_token=<..>&limit=<..>&version=1&api_key=<..> HTTP/1.1
```

```http
Host: api.fm-track.com
```

```http
Content-Type: application/json;charset=UTF-8
```
Tokens:
Raw