go-playground

Documentation

Overview

NOTES basically what we see is that underneath everything there is a semi-reasonable oauth based API which is documented here https://developers.hyundai.com/web/v1/hyundai/specification/account/account_token albiet in korean. You go through a flow to get an auth code which you can then provide back to the service to get an access, refresh, and id token. It's unclear, possibly a bit unlikely that you need the cookie once you've got the access token. This remains to be tested. It's very likely that it's just the oauth flow used by the bluelink apps that are fragile, while the core ccapi is fairly stable.