Retrieve Monitoring Trace

URL parameters and connection settings

Headers:

  • Con­tent type: app/json
  • Accept: application/json
  • Autho­riza­tion: bear­er {access_token}
  • API Key: {unique_app_api_key}

Authorization

The autho­riza­tion process is described Here. Each API request must also con­sist of a unique Api-key obtained dur­ing appli­ca­tion reg­is­tra­tion togeth­er with client_id and client_secret.

Endpoint operation description

This end­point returns the mon­i­tored route of a giv­en trans­port order in Geo­J­SON for­mat (Feature with MultiPoint geom­e­try), includ­ing arrays of time­stamps.

Parameters

Path

  • transport_id (UUID or sys­tem iden­ti­fi­er of the mon­i­tored trans­port order).

Example Response

{
  "type": "Feature",
  "geometry": {
    "type": "MultiPoint",
    "coordinates": [
      [17.02328, 51.10547],
      [17.00543, 51.07439],
      [16.97018, 51.04871],
      ...
      [18.21338, 50.55592]
    ]
  },
  "properties": {
    "timestamps": [
      "2025-09-02T11:09:41.000Z",
      "2025-09-02T11:10:41.000Z",
      ...
      "2025-09-02T11:30:41.000Z"
    ],
    "date_received": [
      "2025-09-02T11:09:41.000Z",
      "2025-09-02T11:10:41.000Z",
      ...
      "2025-09-02T11:30:41.000Z"
    ]
  }
}