telebimmer
🌐 English
EnglishSrpskiDeutschFrançaisРусскийEspañolItalianoPortuguês中文한국어PolskiČeštinaSlovenčinaSlovenščinaБългарскиNederlandsTürkçeالعربيةLietuviųLatviešuEestiHrvatskiRomânăΕλληνικάМакедонскиShqipBosanskiBahasa IndonesiaไทยTiếng Việtहिन्दीქართულიעברית日本語MagyarSvenskaDanskNorskSuomiفارسی

🛠️ Setup, FAQ & Troubleshooting

Everything you need to connect your BMW to the bot — and how to fix the most common snags. The bot reads your car's data through BMW's official CarData API, under your own account, read-only. No OBD dongle, no hardware.

⚡ Quick setup (about 5 minutes)

  1. Create your own Telegram bot with @BotFather and send its token to our registration bot.
  2. Create a CarData application in your BMW account (BMW CarData → developer area) and turn on both switches: CarData API and CarData Stream. Wait 1–2 minutes after enabling them.
  3. Send the Client ID from that application to the bot.
  4. Authorize the device code: the bot gives you a code — enter it on the BMW website, pick your car and confirm. Done.

🚨 "access_denied" on the BMW screen — how to fix

This is the single most common snag, and it is almost always one of the points below. The device code is issued fine, but BMW rejects the authorization. Check, in order:

  1. Both switches must be ON. In your CarData application both CarData API and CarData Stream must be enabled. If even one is off, BMW cannot grant the authorization and returns access_denied on every attempt. Turn both on, then wait 1–2 minutes (BMW propagates the permission slowly) before entering the code.
  2. Same BMW account for the app and the car. The device code is tied to the account that created the CarData application. When you enter the code, you must be logged into that same BMW account — the one that also owns the vehicle. App in one account, car in another → access_denied.
  3. Finish the consent — select the car and confirm. On the BMW consent screen don't stop at logging in: tick your vehicle and press Confirm/Allow. If you close the tab or don't select the car, BMW records it as declined.
  4. "500 / Invalid Access Token" is BMW's flakiness, not your config. BMW's gateway is sometimes unstable and returns 500 errors during polling. Just retry — in our experience weekday daytime is more reliable than nights and weekends.
  5. Recreated the application? Then the Client ID changed. Use the “🔑 Replace Client ID” button in the registration bot and paste the new one.

🌍 Which countries are supported?

What matters is your BMW account, not where the car is now. If BMW CarData can be switched on in your account, the bot works — including imported and used BMWs. The easiest way to check is to connect and see: if CarData is available in your account, you're all set.

🚗 Which BMW models?

Any BMW whose account supports BMW CarData — typically newer connected models with an active BMW ConnectedDrive account. If your car shows up in CarData with the two switches available, it will work.

BMW — F-series (2013–2021) · G-series · i · U: ✅ all work.
MINI Connected — F56 · F55 (2014) · F54 (2015) · F57 (2016) · F60 (2017): ✅ all work.
❌ not supported: BMW E-series · MINI R55–R61 (R-series).

🔒 Is it safe? Can it control my car?

No — and it can't. BMW CarData has no vehicle-control commands; it is data-only. The bot is read-only by design, so remote control is technically impossible. We operate under your own access (your Client ID, your account), and never scrape anything.

🏛️ Is this official?

telebimmer is an independent software (SaaS) servicenot affiliated with or endorsed by BMW. What is official is the data source: we connect only through BMW's official CarData API (read-only, under your own access). The old unofficial app-scraping methods were shut down by BMW in 2025; the official API won't break the same way.

🔐 What about my data and privacy?

Your data stays yours — stored in Switzerland on infrastructure certified to ISO 27001, SOC 2 and PCI DSS, under your own access, encrypted and read-only. We don't sell data or use it for advertising. You can erase everything at any time with /deletedata. Compliant with the EU GDPR and Switzerland's revised data-protection act (nFADP).

💬 Still stuck?

Send /support in the bot and describe what you see on the BMW screen — that usually pinpoints the issue in one message.

🔄 BMW keeps rejecting after many tries? Reset CarData

If the authorization keeps failing on BMW's side after repeated attempts — typically when you are re-linking because the old connection broke — the cleanest fix is to reset BMW CarData and start completely fresh:

  1. On the BMW site open BMW CarData → Reset («BMW CarData zurücksetzen») and press «Reset ausführen». This revokes all your data and service shares and deletes your CarData archive.
  2. Then connect again from scratch: enter your Client ID in the bot (Replace Client ID), enable both toggles (CarData API + CarData Stream), open the device-code link and confirm, and tick the telemetry attributes.

⚠️ Note: the reset also revokes any other third-party CarData access you had, so only do it when you are genuinely stuck.


Telebimmer · monitoring your car via the official BMW CarData API
Terms · Privacy · Refunds · Legal notice · Contact · Reviews · FAQ
· Not affiliated with the vehicle manufacturer ·