# Fleet API Explained: What You Can Build With High Point GPS

The High Point GPS fleet API gives developers trips, fault codes, EV data, zones and more for GPS tracking integrations. What it covers, when to use it.

Source: https://www.highpointgps.com/resources/fleet-api-explained
By Israel Margulies, CEO & Founder, published 2026-08-14, updated 2026-10-13

## What does the High Point GPS fleet API expose?

The High Point GPS fleet API gives developers programmatic access to the same fleet data the platform interface is built on: devices, users, groups, zones, trips, locations, engine measurements, fault codes, rules, maintenance records, electric vehicle data and media metadata. You can build against the platform's own data layer directly, which goes well beyond a limited export feed.

That breadth is what turns an integration from an idea into something you can ship. A fuel card reconciliation tool needs trip and location data. A maintenance dashboard needs fault codes and engine measurements, and a dispatch system needs live location and zones. The same SDK covers all of it, so one integration project can pull several data types without stitching together separate exports that don't match.

## How does API access work?

You don't request or manage a separate developer API key. Access runs through the High Point GPS platform database and a user account with the right scope, so integration access follows the same permission system as everything else in the High Point GPS platform.

The SDK supports JavaScript and C# development and comes with documentation and tooling for building and integrating Add-Ins. Add-Ins are the same mechanism behind add-on library listings and our own custom Add-Ins like GeoDocs. A developer writing a custom integration and one building an add-on library Add-In use what amounts to the same toolkit.

![Diagram of telematics data flowing from the vehicle to the GPS tracking device, the cloud, the High Point GPS platform and the fleet's own systems](https://www.highpointgps.com/images/figures/telematics-data-flow.webp)

*Where the data goes: the engine bus and sensors feed the GPS tracking device, the cloud applies the fleet's rules, and the High Point GPS platform or the API hands it to your systems.*

## When does a custom GPS tracking API integration make sense?

Many fleets never need a custom integration. Common needs such as fuel card connections, popular TMS platforms and standard reporting are already covered by add-on library Add-Ins with no custom development. Building against the API pays off when no off-the-shelf connector exists for a system your fleet already relies on, or when a workflow is so specific to your operation that no generic tool was going to fit it.

Our development team fills that gap. When the add-on library has no answer, we build the custom connector or Add-In, so you are not stuck living without the integration or running a manual workaround between two systems that should talk to each other directly.

## Common calls, in plain terms

The API exposes the same objects you see on the High Point GPS platform screens, and most integrations use a handful of them.

| What the integration needs | API entity | Typical use |
| --- | --- | --- |
| Where every vehicle is now | DeviceStatusInfo | A dispatch map or a customer portal |
| Trips with start, stop and distance | Trip | Billing, payroll, cost per job |
| Odometer and engine hours | StatusData with diagnostic IDs | Maintenance system work orders |
| Fault codes as they happen | FaultData | Shop tickets opened automatically |
| Exceptions such as speeding or idling | ExceptionEvent | Safety scorecards, HR systems |
| Hours of service and duty status | DutyStatusLog | Dispatch that respects remaining hours |
| Fuel and fill-ups | FuelTransaction, FuelUsed | Fuel card reconciliation, IFTA |

## FAQ

### Do I need a separate API key to use the High Point GPS API?

No. You access the High Point GPS API through the High Point GPS platform database and a user account with the right scope. That account follows the same permission system used everywhere else in the platform, so there is no separate developer key to request or manage, and no parallel set of access rules for your administrators to manage.

### What programming languages does the platform SDK support?

The platform SDK supports JavaScript and C#. Both come with documentation and tooling for building and integrating Add-Ins, so your developers can pick whichever language fits their existing skills and systems. The same toolkit covers custom integrations and Add-Ins built for the add-on library.

### What kind of data can I pull from the High Point GPS API?

You can pull devices, users, groups, zones, trips, locations, engine measurements, fault codes, rules, maintenance records, electric vehicle data and media metadata. That is the same data layer the platform's own interface is built on, so a custom integration can reach most of what you see on screen.

### When does a fleet need a custom integration instead of an add-on library Add-In?

A fleet needs a custom integration when no existing add-on library listing covers a system it already uses, or when a workflow is so specific to its operation that a generic, pre-built tool won't fit. For common needs like fuel cards, popular TMS platforms and standard reporting, an existing Add-In usually does the job.