Vehicle — entry 006 of 10

Mercedes-Benz

Verified Jul 2026

Mercedes-Benz's connected-vehicle API platform exposes telematics data, remote vehicle commands, a car configurator, and dealer-locator lookups behind an OAuth2 client-credentials/authorization-code flow — its own docs describe exchanging a Base64-encoded Client ID/Secret for a bearer token, correcting the stored auth from "API Key" to "OAuth". A live unauthenticated GET against the real api.mercedes-benz.com gateway returned no Access-Control-Allow-Origin header on any endpoint tested, reconfirming cors "no" — consistent with Mercedes-Benz's own documentation that the API doesn't support direct browser calls; https was reconfirmed. The platform offers a free sandbox/BYOCAR tier for testing against simulated and real vehicles, plus paid production tiers per API product — freemium.

connected-vehicletelematicsoauthfleetautomotive
AuthenticationOAuthRequires an OAuth flow; expect app registration.
HTTPSSupportedTraffic is encrypted in transit.
CORSDisabledBrowser calls need a server-side proxy.
PricingFreemiumA usable free tier exists, with paid plans for more volume.
FormatsJSONResponses can be requested as JSON.

GreatAPIs Score

Score54out of 100
Authentication8/25OAuth flow required
Pricing17/20Freemium tier available
Docs0/20No docs or spec available
Formats9/15Single response format
Freshness20/20Verified within 6 months

Embed this badge

Scored 54 on greatapis.com
<a href="https://greatapis.com/api/mercedes-benz/"><img src="https://greatapis.com/badge/mercedes-benz.svg" alt="Scored 54 on greatapis.com"></a>

Auth quickstart

  1. Register an app / run the OAuth flow to obtain a bearer token.
  2. Send it as an Authorization headerAuthorization: Bearer <token>
Stored keyNo key stored

Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.