The High Point GPS API: What You Can Actually Build

The High Point GPS platform SDK gives developers programmatic access to the same fleet data the platform interface itself is built on: devices, users, groups, zones, trips, locations, engine measurements, fault codes, rules, maintenance records, electric vehicle data, and media metadata. That's not a limited export feed, it's essentially the platform's own data layer, exposed for a developer to build against directly.

That breadth is what makes real integrations possible rather than theoretical. A fuel card reconciliation tool needs trip and location data. A maintenance dashboard needs fault codes and engine measurements. A dispatch system needs live location and zone data. All of that is available through the same SDK, which means a single integration project can pull from multiple data types without stitching together separate, incompatible exports.

There's no separate developer API key to request or manage. Access runs through the High Point GPS platform database and an appropriately scoped user account, which means integration access is tied to the same permission system that governs everything else in the High Point GPS platform, not a parallel access system with its own rules to learn.

The SDK supports both JavaScript and C# development, along with documentation and tooling for building and integrating Add-Ins, the same mechanism that powers add-on library listings and our own custom Add-Ins like GeoDocs. A developer building a custom integration and a developer building an add-on library Add-In are working with fundamentally the same toolkit.

Not every fleet needs a custom integration, and a lot of common needs, fuel card connections, popular TMS platforms, standard reporting, are already covered by existing add-on library Add-Ins without any custom development. The API becomes worth building against specifically when an off-the-shelf connector doesn't exist for a system a fleet already relies on, or when a workflow is specific enough to that fleet's operation that no generic tool was ever going to fit it exactly.

That's the gap our development team fills: building the custom connector or Add-In when the add-on library genuinely doesn't have an answer, rather than a fleet either living without the integration or forcing a manual workaround between two systems that should just talk to each other directly.

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