-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Model S REST API
- Thread starter timdorr
- Start date
-
- Tags
- Model S User Interface
I'm not sure what that means. The apiary doc seems to have more commands and parameter settings than the official application. Was there just trial and error? Did someone set up a proxy to capture traffic?
I can't answer that exact question, but I believe that Tim was able to get the client_id by de-compiling the phone app...
Yep, it was originally some MITM proxy watching. Then I just decompiled the Android APK. In the new React Native version, they actually have a JSON file with all the endpoints listed: Tesla API Endpoints · GitHub
BTW, that shows a new /data endpoint. That gets a combination of all the *_state endpoints so you can get all that info in one call instead of 5
Thanks, Tim. Nice work. I'm looking forward to Tesla opening up new capabilities.Yep, it was originally some MITM proxy watching. Then I just decompiled the Android APK. In the new React Native version, they actually have a JSON file with all the endpoints listed: Tesla API Endpoints · GitHub
BTW, that shows a new /data endpoint. That gets a combination of all the *_state endpoints so you can get all that info in one call instead of 5
wschenk
Member
BTW, that shows a new /data endpoint. That gets a combination of all the *_state endpoints so you can get all that info in one call instead of 5
I'm very excited about this. We'll be able to simplify our processing quite a bit. This is what we do now:
Why Short Term memory is a thing: forgetting as a creative act
Just a heads up that the https://owner-api.teslamotors.com SSL certificate expires on 20th April 2017, so hopefully they will be installing a new cert soon, which may affect SSL pinning etc.
Yep, it was originally some MITM proxy watching. Then I just decompiled the Android APK. In the new React Native version, they actually have a JSON file with all the endpoints listed: Tesla API Endpoints · GitHub
BTW, that shows a new /data endpoint. That gets a combination of all the *_state endpoints so you can get all that info in one call instead of 5
Thanks Tim. This JSON file does not include queries like 'vehicle_state'. The servers still respond to 'vehicle_state'. Does this mean that the 'vehicle_state' is being deprecated?
hans
P631
Those aren't new. pf is passenger side front, pr is passenger side rear, rhd is right hand drive, rt is rear trunk. These indicate if the doors are open (1) or not (0) and the rhd is a flag to tell you which side is the driver/passenger side of the car
Last edited:
josher32
Member
I'm having this exact issue with it resetting to 50% no matter what charge I use. Can you possibly email or respond with he exact Swift Code you used for uploadTask. I can't get it to work on my app for the life of me. Thanks ahead from a grateful beginner!
Hope this helps.
In essence you can see I set the percent charge to 60% in this example
let intVal:Int = 60
let strVal:String = String(intVal)
var strURL:String = ""
strURL = "https://owner-api.teslamotors.com/api/1/vehicles/" + myTesla.id + "/command/set_charge_limit"
let url = URL(string: strURL)!
let request = NSMutableURLRequest(url: url)
request.httpMethod = "POST"
request.addValue("Bearer " + teslaMgr.myTesla.token + "", forHTTPHeaderField: "Authorization")
let json: String = "percent=" + strVal
let jsonData = json.data(using: String.Encoding.utf8)
let session = URLSession.shared
let task = session.uploadTask(with: request as URLRequest, from: jsonData!, completionHandler: { data, response, error in
if let response = response, let data = data {
print(response)
print(String(data: data, encoding: String.Encoding.utf8)!)
} else {
print(error)
}
DispatchQueue.main.async(execute: {
print("Done")
})
})
task.resume()
josher32
Member
Thanks so much! Really Appreciate it! This worked perfectly. One other question. I'm struggling to parse the data for the read only fields like trying to get the current battery miles. If your app included this any chance you could send this to me. Another option is emailing it to me at [email protected]. I can seem to get the string file but can't seem to get to the dictionary file. Thanks again for your wonderful help.
I did some MITM proxy-watching hoping to be able to see how the car gets information related to super-charger occupancy.
It turns out that most of the exchanges are done using TLS (encrypted), so they are not visible. There are some xml files that are downloaded to the car, but they seem to be related to traffic condition and map. Here is an excerpt:
<Inrix docType="GetSegmentSpeedInRadius" copyright="Copyright INRIX Inc." versionNumber="9.8" createdDate="2017-03-16T00:33:59Z" statusId="0" statusText="" responseId="ebab3053-3252-4717-98d4-3bad5cd70b71"><SegmentSpeedResultSet coverage="8"><SegmentSpeedResults timestamp="2017-03-16T00:33:59Z"><Segment code="106P05014" type="TMC" speed="29" reference="63" travelTimeMinutes="1.214" /><Segment code="106N05014" type="TMC" speed="73" reference="64" travelTimeMinutes="0.51" />
It turns out that most of the exchanges are done using TLS (encrypted), so they are not visible. There are some xml files that are downloaded to the car, but they seem to be related to traffic condition and map. Here is an excerpt:
<Inrix docType="GetSegmentSpeedInRadius" copyright="Copyright INRIX Inc." versionNumber="9.8" createdDate="2017-03-16T00:33:59Z" statusId="0" statusText="" responseId="ebab3053-3252-4717-98d4-3bad5cd70b71"><SegmentSpeedResultSet coverage="8"><SegmentSpeedResults timestamp="2017-03-16T00:33:59Z"><Segment code="106P05014" type="TMC" speed="29" reference="63" travelTimeMinutes="1.214" /><Segment code="106N05014" type="TMC" speed="73" reference="64" travelTimeMinutes="0.51" />
HankLloydRight
No Roads
Thanks for pointing this out. It's a very long thread. Looks like someone has been able to get the SC live status, but was asked by Tesla to bring it down. I wonder why Tesla doesn't make that info available outside the car (e.g., through a web interface).
HankLloydRight
No Roads
We can speculate, but we'll never know for sure. Well, wk057 might know, but he's not talking.
BTW, to access the live supercharge info, it was just a simple HTTP GET call, but it was over the in-car Tesla VPN and not accessible elsewhere.
Just a short note on token expiration / refresh:
While i haven't seen it documented yet, the api seems to support token refreshing. The (documented) request for an authentication token returns a standard oAuth token including a refresh_token. Calling the /oauth/token endpoint with parameters
{ "grant_type", "refresh_token" },
{ "client_id", TESLA_CLIENT_ID },
{ "client_secret", TESLA_CLIENT_SECRET },
{ "refresh_token", <refresh token from previous request>}
seems to work and provides a new access token and a new refresh token.
I haven't got any data yet on howlong/how often it's possible to automatically renew the access token this way, but if this works well it could be helpfull for services where you don't want to store the tesla password and yet keep the api accessible.
While i haven't seen it documented yet, the api seems to support token refreshing. The (documented) request for an authentication token returns a standard oAuth token including a refresh_token. Calling the /oauth/token endpoint with parameters
{ "grant_type", "refresh_token" },
{ "client_id", TESLA_CLIENT_ID },
{ "client_secret", TESLA_CLIENT_SECRET },
{ "refresh_token", <refresh token from previous request>}
seems to work and provides a new access token and a new refresh token.
I haven't got any data yet on howlong/how often it's possible to automatically renew the access token this way, but if this works well it could be helpfull for services where you don't want to store the tesla password and yet keep the api accessible.
