Configured? Bootstrapped? Which write mode? No network call, no secrets — the email is masked and the device id truncated.
Step 1 of the MFA bootstrap. Confirm-gated, because a rejection has a permanent cost.
Step 2 — delivers the passcode by `SMS` or `EMAIL`.
Step 3 — exchanges the passcode for a stored session. Returns no secret.
Discards the stored token so the bootstrap can be re-run. Local only; confirm-gated.
Returns the `rmtoken` **in plaintext** — a full MFA bypass. Exists only to move a locally-bootstrapped session into a deployment that cannot run the bootstrap itself, via `KIA_RMTOKEN`. Confirm-gated.
Every enrolled vehicle with its `vehicleKey`, nickname, model, mileage. VINs are masked to the last 6 characters.
Cached status: door lock, ignition (`ign3` — on an EV `engine` stays false), the nested `climate` block, and more with `include_raw`. Fast, but only as fresh as the last upload.
Wakes the telematics unit for a fresh reading. Slower, draws a little power, and returns no data itself — read `kia_vehicle_status` afterwards.
Last reported position plus a map link. Not a live GPS fix.
Target state of charge per plug type.
Preconditioning. Temperature is best-effort: the car may report its own last-set target instead of the one requested.
+6 more tools listed on main page