-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
LineofSight
Member
I have never played with these API tokens before, but perhaps the POST command is wrong?
POST https://owner-api.teslamotors.com/api/1/vehicles/XXXXXXXXXXXXXX/command/set_charge_limit?percent=60
This is the current command. The "XXX" is my s_id #. That "?" after "set_charge_limit" does not look right to me. Maybe that is supposed to be a "/" like the other delimiters?
Computers aren't smart. If we make one small input error they cannot figure out what went wrong. GIGO Garbage In, Garbage Out
OK I got it. You ware in the right direction
The API for the set_charge_limit should have a body of:
{
"percent": <YOUR DESIRED % VALUE AS A NUMBER>
}
so the actual POST url looks like this:
https://owner-api.teslamotors.com/api/1/vehicles/20465486075957809/command/set_charge_limit
LineofSight
Member
OK I got it. You ware in the right direction
The API for the set_charge_limit should have a body of:
{
"percent": <YOUR DESIRED % VALUE AS A NUMBER>
}
so the actual POST url looks like this:
https://owner-api.teslamotors.com/api/1/vehicles/20465486075957809/command/set_charge_limit
How do I edit the POST URL to remove "?percent=xx"?
Also, should there be quotation marks around the charge limit setting in the Body command?
For Example:
{
"percent": "80"
}
ishareit
Member
Thanks @LineofSight and @Akrion for validating that its not just me. Wonder how the Remote S app does it... I tried to set proxy and capture the iPhone traffic but because of SSL pinning, these apps will not work with an SSL proxy...
ishareit
Member
Doesn't work either unfortunately...OK I got it. You ware in the right direction
The API for the set_charge_limit should have a body of:
{
"percent": <YOUR DESIRED % VALUE AS A NUMBER>
}
so the actual POST url looks like this:
https://owner-api.teslamotors.com/api/1/vehicles/20465486075957809/command/set_charge_limit
Edit: Works! I forgot to set the content type for body to json in Postman.
Works 100% in postman ...
{
"percent": 70
}
Make sure this is the url
https://owner-api.teslamotors.com/api/1/vehicles/20465486075957809/command/set_charge_limit
Forking and updating the apiary now.
ishareit
Member
Byshop303
Member
For Windows users I already wrote a Powershell script using the Tesla API Powershell module to get my vehicle data. If anyone's interested I can make a version that specifically calls out the performance config. Functionally it's the same thing as manually crafting API calls, but there are fewer manual steps because once you provide your credentials the script can handle everything else when you run it.
LineofSight
Member
The final fix for me was entering Content-Type as application/json in the Header section of the Set Charge Limit section. None of the other sections, except the initial "Tokens" section, required me to enter the Content_Type application/json into the header section again in order for the request to work. For some reason, it must be re-entered into the Set Charge Limit header section. And quotation marks were not needed around the percent number in the Body command. Whew! I shoulda stood in bed.
Hi Akrion, great video and explanation, thanks!
Quick (perhaps dumb Q) security Q: As we are pasting the password on the browser page that is hosted in the cloud/apiary, wouldn't there be a possibility that apiary/another host is perhaps logging the information?
Last edited:
As of right now, ONLY 75Ds can be "uncorked".
P1 for a 90D just means that you already have the higher performance torque curve/1300A limit for the smaller dual motors (the same that would apply to an uncorked 75D) applied to your car... So, essentially, yes, means you are "uncorked".
Just got a notification from the app that software update is available while the car is at the SC, went to to API check the value and now shows P1
Not having uncorking take makes sense. When I took mine In last week they told me it took 3 times for the update to take. I could see someone thinking it took but really didn’t if they didn’t verify. Took a few hours but performance was Definetly noticeable. Though I am kind of curious to try this check to verify a P1 still.
Similar threads
