BMW ConnectedDrive website screenshot

BMW ConnectedDrive

BMW ConnectedDrive is BMW Group's umbrella for connected vehicle services spanning navigation, remote services, intelligent emergency call, ConnectedDrive Store add-ons, and the My BMW app. Programmatic access for customers, third-party developers, and the repair-and-maintenance ecosystem is consolidated under the BMW Open Data Platform / BMW CarData. CarData exposes an OAuth 2.0 Device Code Flow protected REST API at api-cardata.bmwgroup.com for retrieving static vehicle metadata (basicData), telematics, charging history, smart maintenance tyre diagnosis, location-based charging settings, vehicle images, and managing data "containers" that scope which telematics descriptors a client is authorized to read. A companion MQTT 3.1.1 streaming service at customer.streaming-cardata.bmwgroup.com:9000 (TLS) pushes live container data on the per-VIN topic `{gcid}/{vin}`. CarData is the EU regulatory successor to the legacy BMW ConnectedDrive REST endpoints used by the My BMW app and is the canonical surface for third-party automotive integrations, including independent repair, fleet, charging, and home-automation use cases.

BMW ConnectedDrive publishes 2 APIs on the APIs.io network: Containers API and Vehicles API. Tagged areas include Automotive, Connected Vehicle, Telematics, Vehicle Data, and CarData.

BMW ConnectedDrive’s developer surface includes authentication, developer portal, documentation, signup flow, engineering blog, YouTube channel, and 21 more developer resources.

30.4/100 thin ▬ flat Agent 35/100 agent ready Full breakdown ↓
scored 2026-07-28 · rubric v0.6
AccessSelf serve
4 APIs 10 Features
AutomotiveConnected VehicleTelematicsVehicle DataCarDataConnectedDriveElectric VehiclesChargingMQTTStreamingOAuthDevice Code FlowGDPRRight To RepairMobility

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6
Composite quality — 30.4/100 · thin
Contract Quality 12.9 / 25
Developer Ergonomics 6.1 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.5 / 10
Agent readiness — 35/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/bmw-connecteddrive: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

BMW CarData Streaming API

The BMW CarData Streaming API delivers near-real-time vehicle telematics over MQTT 3.1.1 with TLS. Clients connect to `customer.streaming-cardata.bmwgroup.com` on port 9000, aut...

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 co...

BMW ConnectedDrive Containers API

Management of containers

BMW ConnectedDrive Vehicles API

Access vehicle data and information

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

CARDATA API

OPEN COLLECTION

Features 10

Notable capabilities this provider offers.

OAuth 2.0 Device Code Flow against GCDM for customer consent
Scoped client subscriptions — `cardata:api:read` and `cardata:streaming:read`
CarData "containers" let customers scope which telematics descriptors flow to each client
REST endpoints for basic data, telematic data, charging history, smart maintenance tyre diagnosis, location-based charging settings, vehicle images, and vehicle mappings
MQTT 3.1.1 streaming over TLS for near-real-time per-VIN telematics on topic `{gcid}/{vin}`
GCID-based identity model for both REST bearer tokens and MQTT credentials
One-hour ID tokens with refresh-token rotation
Third-party developer track aligned with EU Data Act / right-to-repair
Separate Repair & Maintenance API track for independent workshops
Companion BMW Car IT open-source stack (joynr, ramses, MoCOCrW, python-dlt) underpinning connected-vehicle middleware

Scroll for all 10

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Bmw Connecteddrive Authentication

http · 1 scheme

SECURITY

Bmw Connecteddrive Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Bmw Connecteddrive Agentic Access

11 operations · 2 acting

11 operations · 2 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

