Access connected vehicle data through the BMW CarData platform
domain: developer.bmw.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a developer account on the BMW Developer Portal and create an application to receive OAuth 2.0 client credentials
Navigate the portal to subscribe to the appropriate Connected Vehicle or CarData API products; BMW gates access by use-case category so select the product matching your scenario
Implement the BMW OAuth 2.0 authorization code flow — the vehicle owner authenticates with their My BMW account credentials and grants consent to the requested scopes
Use the returned access token to call the vehicle data endpoints, referencing the VIN as the primary vehicle identifier in the path or as a query parameter
Test against the sandbox environment provided in the portal using simulated vehicle data before requesting production access, which may require an additional approval step
Known gotchas
BMW's API ecosystem has undergone multiple rebranding cycles (ConnectedDrive, CarData, etc.); ensure you are using the current portal and not relying on documentation for a deprecated API version
Data freshness depends on the vehicle's telematics connection; vehicles without an active SIM or in poor signal areas will return stale data with no real-time update guarantee
Production access often requires a commercial partnership or NDA with BMW Group; purely self-service access is limited to sandbox/simulated data
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?