Vehicle management
Related Manuals
- Introduction to Fleet Complete API
- API User management
- API calls generic description
- Vehicle management
- System callbacks
- Creating API account
- API Tasks management
- Vehicle bookings management
- API Customer management
Vehicle API allows customers to maintain/update their vehicle list in FC+ by using API commands. Customers can request data from FC+ about their fleet as well as make vehicle updates in FC+ by pushing the information from customer’s internal system.
There are multiple GET commands that are used to get vehicle data from FC+. Below we have provided basic description of each GET command to help customers understand which command would best suit their needs:
- Api/Vehicles/get – will provide vehicle data and vehicle setup under customer organization. Command can be run to get ALL company vehicles data or specified vehicles data. If ID parameter is specified, then data is returned only for selected vehicle(s).
Example API calls: app.ecofleet.com/seeme/Api/Vehicles/get?__proto__=&key=API_KEY – get data for all company vehicles
app.ecofleet.com/seeme/Api/Vehicles/get?id=OBJECT_ID&__proto__=&key=API_KEY – get data for selected company vehicle(s)
Response will provide information about general vehicle data, and setup within customer organization (e.g. vehicle make and model, HW installed, vehicle groups etc)
- Api/Vehicles/getLastData – will provide the snapshot of the latest reported vehicle data such as: location, status, movement, and any vehicle related data such last known driver, TCO data for TACHO vehicles CAN data if used etc.
Example API call: app.ecofleet.com/seeme/Api/Vehicles/getLastData?__proto__=&key=API_KEY – get data for all company vehicles app.ecofleet.com/seeme/Api/Vehicles/getLastData?objectId=OBJECT_ID&__proto__=&key=API_KEY - get data for selected company vehicle(s)
NB! The reported speed is based on last known GPS signal ( 1) and not HW device reporting. If latest GPS signal was received before vehicle was stopped (and/or ignition switched off) and the latest data from device was sent after vehicle was stopped, you might still see the speed value > 0, based on last known GPS data. (based on last active GPS state data)
3. Api/Vehicles/getRawData – will provide vehicle historical action data during the selected period for each device reporting event during selected period.
Required parameters:
- ObjectID
- beginTimeStamp
- endTimeTtamp
Response data fields might differ based on vehicle and HW device installed. E.g. if device reads CAN data then CAN related fields will be shown; if vehicle has TACHO then TACHO related data fields will be listed as well. Each node in response holds data for a single timestamp as reported by device.
Difference between lastData and rawData commands:
If customer wants to see where vehicle is right now and what are the most recent data records, they need to use lastData command.
If customer wants to see where vehicle has been, how it moved and how reported values were changing with the time, they need to use getRawData.
- Api/Vehicles/getTrips – will provide vehicle trip data during the selected period. (distance, driver data, location, speed)
Required parameters:
- objectID
- beginTimeStamp
- endTimeTtamp
Example API call: app.ecofleet.com/seeme/Api/Vehicles/getTrips?objectId=OBJECT_ID&begTimestamp=2024-04-17&endTimestamp=2024-04-18&__proto__=&key=API_KEY
Details on individual trips during selected period will provide: the dates of the trip, driver, start and end locations, speed and green driving statistics.
More information about available commands and specific data fields in API response based on vehicle and HW installed can be found at https://app.ecofleet.com/seeme/services/apidoc/seeme#Vehicles