Account for Volkswagen Group's 2026 third-party API lockout when planning a We Connect / CarNet integration for VW, Audi, Škoda, or Cupra
domain: community.home-assistant.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm current status before building anything: as of May 2026, Volkswagen Group disabled the authentication flow that let third-party apps read/control vehicles using stored owner credentials alone, across VW, Audi, Škoda, and Cupra
Check whether the specific brand/market you need has a legitimate high-mobility.com or OEM-published data API alternative instead of the retired consumer-credential flow
If pursuing official access, expect to establish a formal business-to-business relationship with Volkswagen Group Info Services, including app attestation, rather than a simple API-key signup
If relying on a community library, verify it has migrated to the new attestation-based flow (e.g., successor projects to WeConnect-python) rather than assuming an older library still works
Document this dependency risk explicitly for stakeholders, since VW Group has shown it will change or remove third-party access with little advance notice
Known gotchas
Any integration guide describing simple username/password login against We Connect/CarNet predates the May 2026 change and will no longer authenticate — this is a live, breaking change, not a hypothetical risk
The replacement token flow requires cryptographic attestation tying requests to an officially registered VW Group app, which locks out DIY/community clients that can't obtain that attestation
Because the shutdown spans multiple brands (VW, Audi, Škoda, Cupra) under one Info Services layer, a workaround found for one brand's endpoint may not generalize to the others
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?