Apply to the BMW Group CarData partner program through the BMW Group developer portal; the program requires a business use case review and approval before credentials are granted
Upon approval, configure your application with the provided client credentials and review the CarData API documentation to understand the available vehicle data signals for BMW and MINI vehicles
Implement the OAuth2 authorization flow: vehicle owners must consent via the My BMW or MINI Connected app to share their data with your application
Note the OS version requirement for BMW and MINI vehicles: certain API features require the vehicle to be running OS Version 8 or higher — query the vehicle's software version before assuming full capability
Call the available endpoints to retrieve telemetry including location, charge level, fuel level, mileage, and door/window status, handling the response schema which differs from generic OEM-agnostic platforms
For remote service commands (lock, unlock, climate pre-conditioning), use the remote services endpoints and implement the asynchronous polling pattern to check command execution status
Known gotchas
BMW and MINI vehicles require OS Version 8 or higher for certain connected data and command features; vehicles on older software will return limited data or reject remote commands — communicate this requirement to end users
The BMW CarData platform has separate developer tracks for consumer applications and fleet/B2B use cases; ensure you are onboarding on the correct track for your use case, as the data products and agreements differ
Consent must be actively maintained by the vehicle owner; if the owner revokes access through the My BMW app, your API calls will begin returning authorization errors — implement consent-revocation handling in your 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