If you have a GPS fleet tracking system (also known as an AVL), AngelTrack has an API by which it can push position reports into the system.
Your AngelTrack server can accept GPS position reports sent in by your third-party GPS tracking system, via a simple API that anyone can implement.
API URL
Your AngelTrack server's geolocation upload API URL is:
https://your_server_name.angeltrack.com/GPSLocationUpdate.aspx
It expects a GET request with the following query string:
?Token=xxxxxxxxx&Latitude=nnn.nnnnnnnnn&Longitude=nnn.nnnnnnnnn&Accuracy=nnnn
No headers, cookies, or authentication is necessary.
The "Token" parameter contains an employee token or vehicle token, as discussed in the Beacon App Guide. Each token begins with an 'E' or a 'V', plus eight alphanumeric characters.
The "Latitude" and "Longitude" parameters are decimal(16,13), meaning they support up to 13 decimal places. Western longitudes are negative numbers.
The "Accuracy" parameter is optional, containing a numeric number of meters.
You will receive back an HTTP 200 plus a simple HTML document containing a summary of the data you sent, so that you can verify AngelTrack parsed it correctly.
Update Frequency
You may update as often as you wish, subject to the API rate limit discussed below.
We recommend you update no more frequently than once every 45 seconds, because 60 seconds is the resolution of the underlying data-columns and so all of a token's positions received during each 60-second period are merged together.
We suggest you update at least once every six minutes. If you do not update at least once every 10 minutes, AngelTrack will mark the token's position as stale, and if you do not update at least once every 20 minutes, AngelTrack will cease to display the token on any maps.
Security
The API is write-only; you cannot retrieve any information from it.
There is no way for you to tell whether a token is valid or not. AngelTrack accepts position reports from invalid tokens as well as valid ones, always giving a "success" reply. The only way to verify which tokens are valid is to login to AngelTrack and check the Beacon Status Report.
The API accepts a maximum of 100 position reports per AngelTrack provider per three-minute period. Any requests beyond this threshold receive an HTTP error 429 "Too many requests" error.
Integration with AVL Systems / Integrate Fleet Tracking Software
AngelTrack does not presently have any integrations with GPS tracking systems, or with AVL platforms. Consequently, AngelTrack cannot actively pull vehicle GPS data from your fleet tracking application.
The reason we do not have any integrations is the sheer number of different fleet tracking systems. There are simply too many to integrate them all, and there is no clear winner (at least among EMS and fire agencies) either. We offer the aforementioned API by which a fleet tracking system can easily push data into AngelTrack, but this would require the fleet tracking system to build out the integration from their end -- an unlikely event.
If you love your AVL and think it would be easy for AngelTrack to integrate with it, and if your AVL is a popular choice among EMS and fire agencies, then please contact AngelTrack Support and make your case.