Our GPS Fleet Software has a JSON API interface in order to integrate with 3rd party software solutions (ERP, etc.). The API JSON interface works for our web-based hosting accounts as well as for local server customers (if the network allows it).
The availabilty of the JSON interface depends on our offers and standard conditions. Please contact your provider for more information.
How to access the API
The API can only be used with an APIKEY that can only be set by our support.
http://XXX.sw-management.at/GFS/api/std/checkuser?apikey=apikey
The above command will return OK or ERROR if the apikey is correct or invalid (link must be changed).
{"info":"ok"} or {"error":"100"}How to find the different JSON calls and paramenters
Developers can acces the WADL document on our hosting server (or on the local server of the customer):
http://gfs2.sw-management.at/GFS/api/application.wadl
The WADL document explains the calls and parameters in detail, such as the following example:
Basic examples
Query for existing assets
Use the the following http call to query which assets are in a customer account. You will need the assetIDs for other commands.
https://XXX.sw-management.at/GFS/api/masterdata/gps/getAssetStates?apikey=ENTERYOURSECID&langid=2
xxx ... replace the link
ENTERYOURSECID ... the APIKEY that is set for the account
Get the current position
xxx ... replace the link
ENTERYOURSECID ... the APIKEY that is set for the account
YYYY ... assetid
Get historic trips
https://XXX.sw-management.at/GFS/api/masterdata/gps/getGpsHistory?apikey=ENTERYOURSECID&limit=300
xxx ... replace the link
ENTERYOURSECID ... the APIKEY that is set for the account
Get drivers
https://XXX.sw-management.at/GFS/api/masterdata/driver/getDrivers?apikey=ENTERYOURSECID
Get logbook entries