How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
BMW ConnectedDrive

BMW ConnectedDrive Vehicles API

Access vehicle data and information

Documentation Provider Profile APIs.io OpenAPI GitHub

BMW ConnectedDrive Vehicles API is one of 4 APIs that BMW ConnectedDrive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Vehicles. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 7 paths, and defines 32 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api-cardata.bmwgroup.com.

7 operations 7 paths 32 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api-cardata.bmwgroup.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

BMW ConnectedDrive Vehicles API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (opaque) (bearerAuth).

  • bearerAuth — GCDM Access Token

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 GET. Each is listed below with its method, path, parameters, and response codes.

Vehicles 7

Access vehicle data and information

GET
/customers/vehicles/{vin}/telematicData
Request Vehicle's telematic data for a container, for the specified vehicle.
getTelematicData 3 params → 400401403404500503200
GET
/customers/vehicles/{vin}/smartMaintenanceTyreDiagnosis
Request a vehicle Smart Maintenance Tyre Diagnosis for the specified vehicle.
getSmartMaintenanceTyreDiagnosis 2 params → 400401403404500503200
GET
/customers/vehicles/{vin}/locationBasedChargingSettings
Request Vehicle's location based charging settings
getLocationBasedChargingSettings 3 params → 400401403404500503200
GET
/customers/vehicles/{vin}/image
Request a vehicle image for the specified vehicle.
getImage 2 params → 400401403404500503200
GET
/customers/vehicles/{vin}/chargingHistory
Request the vehicle's Charging History sessions.
getChargingHistory 5 params → 400401403404500503200
GET
/customers/vehicles/{vin}/basicData
Request basic vehicle data for the specified vehicle.
getBasicData 2 params → 400401403404500503200
GET
/customers/vehicles/mappings
Request mapped vehicles.
getMappings 1 param → 400401403404500503200

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are VehicleDto (25 properties), LocationBasedChargingSettingsDataDto (20 properties), ChargingSessionDto (16 properties), TyreDataDto (12 properties). Each schema is shown below with its type and property counts.

TyreWearDto
object
6 properties
BusinessErrorDto
object
2 properties
ChargingLocationDto
object
5 properties 3 required
ExVeTelematicDataResponseDto
object
1 property
TyreDataDto
object
12 properties
PublicChargingPointDto
object
1 property 1 required
DimensionDto
object
8 properties
RunFlatDto
object
3 properties
QualityStatusDto
object
3 properties
LocationBasedChargingTimeWindowDto
object
4 properties
ChargingHistoryResponseDto
object
2 properties 1 required
OptimizedForOemDto
object
3 properties
PassengerCarTyreSetDto
object
6 properties
ChargingSessionDto
object
16 properties 9 required
SmartMaintenanceErrorDto
object
3 properties
VehicleMappingDto
object
3 properties
SeasonDto
object
3 properties
AggregatedQualityStatusDto
object
3 properties
LocationBasedChargingSettingsDataDto
object
20 properties
TreadDto
object
5 properties
PublicChargingPointMatchesDto
object
4 properties
TelematicDataEntryDto
object
3 properties
TyreProductionDateDto
object
3 properties
PassengerCarDto
object
2 properties
SmartMaintenanceTyreDiagnosisDto
object
2 properties
TyreDefectDto
object
4 properties
CustomerErrorResponse
object
4 properties
VehicleDto
object
25 properties
PartNumberDto
object
3 properties
MountingDateDto
object
3 properties
ChargingBlockDto
object
3 properties 2 required
LocationBasedChargingSettingsDto
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bmw-connecteddrive-vehicles-api-openapi.yml Raw ↑

Other APIs BMW ConnectedDrive publishes across the network.

BMW CarData Streaming API
AE Profile APIs.io
BMW CarData Third-Party API
AE Profile APIs.io
BMW ConnectedDrive Containers API
AE Profile APIs.io
#Vehicles
← Back to B APIs
API Details
ID
bmw-connecteddrive:bmw-connecteddrive-vehicles-api
Base URL
https://api-cardata.bmwgroup.com
Docs
https://bmw-cardata.bmwgroup.com/customer/public/api-documentation
Provider
BMW ConnectedDrive
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=bmw-connecteddrive-vehicles-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/bmw-connecteddrive-vehicles-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of BMW ConnectedDrive Vehicles API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.