tesla-api VS tesla-oauth2

API reference: https://github.com/timdorr/tesla-api/issues/16

It uses the TeslaPy python module. There is an unofficial list of Tesla APIs here: https://tesla-api.timdorr.com/

The easiest way to explore most of what the API could offer is though tesalmate. It's nice because you host the server and own the data yourself rather than trusting some 3rd party to do it. The API is well documented here, although the authentication is a bit convoluted, but there are helpful apps that simplify its retrieval.

I did update the unofficial Tesla API documentation to show the response to some of the energy site endpoints for my setup (Tesla inverter only). If you know Python, it’s fairly easy figure to out since the authentication work has already been done.

I don't know about any pre-built integrations, but you could build your own https://tesla-api.timdorr.com/

For the Tesla API you can use https://tesla-api.timdorr.com. Alternatively you can install some hardware in your car like CANServer https://jwardell.myshopify.com for info directly from the car.

These apps need your API credentials so that they can generate tokens on your behalf. They are most likely using the methods documented by /u/timdorr here since the API is still unofficial. Also, Tesla added CAPTCHAs to their "OAuth" flow, so apps now need to present a WebView whenever they ask to regenerate your token.

Maybe this is my lack of web dev experience showing, but when I was testing step 2 of your documentation it was unclear on whether to include the earlier request parameters in the POST body. I ended up lumping everything together (request parameters, hidden input names, identity and credential) in the body of an Invoke-WebRequest along with the session state from the first GET request and some "tesla app like" header parameters borrowed from here but no explicit cookie header, and this got me the 302 response with the redirect to /void/callback and the code to move to step 3.