The iOS app was acting up for me at the same time their servers were having trouble with API calls. Everything has normalized from my end.
-
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
rog
Member
Does anyone by any chance have a working Javascript implementation for the "new" streaming Summon / Autopark method? Any help would be much appreciated.
rog
Member
SG57
Former Vendor
Hey all, is there a definitive wake up process established? I've read many variations thought we could come up with a trusted method.
My idea (can't test as my model S doesn't arrive til September):
We have a lot of unofficial API documentations out there, but it seems we're lacking a resource for the real world usage of them. Another good example would be the streaming API, something even the unofficial documentations are lacking (please prove me wrong!)
My idea (can't test as my model S doesn't arrive til September):
- Poll */vehicles*
- Check vehicle *state*
- If *online*, done.
- If not *online*, continue.
- Send *wake_up*
- Repeat 1 & 2 with delay until timeout
We have a lot of unofficial API documentations out there, but it seems we're lacking a resource for the real world usage of them. Another good example would be the streaming API, something even the unofficial documentations are lacking (please prove me wrong!)
Hi All,
New to this thread. I'm trying to make my own Tesla app for windows in Visual Basic. I'm using the code from the API docs and it returns an access token. However, passing that token into the header give me a 404. Is the API playing up or is there a special way to pass the token to the server? I'm happy to give my code to a VB expert for critique.
New to this thread. I'm trying to make my own Tesla app for windows in Visual Basic. I'm using the code from the API docs and it returns an access token. However, passing that token into the header give me a 404. Is the API playing up or is there a special way to pass the token to the server? I'm happy to give my code to a VB expert for critique.
fact200
Member
Hi All,
Author of the EV Watch and Tesla Waze Website here. Seeing all the difficulties with the API, I'm experimenting with a new project to provide an alternate Tesla API endpoint. The main objectives are to:
Tesla API Simulator
Disclaimer: This is at *alpha* development stage. Especially the autopark/web sockets stuff which I haven't been able to verify; my model S is pre-autopilot and the current implementation is just an approximation based off of various threads.
Author of the EV Watch and Tesla Waze Website here. Seeing all the difficulties with the API, I'm experimenting with a new project to provide an alternate Tesla API endpoint. The main objectives are to:
- Avoid having to hit your personal Telsa account and potentially trigger any rate limits or suffer any side effects
- Test with different configurations without having to actually own them (e.g. Multiple Teslas or alternate models like the Model X).
- Potentially have more insight into error conditions outside of what the stock REST api provides. (e.g. "Your token is wrong" ,"your vehicle id is wrong", "value makes no sense", etc..)
- Ability to emulate external state changes like temperature/SOC/location/speed/doors/driving changes.
Tesla API Simulator
Disclaimer: This is at *alpha* development stage. Especially the autopark/web sockets stuff which I haven't been able to verify; my model S is pre-autopilot and the current implementation is just an approximation based off of various threads.
As someone with a single S who had to create a custom XML and put it on an Azure endpoint to test how my app would handle more than a single vehicle, let me say this: "Where were you 2 months ago!!"
J/K, this should come in really helpful, specially your new summon streaming examples which I haven't fixed on my app yet.
PS: if you want to do some testing on the Summon API against a car with Summon shoot me a PM and we can test it with my car, I have a long driveway.
Thanks.
SG57
Former Vendor
Do the auth parameters really have to be placed in the query string like that? Attempting to auth is failing on my side due to posting a JSON body instead of in the query string. Does the official API support both?
SG57
Former Vendor
And might I suggest for the 2 vehicle account to actually have 2 distinct vehicles? As is, they have the same VIN numbers which broke some items of mine that required that to be unique.
Otherwise, looks solid! Love the persistence, saves a lot of time instead of having to manually update my mock server with desired results of a command.
Otherwise, looks solid! Love the persistence, saves a lot of time instead of having to manually update my mock server with desired results of a command.
HankLloydRight
No Roads
Yeah, everything is working now. The problem was I was in the middle of debugging my code when the API went down that morning, so I couldn't tell if it was my code or the API. I assumed the API was working and kept trying to figure out why my code didn't work. Very frustrating when my code was totally fine all along!
fact200
Member
It should work although I only tested on the regular api commands and not the auth.
Ah, thought I modified the second record slightly but guess I missed some pieces. Eventually I plan to expose the functions to directly modify the underlying model.
I'm unfortunately going to be afk for the next couple weeks. Will fix these items when I get back!
Thanks for the notes!
I'm using the exact code from the API docs,
code is below:
request.Headers.Add("authorization", "Bearer {token}")
Hi,
Your emulator is awesome. I got an access token from it, but when I try this call: https://tesla.flawedmodel.com/api/1/vehicles I get a 404.
Interesting. I'm sure I'm missing something my code must be the problem.
fact200
Member
Thanks! Looking at your previous post, it looks like your auth header may not be correct. It should look like:
"Authorization: Bearer tokenXYZ"
Where tokenXYZ should be replaced by whatever you got from the oauth/token call
Hi,
My visual basic code now looks like:
request.Headers.Add("Authorization: Bearer 123123123123123123123") (random numbers are the token)
Same problem. Any help would be appreciated, I know I'm missing something.
HankLloydRight
No Roads
I believe it should read:
request.Headers.Add("Authorization: Bearer 123123123123123123123")
and not:
request.Headers.Add("Authorizationrer 123123123123123123123")
I've tried: request.Headers.Add("Authorization: Bearer 121212121212121212")
Same problem.
Starting to doubt the problem is me.
