Fleet API command/navigation_request endpoint

[fhteagle]

Hey all

Just converted Home Assistant to be using the new Fleet API since my vehicle finally got kicked off of Owner API this week. Used Teslemetry for the http proxy, so far so good on that.

Next bit of functionality that I am trying to restore is sending a destination to the car. The Tesla API docs on this are too sparse, no examples, etc. Tried a bunch of random strings for "type", but it always errors out. Has anyone successfully used the /command/navigation_request endpoint yet?

 

[IronCoffee_Max]

I'd love to know because all of the apps I've used that supported that capability no longer do. It's frustrating because I had an iOS shortcut that sent a location to two cars when my wife and I had to go to the same place.

Even just sending to my car was a pain because I have 4 on my account and I usually have my house on my home screen so when I send to tesla, it gives me an error. I have to open the Tesla app, pick my car, and then redo the send. I preferred my shortcut that sent it to my car specifically.

Seems like the API no longer supports it so everyone dropped it.

 

[fhteagle]

I figured out the navigation_request syntax for the Fleet API, it's the same as the old Owner API:

curl --header 'Content-Type: application/json' \
--header "Authorization: Bearer YOURTOKENHERE" \
--data '{
"type": "share_ext_content_raw",
"locale": "en-US",
"timestamp_ms": "1715867369999",
"value": {
"android.intent.extra.TEXT": "Telluride, CO, USA"
}
}' \
'https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/vehicles/YOURVINHERE/command/navigation_request'

Again, I'm using Teslemetry at the moment so the domain part of my URL is different on the last line. Yours will be too, depending on how your Fleet API proxy is set up...