Speak EV - Electric Car Forums banner

Tesla releases API pricing, dev says would cost $60 million per year to run his 3rd-party app

956 views 5 replies 4 participants last post by  dirk362  
#1 ·
Tessie are the first one to take a hit...:

"It doesn’t mean much to me, but the developer of the Tessie app, a third-party Tesla analytics and automation app, used it and said on Reddit that it would cost about $60 million in API fees to run his app under this pricing model:
“I’ll owe Tesla around $60 million per year using current rate.”
That’s with 400,000 Tesla drivers reportedly using the app."

What is worrying here is that all the others will follow, Mercedes, BMW, Kia, Hyundai etc, etc.
Once when they see the cash flow, they will join.

 
#2 ·
Intelligent manufacturers will recognise third-party Apps create an ecosystem around their product that they directly benefit from. So long as usage is sensible, there should be no need for knee-jerk reaction and profit-chasing.

Tesla as usual seems to want to trailblaze ahead, but also as usual seems to have completely missed the point and it will create yet more negativity towards the company.

Hyundai/Kia for example limits the number of API calls a day by a user under their account, and in the UK that is 200. Plenty to cover any sensible usage profile from a third-party App, indeed too generous you could argue.

But if they do indeed turn to profiteering from API calls then plenty of owners will just not care and revert to whatever the native App can do and be done with it. Only a small percentage will pay, but the majority will not.

If I lost access tomorrow it would be a little inconvenient, but there's no way I'd consider paying to have the same data as the native App in a more consumable environment like Home Assistant. I would revert to maintaining what I want as information points via a spreadsheet for the stuff that matters.
And I can work manually for any automation or whatever.

It wouldn't be the end of the world, because it isn't actually important in the grand scheme of things.
 
#4 ·
If I lost access tomorrow it would be a little inconvenient, but there's no way I'd consider paying to have the same data as the native App in a more consumable environment like Home Assistant. I would revert to maintaining what I want as information points via a spreadsheet for the stuff that matters.
And I can work manually for any automation or whatever.
I used to have Tessie and I was paying for it. However, after just a few months I didn't really seen any additional benefits for me as a user, so I canceled the subscription and deleted the App.
 
  • Like
Reactions: dirk362
#3 ·
Jaguar banned all unofficial access to their API several months ago. At the time I thought this marked the beginning of the end for third party apps. If manufacturers think they can squeeze some extra revenue out of customers by charging for API access then I am sure they will. Be a nuisance if they do this though.
 
#5 ·
The third party Hello # app is much better than the official Hello Smart app, and free. The official one is adequate, but exposes far less data - for example, both will start the preconditioning, but the official one only shows the temperature and drivers heated seat. The third party one also lets me set the passenger seat and steering wheel.
 
#6 · (Edited)
I am wondering whether there is any relationship between the proposal to charge for API and recently enacted European legislation stating that certain data must be made available to consumers from IOT and energy-related devices for free.

Via a post on Mastodon, I followed a series of stories that led me to the legislation, which effectively states that manufacturers must provide access to this data for free (see point 52 of the directive).

If the official App or website is free, it is aligned with the legislation.
A third-party App doesn't have to be given free access to the same data, hence the manufacturer can see a revenue opportunity.


Edit: This link is also relevant
 
owns 2025 Kia EV6 GT-Line S
  • Like
  • Helpful
Reactions: tom66 and Padrino