BMW ConnectedDrive

BMW CarData Third-Party API

The third-party variant of BMW CarData targets independent service providers — repair shops, charging operators, fleet platforms, insurance, and aftermarket integrators — who consume vehicle data on behalf of customers who have explicitly consented through the BMW Open Data Platform. Third parties register a client, subscribe to one or more CarData services (which assigns the corresponding scope to the client ID), and then drive their users through the OAuth 2.0 Device Code Flow to obtain customer consent. The third-party surface reuses the same REST and MQTT endpoints as the Customer API but is bounded by the data-minimization rules of the BMW Open Data Platform and the EU Data Act / right-to-repair framework.

BMW CarData Third-Party API is one of 3 APIs that BMW ConnectedDrive publishes on the APIs.io network.

Tagged areas include CarData, Third-Party, Vehicles, Telematics, and Right To Repair. The published artifact set on APIs.io includes API documentation.

GitHub

Documentation

📖
Documentation
https://bmw-cardata.bmwgroup.com/thirdparty/public/car-data/technical-configuration/api-documentation
📖
Documentation
https://bmw-cardata.bmwgroup.com/thirdparty/public/car-data/technical-configuration/api-specification
📖
Documentation
https://bmw-cardata.bmwgroup.com/thirdparty/public/repair-and-maintenance/technical-configuration/api-documentation

API entry from apis.yml

apis.yml Raw ↑ 
aid: bmw-connecteddrive:bmw-cardata-thirdparty-api
name: BMW CarData Third-Party API
description: The third-party variant of BMW CarData targets independent service providers — repair shops,
  charging operators, fleet platforms, insurance, and aftermarket integrators — who consume vehicle data
  on behalf of customers who have explicitly consented through the BMW Open Data Platform. Third parties
  register a client, subscribe to one or more CarData services (which assigns the corresponding scope
  to the client ID), and then drive their users through the OAuth 2.0 Device Code Flow to obtain customer
  consent. The third-party surface reuses the same REST and MQTT endpoints as the Customer API but is
  bounded by the data-minimization rules of the BMW Open Data Platform and the EU Data Act / right-to-repair
  framework.
humanURL: https://bmw-cardata.bmwgroup.com/thirdparty/public/car-data/technical-configuration/api-documentation
tags:
- CarData
- Third-Party
- Vehicles
- Telematics
- Right To Repair
properties:
- type: Documentation
  url: https://bmw-cardata.bmwgroup.com/thirdparty/public/car-data/technical-configuration/api-documentation
- type: Documentation
  url: https://bmw-cardata.bmwgroup.com/thirdparty/public/car-data/technical-configuration/api-specification
  name: Third-Party CarData API Specification
- type: Documentation
  url: https://bmw-cardata.bmwgroup.com/thirdparty/public/repair-and-maintenance/technical-configuration/api-documentation
  name: Repair and Maintenance API Documentation