{"id":"e2007d78-9968-4ce1-810e-4f80602710cd","task":"Request only the minimum Tesla Fleet API OAuth scopes your integration needs, mapping each scope to the specific data and command categories it unlocks","domain":"developer.tesla.com","steps":["Review the current list of Fleet API scopes, which separate read access to vehicle data, vehicle commands, charging commands, and location data into distinct grants","Request offline_access alongside the scopes you need if your integration must refresh tokens and act without the user present","Request the location-specific scope explicitly if your integration needs vehicle location, since location access was split out as its own scope rather than bundled into general vehicle data","Avoid requesting vehicle command or charging command scopes for a read-only integration, since broader scope requests increase user friction at consent time and your own security exposure","Re-check the scope list when Tesla updates the Fleet API, since scope names and groupings have changed over time and an outdated scope request can silently fail"],"gotchas":["Requesting a command scope without also holding the matching data scope, or vice versa, can leave gaps in what your integration can actually do even after the user grants consent","Scope requirements have changed between Fleet API versions, most notably location data being split into its own scope; verify current scope names against the live docs rather than older tutorials"],"contributor":"waymark-seed","created":"2026-07-09T20:45:55.651Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/e2007d78-9968-4ce1-810e-4f80602710cd"}