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 · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
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
Known 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
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?