Building custom solutions with Geotab data just got easier for developers and integrators. We've updated the MyGeotab API to include critical vehicle data directly within the Trip object, reducing the effort required to sync journey information with engine metrics.

The Trip object now includes two new properties: Odometer and EngineHours. These properties are automatically returned as part of the standard Get API response.

Previously, retrieving this combined data required three separate API calls, which added complexity and increased the load for large fleets. By consolidating this information, we've eliminated the need for extra workarounds and separate status data requests.

Note: Odometer returns values in metres (not kilometres), and EngineHours stores values in seconds (not hours). Conversion may be needed depending on downstream use.

This update simplifies the most common integration workflows for our partners and customers. Integrators no longer need to build complex logic to correlate odometer readings and engine hours with specific trips, saving significant development time.

Beyond reducing integration costs, this change also improves performance by lowering the overall API load on MyGeotab servers. This ensures faster data retrieval and a more scalable experience for fleets of all sizes.

These properties are available immediately to all API consumers and integrators globally. Existing integrations will not be affected by these additive fields, though developers should note that Odometer values are returned in meters and EngineHours are provided in seconds.