Documentation 5

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Commercial 2

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: bmw-connecteddrive
name: BMW ConnectedDrive
url: https://raw.githubusercontent.com/api-evangelist/bmw-connecteddrive/refs/heads/main/apis.yml
description: BMW ConnectedDrive is BMW Group's umbrella for connected vehicle services spanning navigation, remote services,
  intelligent emergency call, ConnectedDrive Store add-ons, and the My BMW app. Programmatic access for customers, third-party
  developers, and the repair-and-maintenance ecosystem is consolidated under the BMW Open Data Platform / BMW CarData. CarData
  exposes an OAuth 2.0 Device Code Flow protected REST API at api-cardata.bmwgroup.com for retrieving static vehicle metadata
  (basicData), telematics, charging history, smart maintenance tyre diagnosis, location-based charging settings, vehicle images,
  and managing data "containers" that scope which telematics descriptors a client is authorized to read. A companion MQTT
  3.1.1 streaming service at customer.streaming-cardata.bmwgroup.com:9000 (TLS) pushes live container data on the per-VIN
  topic `{gcid}/{vin}`. CarData is the EU regulatory successor to the legacy BMW ConnectedDrive REST endpoints used by the
  My BMW app and is the canonical surface for third-party automotive integrations, including independent repair, fleet, charging,
  and home-automation use cases.
tags:
- Automotive
- Connected Vehicle
- Telematics
- Vehicle Data
- CarData
- ConnectedDrive
- Electric Vehicles
- Charging
- MQTT
- Streaming
- OAuth
- Device Code Flow
- GDPR
- Right To Repair
- Mobility
type: Provider
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
position: Provider
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/bmw-connecteddrive.png
created: '2026-05-25'
modified: '2026-05-25'
specificationVersion: '0.20'
apis:
- aid: bmw-connecteddrive:bmw-cardata-streaming-api
  name: BMW CarData Streaming API
  description: The BMW CarData Streaming API delivers near-real-time vehicle telematics over MQTT 3.1.1 with TLS. Clients
    connect to `customer.streaming-cardata.bmwgroup.com` on port 9000, authenticate with their GCID as the MQTT username and
    a GCDM access token (scope `cardata:streaming:read`) as the password, and subscribe to the per-vehicle topic `{gcid}/{vin}`.
    The set of descriptors streamed is controlled by the container(s) the client has registered via the CarData REST API,
    allowing a customer to scope exactly which signals (e.g. state of charge, mileage, doors, location) flow to each third-party
    integration. The streaming surface is the recommended path for charging optimizers, home-automation hubs, and fleet telematics
    back-ends that need event-driven updates instead of polled reads.
  humanURL: https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
  tags:
  - CarData
  - Streaming
  - MQTT
  - Telematics
  - Real-Time
  properties:
  - type: Documentation
    url: https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
  - type: Documentation
    url: https://bmw-cardata.bmwgroup.com/customer/public/api-specification
    name: CarData Streaming Configuration
- 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
- aid: bmw-connecteddrive:bmw-connecteddrive-containers-api
  name: BMW ConnectedDrive Containers API
  description: Management of containers
  humanURL: https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
  baseURL: https://api-cardata.bmwgroup.com
  tags:
  - Containers
  properties:
  - type: OpenAPI
    url: openapi/bmw-connecteddrive-containers-api-openapi.yml
  - type: Documentation
    url: https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
  - type: Documentation
    url: https://bmw-cardata.bmwgroup.com/customer/public/api-specification
- aid: bmw-connecteddrive:bmw-connecteddrive-vehicles-api
  name: BMW ConnectedDrive Vehicles API
  description: Access vehicle data and information
  humanURL: https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
  baseURL: https://api-cardata.bmwgroup.com
  tags:
  - Vehicles
  properties:
  - type: OpenAPI
    url: openapi/bmw-connecteddrive-vehicles-api-openapi.yml
  - type: Documentation
    url: https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
  - type: Documentation
    url: https://bmw-cardata.bmwgroup.com/customer/public/api-specification
common:
- type: AgenticAccess
  url: agentic-access/bmw-connecteddrive-agentic-access.yml
- type: DomainSecurity
  url: security/bmw-connecteddrive-domain-security.yml
