Our GPS Fleet Software API allows third-party software to access data of our system and pass data as well to realize cooperative programs and apps. With our API we enable other developers to build a synergy between our GPS Fleet Software and their Server or App. For use cases in the following documentation I will use our Hosting, but it the API is also usable with a an own server although it then relies on the accessibility of the server.
...
New calls with 3.8.29
modify
- /logbook/set_operating_hours: calling this command with the parameters apikey, assetid and new_h_value will set a new value for the operating time of an asset.
- /insertpos: calling this command with the parameters apikey, assetid, lat, lng, d1, speed, ts_yyyyMMddhhmmss and optional opt_fuellevel will set a new position for the asset including ignition, speed and the time for this particular position and optionally the fuellevel.
- /insertpos_address: calling this command with the parameters apikey, assetid, address, d1, speed, ts_yyyyMMddhhmmss and optional opt_fuellevel will set a new position for the asset at the particular address.
time
- /start_time_record: calling this command with the parameters apikey, start_ts_yyyyMMddhhmmss, personid and optional opt_assetid, opt_custid_geofenceid, opt_activityid, opt_commentstr, opt_lat, opt_lng and opt_address will start a time record for the person starting with the given time and will optionally add the used asset, the geofence or the lng/lat or the address the person is working at, a comment and the activity the person is performing corresponding to the optional parameters given.
- /update_time_record: calling this command with the parameters apikey, end_ts_yyyyMMddhhmmss, personid and optional opt_assetid, opt_custid_geofenceid, opt_activityid, opt_commentstr, opt_lat, opt_lng and opt_address will end the last time record for the person with the given time and will optionally add the used asset, the geofence or the lng/lat or the address the person is working at, a comment and the activity the person is performing corresponding to the optional parameters given. In case of a vehicle the end address/position may vary from the start address/position.
- /insert_complete_time_record: calling this command with the parameters apikey, start_ts_yyyyMMddhhmmss, end_ts_yyyyMMddhhmmss, personid and optional opt_assetid, opt_custid_geofenceid, opt_activityid, opt_commentstr, opt_lat, opt_lng and opt_address will create a full time record from the given start time to the given end time and will optionally add the used asset, the geofence or the lng/lat or the address the person is working at, a comment and the activity the person is performing corresponding to the optional parameters given.
masterdata
- /data/getLastTimeRecord: calling this command with parameters apikey and personid will return the last time record of this person.
- /data/getActivityTypes: calling this command with the apikey returns all activity types of the account.
bin
- /upload: calling this command will allow to upload a file to the server (an image in most cases). As always the apikey is needed as parameter, optional opt_relationID, opt_pkid, opt_category, opt_name, opt_commentinfo, opt_binid can be set to specify the relation and the object the file relates to or to set the category, name or a comment, also the binid could be set to overwrite an existing file.
odr
- /getDynDataValues: calling this command with the apikey and optional opt_limit, opt_relationID or opt_pkid for filtering will return the dynamic fields which can be created and configured by the customer in the GPS Fleet Software allowing to set extra fields/flags for objects.
- /setDynDataValue_for_pkid_defid_relationID: calling this command with parameters apikey, pkid, relationID, defid and one parameter of v_int, v_str, v_bigint, v_float, v_date_yyyyMMddhhmmss, v_boolean will set the given field/flag of the given object to the given value. Important: the correct value parameter must be used to update the field/flag.