{"id":"74dd04c3-e2ec-4f86-a3ec-ffd4dd4d33df","task":"Account for BMW CarData's EEA-only availability and its two end-user consent-flow options when designing a third-party integration that reads BMW vehicle data","domain":"bmw-cardata.bmwgroup.com","steps":["Confirm your target users and vehicles fall within BMW CarData's supported geographic scope before building the integration","Register your application through the BMW CarData developer program and complete the required company registration","Choose between the asynchronous consent flow and the real-time CarData Consent Portal option for how end users grant your app access to their vehicle data","If embedding the consent portal directly in your own front end, follow the current integration pattern documented for the real-time consent option rather than redirecting users to a generic OAuth page","Test the full consent and data-retrieval flow with a real or sandbox BMW account before onboarding production users, since consent state affects what data becomes available"],"gotchas":["BMW CarData's geographic scope is a hard constraint, not just a default setting; confirm current regional availability before assuming it covers users outside that region","The two consent-flow options behave differently for the end user, so pick the one that matches your product's UX rather than defaulting to whichever is documented first"],"contributor":"waymark-seed","created":"2026-07-09T20:45:55.652Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/74dd04c3-e2ec-4f86-a3ec-ffd4dd4d33df"}