Tesla Owner API Tutorial (All you need is your browser)

[Matutino]

Seems like the website is now down

 

[bward76]

Anyone know where to query the perf_config data anymore? Can't seem to get it from JSON apiary. Just did the uncorking and can't be sure it was done properly.

 

[avesraggiana]

Anyone know where to query the perf_config data anymore? Can't seem to get it from JSON apiary. Just did the uncorking and can't be sure it was done properly.

Nothing would beat getting some kind of confirmation via an app or some such. However, post uncorking, the car’s acceleration from a standing start has a definitive “grab and snatch” feel to it, accompanied by a noticeable increase in electrical whine. If your car was uncorked you’ll sense it and hear it the moment you press that accelerator.

I was very lucky, a very kind soul on this thread verified the uncorking for me, since I couldn’t manage it on my own, and I also downloaded the PowerTools app on my iphone. Post uncorking it consistently reads 4.1 seconds.

 

[SucreTease]

Anyone know where to query the perf_config data anymore? Can't seem to get it from JSON apiary. Just did the uncorking and can't be sure it was done properly.

"perf_config" was moved from the vehicle state into the vehicle config state:
0 to 60 uncork

 

[Stasla]

"perf_config" was moved from the vehicle state into the vehicle config state:
0 to 60 uncork

Is there a way to access vehicle config state via the apiary web api browser?

 

[Jonas_man]

Is there a way to access vehicle config state via the apiary web api browser?

No

 

[Stasla]

No

 

[ishareit]

No

Not correct... Use one of the following endpoints to get that info..
https://owner-api.teslamotors.com/api/1/vehicles/{vehicle_id}/data/
https://owner-api.teslamotors.com/api/1/vehicles/{vehicle_id}/data_request/vehicle_config

 

[ishareit]

See my reply above

 

[barjohn]

Would you mind explaining exactly how one uses your information as an endpoint in the web application?

 

[Jonas_man]

Not correct... Use one of the following endpoints to get that info..
https://owner-api.teslamotors.com/api/1/vehicles/{vehicle_id}/data/
https://owner-api.teslamotors.com/api/1/vehicles/{vehicle_id}/data_request/vehicle_config

The api exists, but how do you access it via apiary web interface is the question.
Via apiary you cannot in theory.

 

[ishareit]

Not sure how apiary is maintained or updated. But you can use Postman to make requests to any endpoint.
Postman

I am sure that you can find tons of tutorials online on how to use Postman.

 

[barjohn]

Thank you. That was pretty easy all you really need is the authorization token and the Vehicle ID (IDs) and your url command and it works nicely.

 

[SundayDriver]

Making us a bit easier. You can check config in the link:

vehicle_list and vehicle_config by a token or your access credential

 

[Jonas_man]

Not sure how apiary is maintained or updated. But you can use Postman to make requests to any endpoint.
Postman

I am sure that you can find tons of tutorials online on how to use Postman.

I know you can use postman or whatever tool. But not via apiary which was the initial question.

 

[boaterva]

Not sure it's been noted, but the iOS app "Remote S" also added most/all of the API data recently. Shows the raw Car State/Location/Climate/Charge/Config/GUI, etc. API info. And does have the perf_config under Car Config. Excellent app, in general (and nothing but a satisfied user, here!).

 

[ABC2D]

And does have the perf_config under Car Config.

IIRC, perf_config was removed from API a while back and is not being reported by Tesla anymore, I'm not sure what Remote S reports.

I just tried pulling up my car info and perf_config is not reported, below is all that reported:

"response": {
"api_version": 3,
"autopark_state": "standby",
"autopark_state_v2": "standby",
"autopark_style": "standard",
"calendar_supported": true,
"car_version": "2018.6.1 641efac",
"center_display_state": 0,
"df": 0,
"dr": 0,
"ft": 0,
"homelink_nearby": false,
"last_autopark_error": "no_error",
"locked": true,
"notifications_supported": true,
"odometer": xxxxxxxx,
"parsed_calendar_supported": true,
"pf": 0,
"pr": 0,
"remote_start": false,
"remote_start_supported": true,
"rt": 0,
"sun_roof_percent_open": null,
"sun_roof_state": "unknown",
"timestamp": xxxxxxxxxxx,
"valet_mode": false,
"vehicle_name": "xxxxxxx"

 

[barjohn]

Use Sundaydriver's link, Remote S or use Postman. It is till there but was moved to Vehicle_config instead of Config_State.

 

[ishareit]

I know you can use postman or whatever tool. But not via apiary which was the initial question.

Sorry, I misunderstood.

 

[boaterva]

IIRC, perf_config was removed from API a while back and is not being reported by Tesla anymore, I'm not sure what Remote S reports.

I just tried pulling up my car info and perf_config is not reported, below is all that reported:

"response": {
"api_version": 3,
"autopark_state": "standby",
"autopark_state_v2": "standby",
"autopark_style": "standard",
"calendar_supported": true,
"car_version": "2018.6.1 641efac",
"center_display_state": 0,
"df": 0,
"dr": 0,
"ft": 0,
"homelink_nearby": false,
"last_autopark_error": "no_error",
"locked": true,
"notifications_supported": true,
"odometer": xxxxxxxx,
"parsed_calendar_supported": true,
"pf": 0,
"pr": 0,
"remote_start": false,
"remote_start_supported": true,
"rt": 0,
"sun_roof_percent_open": null,
"sun_roof_state": "unknown",
"timestamp": xxxxxxxxxxx,
"valet_mode": false,
"vehicle_name": "xxxxxxx"

As I said, in Remote S it’s on the Car Config button which is short for Vehicle Config (to fit on the buttons).