Environment
- Country: Germany
- Vehicle: Kia (EU)
- ioBroker Bluelink Adapter: 3.1.28
- Windows 11
- Python 3.14
- Latest bluelinktoken.py from main branch
- Latest curl_cffi
- Smartphone Hotspot tested (same result)
Description
The headless login works almost completely.
The script
- establishes the session
- fetches the RSA public key
- encrypts the password
- signs in successfully
- receives a valid authorization code
Only the last step fails.
[1/4] Loading authorize page...
✅ Session established
[2/4] Fetching RSA public key...
✅ Password encrypted
[3/4] Signing in...
✅ Authorization code received
[4/4] Exchanging code for tokens...
❌ Token exchange failed: HTTP 403
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
</body>
</html>
The Kia Connect App works normally.
Login with username/password is successful.
The authorization code is received successfully.
Only exchanging the authorization code for refresh/access tokens fails.
I also tested
- different Internet connection (smartphone hotspot)
- fresh login
- logout/login in Kia Connect App
- latest version from GitHub
- latest Python packages
Result is always identical.
Could Kia have changed the token endpoint or additional headers/cookies now be required during the token exchange?
Thank you for your great work.
Environment
Description
The headless login works almost completely.
The script
Only the last step fails.
The Kia Connect App works normally.
Login with username/password is successful.
The authorization code is received successfully.
Only exchanging the authorization code for refresh/access tokens fails.
I also tested
Result is always identical.
Could Kia have changed the token endpoint or additional headers/cookies now be required during the token exchange?
Thank you for your great work.