Create a developer account and application in the High Mobility Developer Console at high-mobility.com; enable the OEM data connections you need (BMW, Mercedes-Benz, Ford, Volkswagen Group, and others from the 22+ OEM partnerships).
Implement the High Mobility OAuth flow: direct the vehicle owner to the consent screen where they authenticate with their OEM account credentials and grant data access to your application.
After consent, exchange the authorization code for an access token using the High Mobility token endpoint.
Use the Auto API to request data in a normalized, brand-agnostic format; send GET requests to endpoints such as /vehicles/{vehicleSerial}/location, /vehicles/{vehicleSerial}/odometer, /vehicles/{vehicleSerial}/engine, or /vehicles/{vehicleSerial}/charging.
For real-time streaming, subscribe to data push notifications from High Mobility, which delivers updates from the vehicle without repeated polling.
Use the built-in car simulator in the developer console to test integrations without requiring a physical vehicle during development.
Known gotchas
Each OEM integration requires the vehicle owner to have an active connected-car account with that OEM and to complete the consent step; access cannot be obtained without explicit owner authorization.
Signal availability and refresh rates vary significantly across OEMs and vehicle models; consult the High Mobility compatibility tables for each brand before committing to specific signals in your application design.
Production access to live vehicle data requires moving beyond the sandbox tier; pricing is consumption-based per data point update, which can become significant at fleet scale.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp