Access Ford connected vehicle data via the Ford Pro or FordPass developer API
domain: developer.ford.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Apply for API access through the Ford Developer Portal (developer.ford.com); Ford's connected vehicle APIs are not fully self-serve and require submitting a use-case description for approval
Once approved, receive OAuth 2.0 client credentials; implement the authorization code flow where the vehicle owner authenticates with their FordPass or Ford Pro account
Request appropriate scopes for the data needed (e.g., odometer, fuel level, door lock status, location); scope availability differs between consumer FordPass vehicles and commercial Ford Pro fleet vehicles
Call the vehicle status endpoints using the access token, supplying the vehicle ID (obtained from listing the user's vehicles) as a path parameter
For fleet/Ford Pro use cases, explore the Ford Pro Intelligence APIs which provide additional telematics and driver behavior data beyond the consumer FordPass scope
Known gotchas
Ford has historically had separate API programs for consumer (FordPass) and commercial (Ford Pro/Telematics) use cases with different endpoints and approval processes; verify which program applies to your use case before starting
Remote command execution (e.g., remote start, lock/unlock) requires the vehicle owner to have an active FordPass Connect subscription; the API call will fail or return an error if the subscription has lapsed
Ford's developer program terms have changed over time; third-party access to consumer vehicle data is subject to Ford's data sharing policies and can be revoked with program changes
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?