List the historical breadcrumb locations for a vehicle.
GET
/
vehicles
/
{vehicleId}
/
locations
curl--request GET \--url https://api.withterminal.com/tsp/v1/vehicles/{vehicleId}/locations \--header'Authorization: Bearer <token>'\--header'Connection-Token: <connection-token>'
{"results":[{"id":"vcl_loc_01D8ZQFGHVJ858NBF2Q7DV9MNC","sourceId":"123456789","provider":"geotab","vehicle":"vcl_01D8ZQFGHVJ858NBF2Q7DV9MNC","driver":"drv_01D8ZQFGHVJ858NBF2Q7DV9MNC","locatedAt":"2021-01-06T03:24:53.000Z","location":{"longitude":-122.4194155,"latitude":37.7749295},"address":{"formatted":"1.5 miles from Austin, TX"},"heading":25,"speed":95.33,"metadata":{"modifiedAt":"2023-11-07T05:31:56Z"},"raw":[]}],"next":"cD0yMDIxLTAxLTA2KzAzJTNBMjQlM0E1My40MzQzMjYlMkIwMCUzQTAw"}
Note:
Given the large volume of location data available, we encourage customers to accept compressed (gzip) responses in order to maximize throughput. This is supported with many popular HTTP clients. Result limits vary depending on if results are compressed or not.
Raw data fetched from the source provider. Most of our endpoints support a raw query parameter that will append a list of the raw requests used to form our common model. This can be helpful for leveraging unique fields that are not part of our unified model.
curl--request GET \--url https://api.withterminal.com/tsp/v1/vehicles/{vehicleId}/locations \--header'Authorization: Bearer <token>'\--header'Connection-Token: <connection-token>'
{"results":[{"id":"vcl_loc_01D8ZQFGHVJ858NBF2Q7DV9MNC","sourceId":"123456789","provider":"geotab","vehicle":"vcl_01D8ZQFGHVJ858NBF2Q7DV9MNC","driver":"drv_01D8ZQFGHVJ858NBF2Q7DV9MNC","locatedAt":"2021-01-06T03:24:53.000Z","location":{"longitude":-122.4194155,"latitude":37.7749295},"address":{"formatted":"1.5 miles from Austin, TX"},"heading":25,"speed":95.33,"metadata":{"modifiedAt":"2023-11-07T05:31:56Z"},"raw":[]}],"next":"cD0yMDIxLTAxLTA2KzAzJTNBMjQlM0E1My40MzQzMjYlMkIwMCUzQTAw"}