Register as a third-party developer at bmw-cardata.bmwgroup.com; BMW CarData is built on the ISO 20078 standard and covers BMW, MINI, Rolls-Royce, and Toyota Supra vehicles.
Implement the OAuth 2.0 Device Authorization Grant (Device Code Flow) as specified by BMW CarData to obtain data access clearances from vehicle owners.
Direct the vehicle owner through the consent flow; the owner must have an active BMW ConnectedDrive, MINI Connected, or equivalent account and must explicitly approve third-party data access.
Once a clearance is approved, use the issued access token to call BMW CarData's REST API endpoints for telematics data such as location, mileage, fuel level, and charge status.
For Mercedes-Benz vehicles, access is available through the High Mobility Auto API (see route 7), which aggregates BMW and Mercedes data behind a single normalized integration.
Monitor clearance status; a customer can revoke consent at any time, which invalidates the token and stops data delivery.
Known gotchas
BMW CarData requires explicit per-vehicle, per-customer consent; there is no mechanism to pull data from a vehicle whose owner has not actively approved the clearance in their ConnectedDrive account.
Data scope and signal availability vary by vehicle age, trim level, and whether the owner has an active connected-services subscription; older vehicles may return only a subset of signals.
Direct Mercedes-Benz API access requires its own developer agreement; the High Mobility aggregation layer is the practical path for accessing both brands through a single integration.
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