Access vehicle data through the Mercedes-Benz developer APIs
domain: developer.mercedes-benz.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register on the Mercedes-Benz developer portal and create an application to obtain OAuth 2.0 client credentials
Subscribe your application to the relevant API products (e.g., Vehicle Status, Pay As You Drive Insurance, Electric Vehicle Status) in the portal — each product must be explicitly subscribed
Direct the vehicle owner through the Mercedes-Benz OAuth authorization flow; the owner must have a Mercedes me connected account and the vehicle must be registered to that account
Exchange the authorization code for an access token; use the token to call API endpoints such as GET /vehicles/{id}/resources/odometer/value or /fuel-level/value
Handle the simulators provided in the developer portal to test without a real vehicle; switch the base URL from the simulator to production once validated
Known gotchas
Vehicle data is only available if the physical vehicle has the Mercedes me connect subscription active and has been associated with the owner's Mercedes me account — the OAuth flow succeeds but all resource endpoints return 404 or empty if the vehicle is not enrolled
API rate limits are enforced per application and can be quite restrictive on the free developer tier; batch reads are not available so each data point requires a separate HTTP call
The portal requires each API product to be approved separately; some products (e.g., certain vehicle control APIs) are not available to third parties without a signed commercial agreement
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?