Get data from a single device tracker.

You can enter a range of dates to get the data for that period.

/v2/trackers/<dev-id>/?start=XXX&end=XXX

Arguments

• dev_id [*]: Device id number

• start: (Optional) (yyyy-mm-dd hh:ii:ss) Start date of search interval.
  If you only enter the start date it will show the reading of that moment.

• end: (Optional) (yyyy-mm-dd hh:ii:ss) End date of search interval.
  Can not be greater than the current date or the difference
  between dates can not be greater than 32 days
• fields: (Optional) Comma-separated list of variables to return, with or
  without the table prefix (e.g. Pact_ac,energy). Datetime and
  devices_id are always returned. Unknown fields return 400.

Response

JSON object with the result. May return the following errors:

• 502 Unsupported tracker tech : No database conversion made, contact us
• 404 Not found : No device found or don't have rights to get data
• 400 Wrong plant or trackers id: The id format is incorrect
• 400 Bad Dates: Dates entered are incorrect
• 204 No data found: The data entered have not produced any results

Example

Get all trackers data (last quarter) in for device_id XXXXX

GET /v2/trackers/XXXXX HTTP/1.1
Host: apiexternal.mvscada.com
MV-API-Key: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Content-Type: application/json

Response

{
    "plant": "XXXXXXXX",
    "devices_id": XXXXX,
    "start": "2025-04-25 11:15:00",
    "end": "",
    "trackers": [
        {
        "data_pvh_tcu_datetime": "2025-04-25 17:00:00",
        "data_pvh_tcu_operationmode": 1,
        "data_pvh_tcu_elevationsetpoint": 0,
        "data_pvh_tcu_elevationposition": 1.29,
        ...
        },
        {...}
    ]
}

Other examples

Get all datas of all meters between requested dates

/v2/trackers/<dev-id>/?start=2025-04-25 00:00:00&end=2025-04-25 11:15:00

Get data from several trackers of the same plant in one response.

/v2/trackers/?gid=XXX&start=XXX&end=XXX
/v2/trackers/?ids=XXX,YYY&start=XXX&end=XXX

Arguments

• gid: Group (plant) id: returns all its trackers. Use gid or ids.
• ids: Comma-separated tracker ids, all from the same plant.
• start: (Optional) (yyyy-mm-dd hh:ii:ss) Start date of search interval.
  If you only enter the start date it will show the reading of that moment.
• end: (Optional) (yyyy-mm-dd hh:ii:ss) End date of search interval.
  Can not be greater than the current date or the difference
  between dates can not be greater than 1 day
• fields: (Optional) Comma-separated list of variables to return, with or
  without the table prefix (e.g. Position,Target). Datetime and
  devices_id are always returned. Unknown fields return 400.
  If the plant mixes tracker technologies, fields must exist in all of them.

Response

JSON object with the result, rows ordered by devices_id and datetime.
Column names depend on the tracker technology. May return the following errors:

• 404 Not found : No device found or don't have rights to get data
• 400 Bad request: gid/ids, dates or fields are incorrect
• 502 Unsupported tracker technology

Example

GET /v2/trackers/?gid=289&start=2026-10-14%2000:00:00&end=2026-10-14%2023:59:59&fields=Position,Target HTTP/1.1
Host: apiexternal.mvscada.app
MV-API-Key: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

{
"group": 289,
"devices_id": [9597, 9598],
"start": "2026-10-14 00:00:00",
"end": "2026-10-14 23:59:59",
"trackers": [
    {"data_trina_tcu_datetime": "2026-10-14 00:00:00", "data_trina_tcu_Position": -15.1, "data_trina_tcu_Target": -15.0, "devices_id": 9597},
    ...
]
}