Model S REST API

[hans]

There is another Tesla API NodeJS library available: teslajs

Just to clarify, the teslams javascript library does not login for every API call. It only does a login once and caches the token in memory for the life of the application and reuses it for all subsequent api calls. If your javascript app never exits, it will not ever need to login again for 90 days.

 

[ACDriveMotor]

@hans Yes, sorry and thank you for clarifying that point. What I've found however is that if you have a scheduled task, rather than a long-lived app/process, for data-logging you must login each time because the token is not exposed via the API. For my purposes that is less desirable than re-using the OAuth token. I see from recent discussions on teslams that similar changes are being considered.

 

[jsgoecke]

I did get the Autopark API call to work and added to the Golang lib I wrote here: tesla/commands.go at master · jsgoecke/tesla · GitHub

 

[jsgoecke]

On 'trigger_homelink' I see that @timdorr posted this:

There are a couple calls for the auto park (Summon) and homelink features. I'm working on them now. But here's the gist of it:

trigger_homelink: lat, lon, token​

But that can't be all of the fields if you have more than one garage door configured. Any ideas of the full definition?

 

[ACDriveMotor]

What is the token param? Earlier in the thread it said something about BT.

 

[ACDriveMotor]

When I call trigger_homelink I get back a result of "unavailable" passing in the vehicle lat/long from my garage with the FOB in the car. No AP hardware in my car.

 

[Prefect]

Is this documentation still up to date? Tesla Model S JSON API · Apiary

Reading all parameters works just fine, but I can't get any of the commands to work. I get just a "404" back.

If I omit the "curl_setopt($ch, CURLOPT_POST, TRUE);" (which is the only difference to reading data) I seem to get an error back right from the firewall (graphical html 404 error message).

The api documentation also lists not all the parameters I get back. Is there an updated api documentation somewhere?

 

[ACDriveMotor]

The documentation is mostly up to date. Some of the newer commands are missing: calendar, homelink, autopark/summon

 

[ACDriveMotor]

Good news, everyone!

I finally updated the API docs for the new oAuth API and some of the new endpoints: Tesla Model S JSON API · Apiary

If anyone has any ideas about the upcoming_calendar_entries, notification_preferences, and vehicle_subscriptions endpoints (or any that I've missed), I can get those added too.

Bumping this up as it would be nice to see these documented. To that list I would add trigger_homelink and autopark_request

 

[jsgoecke]

BTW, I posted this today:

Commanding a Tesla Model S with the Amazon Echo

Having said this, it feels that the API implementation (aka - docs) for trigger_homelink and auotpark aren't necessarily complete:

- Autopark

tesla/commands.go at master · jsgoecke/tesla · GitHub

- Trigger Homelink

tesla/commands.go at master · jsgoecke/tesla · GitHub

 

[Prefect]

The response parameters are nowhere near complete. I get about twice as many fields back from charge-state than are in the documentation. But that is not a problem. My problem is, that I cannot issue any commands. I always get "404" as an answer. Where should I start looking? I copied the php exampe 1:1. Reading is not a problem and works fine.

 

[jsgoecke]

I would have to see the PHP code to understand what is happening. As the API itself does work, so something is wrong in the lib/code you are using.

 

[wayner]

What about set charge time? Has anyone found how to do that in the API yet? I thought I saw a post where someone said that they thought it was being added or had been added, but not yet documented.

 

[Prefect]

jsgoecke:

This code works and I get the json array back:

<?php

include_once("settings.php");
include_once("db_connect.php");
include_once("functions.php");


$ch = curl_init();

$token = getAccessToken();


$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, "https://owner-api.teslamotors.com/api/1/vehicles/".$VEHICLE_ID."/data_request/vehicle_state");
//curl_setopt($ch, CURLOPT_URL, "https://owner-api.teslamotors.com/api/1/vehicles/".$VEHICLE_ID."/command/honk_horn");

curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
curl_setopt($ch, CURLOPT_HEADER, FALSE);

//curl_setopt($ch, CURLOPT_POST, TRUE);

curl_setopt($ch, CURLOPT_HTTPHEADER, array(
  "Authorization: Bearer $token"
));

$response = curl_exec($ch);
curl_close($ch);

var_dump($response);

This one gives me a "404" back: (just switched the two curl URL lines and uncommented the CURLOPT_POST line)

<?php

include_once("settings.php");
include_once("db_connect.php");
include_once("functions.php");


$ch = curl_init();

$token = getAccessToken();


$ch = curl_init();

//curl_setopt($ch, CURLOPT_URL, "https://owner-api.teslamotors.com/api/1/vehicles/".$VEHICLE_ID."/data_request/vehicle_state");
curl_setopt($ch, CURLOPT_URL, "https://owner-api.teslamotors.com/api/1/vehicles/".$VEHICLE_ID."/command/honk_horn");

curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
curl_setopt($ch, CURLOPT_HEADER, FALSE);

curl_setopt($ch, CURLOPT_POST, TRUE);

curl_setopt($ch, CURLOPT_HTTPHEADER, array(
  "Authorization: Bearer $token"
));

$response = curl_exec($ch);
curl_close($ch);

var_dump($response);

And if I omit the

curl_setopt($ch, CURLOPT_POST, TRUE);

the firewall gives me a html 404 page.

Thanks for helping

 

[ACDriveMotor]

What about set charge time? Has anyone found how to do that in the API yet? I thought I saw a post where someone said that they thought it was being added or had been added, but not yet documented.

I don't believe this is available as an option yet. Setting charge_current and scheduled_charge would be useful and important additions to the API.

 

[L-P-G]

I've been playing with PowerShell on my PC to test out the capabilities of the API and I've been able to do most functions, lock/unlock, get data/state/etc, activate homelink, etc. However, trying to open the sunroof seems to not like any states, Here's my code (minus the code to get the token)

$headers = @{'Authorization' = "Bearer $($token.access_token)" }
$restResponse = Invoke-RestMethod -Uri "https://owner-api.teslamotors.com/api/1/vehicles/$($vehicle.id)/command/sun_roof_control?state=move&percent=50" -Method Post -Headers $headers

I've seen mixed replies as to what the command is, the APIary says to use:

($state being, vent, open, close, comfort)

state=$state=$state&percent=$percent

Or

state=$state

Then I've seen other people use

state=$state=move&percent=$percent

But to no avail they all return with

unknown state requested

has this functionality been removed from the API?

 

[hans]

try putting the state value encoded as form parameters rather than in the url.

The sunroof control, set_temperature, and a few others I can't remember off the top of my head are all form encoded

 

[ACDriveMotor]

Yes. The timdorr docs don't yet captures this difference.

 

[L-P-G]

try putting the state value encoded as form parameters rather than in the url.

The sunroof control, set_temperature, and a few others I can't remember off the top of my head are all form encoded

That did it, I feel dumb not even trying that first, thanks for the info.

 

[Prefect]

Sorry to ask again, but I am stuck.

Why does that not work? It is copied from the API docs php sample:

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, "https://owner-api.teslamotors.com/api/1/vehicles/".$VEHICLE_ID."/command/honk_horn");

curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
curl_setopt($ch, CURLOPT_HEADER, FALSE);

curl_setopt($ch, CURLOPT_POST, TRUE);

curl_setopt($ch, CURLOPT_HTTPHEADER, array(
  "Authorization: Bearer $token"
));

$response = curl_exec($ch);
curl_close($ch);

var_dump($response);

I just get a 404 back. All the request-type functions work, but all the command ones don't.