canonical: https://jentic.com/apis/mercedes-benz.com/mercedes-benz-developer-api

# 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.

## For AI agents

Read vehicle status and location, send remote door/window commands, configure cars, and locate dealers across 11 endpoints from one Mercedes-Benz developer entry point.

## Scope

Does not handle service bookings, payments, deep diagnostic readouts, or vehicle imagery - use for vehicle status, location, basic remote control, configuration, and dealer search only.

## Capabilities

- Read live status (fuel, mileage, lock state) for a Mercedes-Benz vehicle by vehicleId
- Retrieve the current GPS location of an authorised Mercedes-Benz vehicle
- Send a remote command to lock or unlock the doors of a vehicle
- Send a remote command to open or close vehicle windows
- List markets, models, and configurations through the embedded configurator surface
- Look up Mercedes-Benz dealers by country from inside the same client

## Use cases

### Owner companion app

Mercedes-Benz vehicle owners and approved partners build companion apps that combine GET `/vehicles/{vehicleId}/status`, GET `/vehicles/{vehicleId}/location`, and POST `/vehicles/{vehicleId}/doors` into one experience. The customer sees fuel level, parked location, and lock state in a single view and can lock the car if they forgot to. Because every endpoint is on one base URL, the integrator manages one apiKey instead of stitching multiple products together.

Example prompt: GET `/vehicles/{vehicleId}/status` to read fuel and lock state, GET `/vehicles/{vehicleId}/location` for parked coordinates, then POST `/vehicles/{vehicleId}/doors` with the lock command if doors are open.

### Fleet operations dashboard

Fleet managers running Mercedes-Benz vehicles use the developer API to consolidate live status and location across the fleet. GET /vehicles enumerates the registered vehicleIds, then per-vehicle calls to /status and /location populate a single ops dashboard. Remote door commands give fleet ops the ability to grant or revoke access to drivers without dispatching a key.

Example prompt: GET /vehicles for the fleet, then for each vehicleId call /status and /location and write the results to the dashboard's metrics store.

### Sales journey from configure to nearest dealer

A retail integration uses the embedded configurator endpoints (`/configurator/markets`, `/configurator/markets/{marketId}/models`) to build a vehicle, then calls /dealers to surface the nearest Mercedes-Benz dealership in the customer's country. The whole sales journey lives on one base URL with one credential, simplifying integration compared to combining the standalone Configurator and Dealer APIs.

Example prompt: GET `/configurator/markets/{marketId}/models` to list models, walk the configurator path to assemble a build, then GET /dealers with the same country to return the closest dealer.

### Agent-driven vehicle command via Jentic

An AI assistant uses Jentic to action a customer request like 'lock my car' or 'how much fuel do I have left'. Jentic exposes the developer API operations by intent so the agent calls `/vehicles/{vehicleId}/status` or `/vehicles/{vehicleId}/doors` without managing the apiKey, and returns the result in chat.

Example prompt: Search Jentic for 'lock mercedes-benz doors', load the POST `/vehicles/{vehicleId}/doors` schema, execute it with the customer's vehicleId and the lock command, and return the success state.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/vehicles` | List the customer's registered Mercedes-Benz vehicles |
| GET | `/vehicles/{vehicleId}/status` | Read live vehicle status (fuel, mileage, locks) |
| GET | `/vehicles/{vehicleId}/location` | Get the vehicle's current GPS location |
| POST | `/vehicles/{vehicleId}/doors` | Send a remote door lock/unlock command |
| POST | `/vehicles/{vehicleId}/windows` | Send a remote window control command |

## Key resources

- **Vehicles** — List of vehicles registered to the user and per-vehicle status, location, and control endpoints
- **Vehicle Status** — Fuel, mileage, and lock state readings for a vehicleId
- **Vehicle Control** — Remote commands for doors and windows
- **Configurator** — Embedded configurator endpoints for markets and models
- **Dealers** — Authorised Mercedes-Benz dealer search inside the same client

## Why Jentic

- **Setup:** Wiring the Mercedes-Benz Developer API by hand means getting a developer-portal apiKey plus per-customer tokens, attaching them to each call, and coding status, location, and remote-control requests against the vehicles host yourself. Through Jentic you install once, import the Mercedes-Benz Developer API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The Developer API puts the vehicle id in the URL path (`/vehicles/{vehicleId}/status`), so a rule can pin your agent to one vehicle. You choose the operations it may call, so a rule can grant read-only status and location while leaving out remote-control writes like door or window operations unless you add them.
- **Credential handling:** Your Mercedes-Benz apiKey and any per-customer tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check Mercedes vehicle status' or 'lock the doors', and Jentic returns the matching Developer API operation with its vehicleId schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Car Configurator** — Deeper configurator surface (24 endpoints, saved configurations, full masterdata) than the embedded /configurator subset.
- **Remote Diagnostic Support** — Adds DTC and ECU readouts that the developer API's status endpoint does not expose.
- **Smartcar** — Multi-brand connected-car platform covering many manufacturers with a unified API surface.

## FAQ

### What authentication does the Mercedes-Benz Developer API use?

The spec declares an apiKey scheme. Vehicle-data endpoints additionally require a customer-authorised access flow through the Mercedes-Benz developer portal. Jentic stores the apiKey in its encrypted vault so the agent never handles it directly.

### Can I remotely lock the doors with the Mercedes-Benz Developer API?

Yes. POST `/vehicles/{vehicleId}/doors` sends a remote lock or unlock command for an authorised vehicle, provided the customer has consented and the vehicle is connected.

### What are the rate limits for the Mercedes-Benz Developer API?

Numeric limits are not in the spec - they are set per developer-portal contract. Vehicle command endpoints are deliberately rate-limited more strictly than read endpoints to avoid actuator wear.

### How do I check a customer's fuel level through Jentic?

Search Jentic for 'mercedes vehicle status', load the GET `/vehicles/{vehicleId}/status` schema, and execute it with the customer's vehicleId. The response includes fuel, mileage, and lock state in one call.

### Does this API replace the standalone Configurator and Dealer APIs?

It exposes a subset of the same functionality under /configurator and /dealers, with one apiKey and one base URL. For deeper configurator features (saved builds, full reference masterdata) the standalone Configurator API still has more endpoints.

### Can I open the windows remotely on any Mercedes-Benz vehicle?

POST `/vehicles/{vehicleId}/windows` is supported, but only on connected Mercedes-Benz vehicles whose owner has authorised the integrating application via the Mercedes-Benz developer portal consent flow.

### Can I limit what my agent is allowed to do with the Mercedes-Benz Developer API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and since the vehicle id sits in the URL path you can pin the agent to a single vehicle. You can grant read-only access to GET `/vehicles/{vehicleId}/status` and GET `/vehicles/{vehicleId}/location` while withholding the remote-control writes, so the agent cannot POST to `/vehicles/{vehicleId}/doors` or `/vehicles/{vehicleId}/windows` unless you add those operations. The apiKey and any per-customer tokens are stored by your instance and injected at execution time, never reaching the agent's prompt or logs.