Mercedes-Benz
This page provides information specific to Mercedes-Benz connected vehicles owned by individuals, including data plans, supported regions, and eligible Mercedes-Benz vehicles.
Note that this page describes data access from individual vehicle owners. If you are a fleet operator or a fleet management provider, please see the separate Learn: Mercedes-Benz Fleets page.
Available data points
You can find a breakdown of all available data points in the Auto API availability for Mercedes-Benz table.
Supported Markets
Mercedes-Benz customers in the following countries can grant third-party access to vehicle data: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, and the United Kingdom.
Data Plans
In order for a Mercedes-Benz customer to supply data through HIGH MOBILITY's Auto APIs, he or she must have an eligible vehicle with a Mercedes Me Connect subscription, the "Interface to Third Parties" service activated, and consent to providing data access to a third party.
API Data Buckets
Mercedes-Benz offers data buckets pre-tailored for specific use cases. Note that to limit data retention, data is stored for 12 hours from the time of vehicle upload. Make sure to retrieve data during this period to not miss out on any updates.
For example pricing visit our pricing page.
Pay-as-you-drive
| Allowed purpose | Auto APIs | Request Limit |
|---|---|---|
| Insurance related purposes such as distance based insurance services. | Diagnostics: mileage, timestamp | 2 requests / car / day |
Fuel status
| Allowed purpose | Auto APIs | Request Limit |
|---|---|---|
| Marketing purposes respectively product offerings in relation to remaining driving distance. | Diagnostics: fuel level, estimated range, timestamp | 1 request / car / hour |
Vehicle status
| Allowed purpose | Auto APIs | Request Limit |
|---|---|---|
To offer warning services for damage prevention, e.g. rain damage by open doors or windows caused by having them involuntarily opened. | Windows: positions, timestamp | 50 requests / car / day |
Lock status
| Allowed purpose | Auto APIs | Request Limit |
|---|---|---|
Offer warning services for theft prevention or detection. | Doors: locks, timestamp | 50 requests / car / day |
Electric vehicle
| Allowed purpose | Auto APIs | Request Limit |
|---|---|---|
| Offer smart charging services. | Charging: battery level, estimated range, timestamp | 2 requests / car / hour |
Eligible Models
| A-Class | |
| A‑Class Hatchback (W176) | 06/2016 |
| A‑Class Hatchback (W177) | 01/2018 |
| A‑Class Saloon (V177) | 07/2018 |
| B-Class | |
| B‑Class Sports Tourer (W246) | 06/2016 |
| B‑Class Electric Drive (W242 EV) | 06/2016 |
| B‑Class Natural Gas Drive (W242 CNG) | 06/2016 |
| C-Class | |
| C‑Class Cabriolet (A205) | 04/2016 |
| C‑Class Coupé (C205) | 06/2016 |
| Long-wheelbase C‑Class (V205) | 06/2016 |
| C‑Class Saloon (W205) | 06/2016 |
| C‑Class Estate (S205) | 06/2016 |
| CLA | |
| CLA Shooting Brake (X117) | 06/2016 |
| CLA Coupé (C117) | 06/2018 |
| CLS | |
| CLS Coupé (C218) | 06/2016 |
| CLS Shooting Brake (X218) | 06/2016 |
| CLS Coupé (C257) | 12/2017 |
| E-Class | |
| E‑Class Saloon (W213) | 12/2015 |
| Long-wheelbase E‑Class (V213) | 09/2016 |
| E‑Class Estate (S213) | 9/2016 |
| E‑Class Coupé (C238) | 01/2017 |
| E‑Class Cabriolet (A238) | 06/2017 |
| EQ | |
| EQA (H243) | 09/2020 |
| EQC (N293) | 09/2019 |
| EQV (4478) | 09/2020 |
| G-Class | |
| G‑Class Station Wagon (W463) | 09/2016 |
| GLA | |
| GLA (X156) | 06/2016 |
| GLC | |
| GLC (X253) | 06/2016 |
| GLC Coupé (C253) | 06/2016 |
| GLC F-Cell (N253 CH2) | 05/2018 |
| GLC (V253) | 06/2018 |
| GLE | |
| GLE (W166) | 06/2016 |
| GLE Coupé (C292) | 06/2016 |
| GLS | |
| GLS (X166) | 06/2016 |
| S-Class | |
| S‑Class (W222) | 06/2016 |
| S‑Class Cabriolet (A217) | 06/2016 |
| S‑Class Coupé (C217) | 06/2016 |
| Long-wheelbase S‑Class (V222) | 06/2016 |
| Mercedes-Maybach S‑Class (X222) | 06/2016 |
| SL | |
| SL (R231) | 03/2016 |
| SLC (R172) | 03/2016 |
| AMG GT | |
| Mercedes‑AMG GT (C190) | 06/2016 |
| Mercedes‑AMG GT (R190) | 02/2017 |
| Mercedes‑AMG GT (X290) | 07/2018 |
| V and X | |
| V‑Class (VS20) | 09/2016 |
| X‑Class (VS40) | 11/2017 |
| All later vehicles |
Consent flow
The vehicle owner has to go through the following steps in order to grant access to their Mercedes-Benz vehicle data. To support the process, we offer a consumer-oriented service called Driver by High Mobility to vehicle owners. Through a Driver account, it's possible to manage 3rd party data access to all vehicles and to monitor and revoke access at any time by visiting the Driver Dashboard. The consent flow works in every browser and in addition we offer SDKs for iOS and Android to easily include it in any native mobile application.
Click on any image to see a full-sized graphic.
OAuth2
The technical integration of the consent flow is done according to the OAuth 2.0 User Consent guide.
Step 1 | Landing screen
As soon as you trigger the consent flow, the following screen is shown to the user. If the user already has a Driver account they can use it to sign in and select one of their previously used vehicles. In this flow we assume it's a first-time user.
The logo on the top left of the view and the name "Service X" is replaced with the details that you enter for your production application in the console.
Language parameter
It's possible to set the language for the consent flow by passing in the
localeparameter when initiating the consent flow. English and German are currently supported.
Step 2 | Account Creation
The user is prompted to create an account by entering their email and selecting their country. Once the consent flow has finished, we send a confirmation email to the user with a link to set their password. The terms of use and privacy policy informs the user about our data handling which is fully GDPR compliant.
Legal transparency
You can read the Terms of Use and Privacy Policy of the Driver account on our website.
Step 3 | Car Brand Selection
In this step we ask the user to select their vehicle brand. Every manufacturer that has been activated for your production application is listed in this screen and the user can select which car they want to connect.
Brand parameter
It's possible to skip this step by passing in the
brandas a parameter when initiating the consent flow according to the OAuth 2.0 User Consent guide.
Step 4 | VIN Entry
Once Mercedes-Benz has been selected as the brand, we ask the user to enter the Vehicle Identification Number (VIN) of their vehicle. In case the vehicle has been added earlier by the user, the VIN has been stored and can be selected directly from a list. The VIN entry is used later in the consent flow when the user is forwarded to the Mercedes-Benz owner panel.
The user can find their VIN from several places. If the MercedesMe application has been installed by the user, they can open it up to see the VIN of their connected Mercedes-Benz. Another alternative is to look at the vehicle windscreen or other vehicle documents that include the VIN.
Step 5 | Permissions Consent
The most important step is the approval by the user that your service may get access to their vehicle data. The data points that are listed here are taken from the granted rights for your production application.
Once we have established user consent to share data with your service, we redirect the user to the MercedesMe portal.
MercedesMe Portal
Once the user reaches the Mercedes-Benz owner portal, the following steps are taken:
- Login with MercedesMe account
- Review of the permissions to be granted
- Consent to the data sharing
Once this has been done, there is a redirect back to High Mobility and then directly to your service using the redirect_uri that was used for the initiation of the consent flow. Note that only Redirect URIs that have been registered for your production application in the console are allowed.
All of the above steps are handled by us and Mercedes-Benz respectively with the result of you receiving an access token that can be used with any of our APIs or SDKs to start fetching data for this specific vehicle.
More Information
Should you have any questions, please contact us on our Slack channel.