- type: Authentication
  url: authentication/bmw-connecteddrive-authentication.yml
- type: Portal
  url: https://www.bmw.com
- type: Portal
  url: https://www.bmwgroup.com
- type: Portal
  url: https://bmw-cardata.bmwgroup.com/
  name: BMW Open Data Platform / CarData
- type: Documentation
  url: https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
  name: CarData Customer API Documentation
- type: Documentation
  url: https://bmw-cardata.bmwgroup.com/customer/public/api-specification
  name: CarData Customer API Specification (Swagger UI)
- type: Documentation
  url: https://bmw-cardata.bmwgroup.com/thirdparty/public/car-data/technical-configuration/api-documentation
  name: CarData Third-Party API Documentation
- type: Documentation
  url: https://bmw-cardata.bmwgroup.com/thirdparty/public/car-data/technical-configuration/api-specification
  name: CarData Third-Party 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
- type: Signup
  url: https://bmw-cardata.bmwgroup.com/customer
  name: CarData Customer Portal
- type: Signup
  url: https://bmw-cardata.bmwgroup.com/thirdparty
  name: CarData Third-Party Portal
- type: Blog
  url: https://www.press.bmwgroup.com/global/rss
- type: Authentication
  url: https://customer.bmwgroup.com/oneid/login
  name: BMW ID / GCDM OAuth (Device Code Flow)
- type: ConnectedDrive
  url: https://www.bmw.com/en/explore-bmw/connected-drive.html
  name: BMW ConnectedDrive overview
- type: ConnectedDriveStore
  url: https://customer.bmwgroup.com/store/
  name: ConnectedDrive Store
- type: MyBMW
  url: https://www.bmw.com/en/footer/my-bmw-app.html
  name: My BMW App
- type: GitHubOrganization
  url: https://github.com/bmwcarit
  name: BMW Car IT GitHub (joynr, ramses, MoCOCrW, python-dlt)
- type: GitHubOrganization
  url: https://github.com/bmwgroup
  name: BMW Group GitHub
- type: PrivacyPolicy
  url: https://www.bmw.com/en/footer/metanavigation/privacy-policy.html
- type: TermsOfService
  url: https://www.bmw.com/en/footer/metanavigation/legal-notice-pool/legal-notice.html
- type: Press
  url: https://www.press.bmwgroup.com
- type: Newsroom
  url: https://www.bmwgroup.com/en/news.html
- type: Twitter
  url: https://twitter.com/BMWGroup
- type: LinkedIn
  url: https://www.linkedin.com/company/bmw-group
- type: YouTube
  url: https://www.youtube.com/@BMWGroup
- type: Features
  data:
  - OAuth 2.0 Device Code Flow against GCDM for customer consent
  - Scoped client subscriptions — `cardata:api:read` and `cardata:streaming:read`
  - CarData "containers" let customers scope which telematics descriptors flow to each client
  - REST endpoints for basic data, telematic data, charging history, smart maintenance tyre diagnosis, location-based charging
    settings, vehicle images, and vehicle mappings
  - MQTT 3.1.1 streaming over TLS for near-real-time per-VIN telematics on topic `{gcid}/{vin}`
  - GCID-based identity model for both REST bearer tokens and MQTT credentials
  - One-hour ID tokens with refresh-token rotation
  - Third-party developer track aligned with EU Data Act / right-to-repair
  - Separate Repair & Maintenance API track for independent workshops
  - Companion BMW Car IT open-source stack (joynr, ramses, MoCOCrW, python-dlt) underpinning connected-vehicle middleware
  sources:
  - https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
  - https://bmw-cardata.bmwgroup.com/customer/public/api-specification
  - https://bmw-cardata.bmwgroup.com/thirdparty/public/car-data/technical-configuration/api-documentation
  - https://github.com/bmwcarit
  updated: '2026-05-25'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
  url: https://apievangelist.com