Mercedes Benz APIs
12 APIs125 Endpoints4 Categories
Categories
API Catalog(4 of 12)
Mercedes-Benz Developer API
The Mercedes-Benz Developer API is the consolidated entry point for the developer-portal product family. It exposes vehicle status (fuel level, lock state, mileage), vehicle location, remote control commands for doors and windows, an embedded car configurator surface, and the dealer locator under a single base URL. Each operation is keyed to a vehicleId or marketId so an integrator can mix telematics with shopping flows in one client.
11 endpointsRemote Diagnostic Support
The Mercedes-Benz Remote Diagnostic Support API lets authorised third parties pull on-board diagnostic data from a customer's Mercedes-Benz vehicle remotely, on the customer's consent. It returns Diagnostic Trouble Codes (DTCs), DTC snapshots from individual electronic control units (ECUs), ECU readouts, and resource readouts, scoped per vehicleId (VIN/FIN). It is built for partners such as roadside assistance providers and independent workshops who need fault data before sending a technician.
4 endpointsRemote Diagnostic Support
Jentic publishes the only available OpenAPI specification for Remote Diagnostic Support, keeping it validated and agent-ready. The Mercedes-Benz Remote Diagnostic Support API lets authorised third parties pull on-board diagnostic data from a Mercedes-Benz vehicle on the customer's consent. It returns active Diagnostic Trouble Codes (DTCs), DTC snapshots from individual ECUs, ECU readouts, and resource readouts, all scoped per vehicleId (VIN/FIN). The API is designed for partners such as roadside assistance providers and authorised workshops who need fault data before sending a technician.
4 endpointsRemote Diagnostic Support
The Mercedes-Benz Remote Diagnostic Support API lets authorised third parties pull on-board diagnostic data from a customer's Mercedes-Benz vehicle remotely, on the customer's consent. It returns active Diagnostic Trouble Codes (DTCs), DTC snapshots from individual ECUs, ECU readouts, and resource readouts, all scoped per vehicleId (VIN/FIN). It is built for partners such as roadside assistance providers and authorised workshops who need fault data before sending a technician.
4 endpointsConnect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmercedes-benz.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmercedes-benz.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.