Telsa Oauth Authentication

[gerard....@gmail.com]

Tesla changed the way they do authentication to use OAuth. It's not just a bunch of GET and POST anymore.

https://tesla-api.timdorr.com/api-basics/authentication

You have to parse HTML that gets returned to scrape data. I'm not sure Automate can do this.

[Henrik "The Developer" Lindqvist]

Use the HTTP request block to get the page content, then execute a findAll function on the content to find the "hidden fields", whatever they are.

[gerard....@gmail.com]

It's strange. I can get a successful response in SoapUI for the first step, but doing it in Automate results in an error response (400 status code)

Request URL: https://auth.tesla.com/oauth2/v3/authorize

Request Method: GET

Request content type: JSON

Request content body: {"client_id": "ownerapi", "code_challenge": "123", "code_challenge_method": "S256", "redirect_uri": "https://auth.tesla.com/void/callback", "response_type": "code", "scope": "openid email offline_access", "state": "123", "login_hint": "X...@yahoo.com"}

I tried adding a user agent string that I found in a Python script that talks to the API, but it made no difference.

Request headers: {"User-Agent": "Mozilla/5.0 (Linux; Android 10; Pixel 3 Build/QQ2A.200305.002; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/85.0.4183.81 Mobile Safari/537.36"}

[Henrik "The Developer" Lindqvist]

GET requests usually don't have a body, try encoding the parameters in the URL, e.g.:

Request URL: https://auth.tesla.com/oauth2/v3/authorize?{{"client_id": "ownerapi", "code_challenge": "123", "code_challenge_method": "S256", "redirect_uri": "https://auth.tesla.com/void/callback", "response_type": "code", "scope": "openid email offline_access", "state": "123", "login_hint": "X...@yahoo.com"};urlEncode}

Request Method: GET

[gerard....@gmail.com]

I tried this the way you specified and using

https://auth.tesla.com/oauth2/v3/authorize?client_id=ownerapi&code_challenge=123&code_challenge_method=S256&redirect_uri=https%3A%2F%2Fauth.tesla.com%2Fvoid%2Fcallback&response_type=code&scope=openid%20email%20offline_access&state=123&login_hint=XXX%40yahoo.com

as the Request URL. (I understand that this is the same as the way you did it.) Both give errors with a status code of 500.

[Henrik "The Developer" Lindqvist]

Works as expected on my device, with just:

• Request URL: https://auth.tesla.com/oauth2/v3/authorize?client_id=ownerapi&code_challenge=123&code_challenge_method=S256&redirect_uri=https%3A%2F%2Fauth.tesla.com%2Fvoid%2Fcallback&response_type=code&scope=openid%20email%20offline_access&state=123&login_hint=XXX%40yahoo.com

[gerard....@gmail.com]

I had gotten the authentication working for a few weeks. I just noticed that it fails with a timeout. Is it possible Tesla is blocking calls from Automate somehow?  That URL works in my browser, but Automate on any platform fails with a java.net.SocketTimeoutException error.

[Henrik "The Developer" Lindqvist]

Unlikely, since Automate hasn't even connected yet.

Maybe their site is just overloaded/slow, try setting longer Timeout, default it just 15s.

[gerard....@gmail.com]

I tracked it down to the User Agent I was told to use in the header: {"User-Agent": "Mozilla/5.0 (Linux; Android 10; Pixel 3 Build/QQ2A.200305.002; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/85.0.4183.81 Mobile Safari/537.36"}

If I remove that, it works again. I think Tesla noticed that user agent is being used by scripts and is blocking it.