Audi has closed third-party API access — pairing and Repair are currently blocked
Since ~Sept 3rd, Audi has blocked the login method this app uses (unauthorized_client — client is not allowed to use the device_code grant). This is on Audi’s servers, not a bug in the app — and it’s independently confirmed by several other open-source Audi/VW integrations this week too.
Already paired? You’re fine — your device keeps running on its saved login, no action needed. 1.0.95 makes sure the app never discards that login unnecessarily.
Pairing a new device or need Repair? Not possible right now. I’ve tested every login path Audi still accepts, including a full re-implementation of the original flow — all blocked by a device-attestation check only Audi’s own app can pass. No workaround exists on my end.
Technical details
Password login broke in July (Play Integrity attestation). The app moved to Device Code (RFC 8628) as a fix. Audi has now revoked that grant too. The authorization-code flow still issues a login, but the token exchange is rejected without genuine Play Integrity attestation, which only the real myAudi app can produce.
I’m looking into alternatives, but honestly: the best option so far covers reading data only, or basic charge control — not climate or lock/unlock. If data-only is enough for you, my VW Group Vehicles app (EU Data Act portal) still works and isn’t affected.
Will update this thread as things develop. Sorry for the bad news.
Andi
