Code Maintainers Wanted
I no longer have a Kia or Hyundai so don’t maintain this like I used to. Others who are interested in jumping in are welcome to join the project! Even just pull requests are appreciated!
Introduction
This is a Kia UVO, Hyundai Bluelink, Genesis Connect(Canada Only) written in python. It is primary consumed by home assistant. If you are looking for a home assistant Kia / Hyundai implementation please look here: https://github.com/Hyundai-Kia-Connect/kia_uvo. Much of this base code came from reading bluelinky and contributions to the kia_uvo home assistant project.
Chat on discord::
API Usage
This package is designed to simplify the complexity of using multiple regions. It attempts to standardize the usage regardless of what brand or region the car is in. That isn’t always possible though, in particular some features differ from one to the next.
Europe Hyundai and Kia login logic is based on the bluelink-refresh-token project. Username/password login is supported directly for Kia, Hyundai, and Genesis (EU) — no browser or manual token extraction needed. The pycryptodome package (included as a dependency) is used for RSA password encryption during the EU login flow.
China (Hyundai Bluelink / Kia UVO CN)
China support was rewritten in 2026 against the current China Bluelink iOS app (com.hyundai-motor.cn.bluelink). Highlights and differences vs other regions:
Login uses a five-step flow through the UARS service (uars-{k|h}.hmgmobility.com.cn); the OAuth authorization code is exchanged server-side by UARS and the tokens are returned inside the callback page. Only the Hyundai brand has been live-verified; Kia constants are included from the app binary but are untested.
Access tokens live 6 hours. There is no working refresh_token grant on the China servers, so refresh_access_token re-authenticates silently when possible and otherwise performs a full password login (same pattern as Canada).
Remote control on non-CCS2 vehicles uses the plain access token; a PIN is only required for CCS2-style control commands. pin should be passed to VehicleManager as usual.
Push device registration uses pushType: APNS (not GCM) and requires a providerDeviceId field.
Control-command latency is high (1-2 minutes to reach SUCCESS); consumers should use generous polling timeouts.
Python 3.12 or newer is required to use this package. Vehicle manager is the key class that is called to manage the vehicle lists. One vehicle manager should be used per login. Key data points required to instantiate vehicle manager are:
region: int brand: int, username: str password: str pin: str (required for CA, and potentially USA, otherwise pass a blank string) Optional parameters are:: geocode_api_enable: bool geocode_api_use_email: bool geocode_provider: int geocode_api_key: str language: str
Key values for the int exist in the const.py file as:
REGIONS = {1: REGION_EUROPE, 2: REGION_CANADA, 3: REGION_USA, 4: REGION_CHINA, 5: REGION_AUSTRALIA, 6: REGION_INDIA, 7: REGION_NZ, 8: REGION_BRAZIL}
BRANDS = {1: BRAND_KIA, 2: BRAND_HYUNDAI, 3: BRAND_GENESIS}
GEO_LOCATION_PROVIDERS = {1: OPENSTREETMAP, 2: GOOGLE}
Once this is done you can now make the following calls against the vehicle manager:
#login login(self) #OTP Details #Sent OTP send_otp(self, method) #Verify OTP verify_otp(self, otp_code) #Checks the token is still valid and updates it if not. Should be called before anything else if the code has been running for any length of time. check_and_refresh_token(self) Ideal refresh command. Checks if the car has been updated since the time in seconds provided. If so does a cached update. If not force calls the car. check_and_force_update_vehicles(self, force_refresh_interval) # Interval in seconds - consider API Rate Limits https://github.com/Hacksore/bluelinky/wiki/API-Rate-Limits Used to return a specific vehicle object: get_vehicle(self, vehicle_id) #Updates all cars with what is cached in the cloud: update_all_vehicles_with_cached_state(self) Updates a specific car with cached state: update_vehicle_with_cached_state(self, vehicle_id) Force refreshes all cars: force_refresh_all_vehicles_states(self) Force refreshes a single car: force_refresh_vehicles_states(self, vehicle_id)
An example call would be:
from hyundai_kia_connect_api import * vm = VehicleManager(region=2, brand=1, username="username@gmail.com", password="password", pin="1234") vm.check_and_refresh_token() vm.update_all_vehicles_with_cached_state() print(vm.vehicles)
If geolocation is required you can also allow this by running:
vm = VehicleManager(region=2, brand=1, username="username@gmail.com", password="password", pin="1234", geocode_api_enable=True, geocode_api_use_email=True)
This will populate the address of the vehicle in the vehicle instance.
The Bluelink App is reset to English for users who have set another language in the Bluelink App in Europe when using hyundai_kia_connect_api. To avoid this, you can pass the optional parameter language (default is “en”) to the constructor of VehicleManager, e.g. for Dutch:
vm = VehicleManager(region=2, brand=1, username="username@gmail.com", password="password", pin="1234", language="nl")
Note: this is only implemented for Europe currently.
For a list of language codes, see here: https://www.science.co.il/language/Codes.php. Currently in Europe the Bluelink App shows the following languages:
- "en" English - "de" German - "fr" French - "it" Italian - "es" Spanish - "sv" Swedish - "nl" Dutch - "no" Norwegian - "cs" Czech - "sk" Slovak - "hu" Hungarian - "da" Danish - "pl" Polish - "fi" Finnish - "pt" Portuguese
In Europe and some other regions also trip info can be retrieved. For a month you can ask the days with trips. And you can ask for a specific day for all the trips of that specific day.:: - First call vm.update_month_trip_info(vehicle.id, yyyymm) before getting vehicle.month_trip_info for that month - First call vm.update_day_trip_info(vehicle.id, day.yyyymmdd) before getting vehicle.day_trip_info for that day
Example of getting trip info of the current month and day (vm is VehicleManager instance):
now = datetime.now()
yyyymm = now.strftime("%Y%m")
yyyymmdd = now.strftime("%Y%m%d")
vm.update_month_trip_info(vehicle.id, yyyymm)
if vehicle.month_trip_info is not None:
for day in vehicle.month_trip_info.day_list: # ordered on day
if yyyymmdd == day.yyyymmdd: # in example only interested in current day
vm.update_day_trip_info(vehicle.id, day.yyyymmdd)
if vehicle.day_trip_info is not None:
for trip in reversed(vehicle.day_trip_info.trip_list): # show oldest first
print(f"{day.yyyymmdd},{trip.hhmmss},{trip.drive_time},{trip.idle_time},{trip.distance},{trip.avg_speed},{trip.max_speed}")
In India the day trip list only carries start/end times, so each trip’s figures come from a per-trip detail call (cached per trip). India trips also report trip.end_hhmmss and the driving-behaviour counters trip.hard_braking_count, trip.rapid_acceleration_count and trip.excessive_speed_count.
CLI Usage
A tool bluelink is provided that enable querying the vehicles and save the state to a JSON file. Example usage:
bluelink --region Canada --brand Hyundai --username FOO --password BAR --pin 1234 info --json infos.json
Environment variables BLUELINK_XXX can be used to provide a default value for the corresponding –xxx argument.
1 maintainer
Metadata
1 maintainer
Release files for hyundai-kia-connect-api 4.40.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| hyundai_kia_connect_api-4.40.0.tar.gz | 382.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hyundai_kia_connect_api-4.40.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 634.6 kB
Release files / hyundai_kia_connect_api-4.40.0.tar.gz
| Download URL | hyundai_kia_connect_api-4.40.0.tar.gz |
|---|---|
| Size | 382.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7da8215d32b53dbe5e524a882914cfe76c379cd30981ac9905570d34fc98266
|
|
BLAKE2b-256 checksum How to use checksums |
0c995516f4baf6077cca5adadbb41fb6bd71b488206023a9001b2d32ddd2d20b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / hyundai_kia_connect_api-4.40.0-py3-none-any.whl
| Download URL | hyundai_kia_connect_api-4.40.0-py3-none-any.whl |
|---|---|
| Size | 251.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3592839408e63494689d4772b533d5e824c6fb0d15e8087d3b5b2fd01e018fdd
|
|
BLAKE2b-256 checksum How to use checksums |
74b38c2cf87e3c389d58ef433c6fb27092d0301f71b4facdde5d31a8a55a76c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for hyundai-kia-connect-api 4.40.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
