MyAudi: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 28: | Line 28: | ||
'VW_REVOKE' => 'https://mbboauth-1d.prd.ece.vwg-connect.com/mbbcoauth/mobile/oauth2/v1/revoke', | 'VW_REVOKE' => 'https://mbboauth-1d.prd.ece.vwg-connect.com/mbbcoauth/mobile/oauth2/v1/revoke', | ||
] | ] | ||
<ref>https://github.com/John6810/myaudi-api/blob/d5652e6472f53eecb022b223e2dee6d5eeb29b2b/docs/oauth-flow.md?plain=1#L51</ref> | |||
Latest revision as of 09:34, 20 May 2026
Audi’s connected-services ecosystem. [1]
How it works
The car communicates with Audi servers through:
- built-in LTE modem + eSIM/SIM
- or tethered phone hotspot (depends on market/features)
The MMI logs into your myAudi account using:
- VIN
- key user registration
- Audi backend authentication
The app can then exchange data with the vehicle:
- location
- fuel level
- service info
- navigation destinations
- remote commands (limited on older cars)
Endpoints
'ENDPOINTS' => [
'AUDI_API' => 'https://msg.audi.de',
'REGISTER_APP' => 'https://mbboauth-1d.prd.ece.vwg-connect.com/mbbcoauth/mobile/register/v1',
'AUDI_REVOKE' => 'https://id.audi.com/v1/revoke',
'AUDI_TOKEN' => 'https://id.audi.com/v1/token',
'VW_TOKEN' => 'https://mbboauth-1d.prd.ece.vwg-connect.com/mbbcoauth/mobile/oauth2/v1/token',
'VW_REVOKE' => 'https://mbboauth-1d.prd.ece.vwg-connect.com/mbbcoauth/mobile/oauth2/v1/revoke',
]