OEM connected vehicle data & BMW CarData integration

OEM vehicle data and tracker data answer different questions

OEM means original equipment manufacturer. Connected vehicle APIs can expose readings reported by the car's manufacturer, while an installed GPS tracker supplies its own position and telemetry. Data availability, timestamps and access permissions differ between these sources.

Chicane keeps the sources separate. BMW readings retain their original values, units and reading timestamps and do not overwrite tracker positions, journeys, odometer readings or service thresholds. That distinction helps an operator understand whether a value came from the car or the tracking device.

BMW CarData: what is available today

For supported BMW vehicles and owner access, the integration can show available mileage, fuel quantity and percentage, fuel and electric range, battery charge, charging status and service readings. VIN-specific model and paint details and a BMW-supplied vehicle image can enrich garage cards when available.

The owner enables CarData API access, supplies a client ID and completes BMW's sign-in and consent flow. Chicane pairs the connection with an existing vehicle and checks the recorded VIN. The connection is scoped to the linking Chicane login; other users do not automatically receive its data.

The current release retrieves readings on request and serves cached results. The standard reading group has no location fields. Continuous streaming, background refresh and remote car commands are outside this release. Enterprise business-account access remains future work, and live owner consent and target-device acceptance require deployment validation.

Plan a manufacturer or device integration around real access

A manufacturer badge on a vehicle does not guarantee API access. Check market, vehicle equipment, account type, consent, field availability and request limits before designing a service. In the OEM garage, reading time and retrieval time are labelled separately so cached data is not presented as a fresh live reading.

For other vehicle manufacturers or device OEMs, use our custom-work service to assess the supplied API or protocol documentation. Telematics Middleware covers supported tracker protocols, and Media Middleware handles supported dashcam and MDVR video. These integrations are distinct from a car manufacturer's connected vehicle API.