<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>fleet-api on SnoWake.dev - Cloud, AI, GridTech, Security, Drones, 3D Printing & More</title><link>https://snowake.dev/tags/fleet-api/index.xml</link><description>Recent content in fleet-api on SnoWake.dev - Cloud, AI, GridTech, Security, Drones, 3D Printing & More</description><generator>Hugo -- 0.151.0</generator><language>en-us</language><lastBuildDate>Sun, 14 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://snowake.dev/tags/fleet-api/index.xml" rel="self" type="application/rss+xml"/><item><title>The Tesla Owner API Isn't Dead — Your TLS Version Is</title><link>https://snowake.dev/posts/tesla-owner-api-tls-version/</link><pubDate>Sun, 14 Jun 2026 00:00:00 +0000</pubDate><guid>https://snowake.dev/posts/tesla-owner-api-tls-version/</guid><description>I tried to move TeslaMate off Tesla's metered Fleet API to kill a $25/mo bill. It detonated into a five-hour, two-wrong-diagnoses debugging marathon that ended at the last layer anyone checks: the TLS version of a token refresh — which, it turns out, silently decides what scope your token gets.</description></item></channel></rss>