Geoforce + goAardvark
Bring Geoforce asset location and supported operating readings into a broader view of your mixed fleet.
- Tag
- GPS
- Connection
- Partner API
- Sync
- Depends on vendor reporting and connection configuration
Vendor data
Available data fields
- Location
- Engine hours
- Idle hours
- Odometer
Setup
How to connect
- 01Confirm your Geoforce organization, tracked assets and device capabilities.
- 02Have an authorized user provision API access and the relevant read permissions.
- 03Match asset IDs and serial numbers with goAardvark, then verify timestamps, runtime and meter units.
Asset identity and readings together
Geoforce’s Asset API documents asset names, IDs, makes, models and serial numbers, alongside latest location, street address and timestamps. Its telemetry list includes engine runtime (ERT), ignition, idle time, odometer, speed and heading. Supported readings vary by device and asset; an unpowered tracker should not be assumed to provide engine data.
Select the API that matches your account
Geoforce documents Asset, Device, Reading, Location and GraphQL APIs with different purposes and authorization requirements. The Location API describes user-defined geofences, rather than current asset-position readings. The Rental API updates custom properties and sharing relationships; that does not itself confirm rental-contract status, rental costs or work-order data. Agree on read scope and polling frequency during implementation.
Planning your goAardvark connection
Review your licensed product, account permissions and a sample data set with the goAardvark team. Confirm asset identifiers, units, timestamps, read/write direction and refresh timing before rollout. Vendor documentation describes vendor capabilities; it does not guarantee that every field is enabled in your goAardvark connection.
Official documentation
Documentation reviewed November 12, 2026.
