tesla-api VS Grape

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.

Grape’s support extends to standard conventions, multiple format support, content negotiation, versioning, etc. The complete guide to Grape to develop REST-APIs, test the API and analyze the performance metrics is available on its official GitHub page.

Grape (ruby-grape.org)

I'm very ambivalent about Grape, but this very much reminds me of something I do really like about it: the param validation. https://github.com/ruby-grape/grape#parameters

I am currently working on developing and api using grape and devise jwt for user user authentication.

Your RN app will be making http requests to your server, so it doesn't really matter what backend language/framework you use. If your React work was also utilizing http requests to fetch data, then there shouldn't be much of a difference. If your backend is a simple JSON api, checkout Grape. You can tack it on to any existing Rails app.

I've benchmarked Grape with YJIT and without it (if want to see the code, visit repo)

Grape is a REST-like microframework written in Ruby programming language. Grape is also considered among the best ruby frameworks and can be used to run on top of Rack or can be used to complement the existing web application frameworks such as Sinatra or Rails. The latter can be done through the DSL-based REST-API for communication. The Grape ruby web framework facilitates efficient and meaningful APIs working in the web application domain.

Take a look at Grape - https://github.com/ruby-grape/grape

I love the Grape gem for building APIs - might be worth considering if you are building something new: https://github.com/ruby-grape/grape

Grape is a REST-like API framework for Ruby. It’s designed to run on Rack or complement existing web application frameworks such as Rails and Sinatra by providing a simple DSL to easily develop RESTful APIs. 9,200 stars by now