Mercedes-Benz Developer API

Name: Mercedes-Benz Developer API API
Brand: Mercedes-Benz Developer API
Availability: InStock

✓ Official Vendor SpecIOTDevice ManagementapiKey11 EndpointsREST

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

Connect the Mercedes-Benz Developer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mercedes-Benz Developer API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Mercedes-Benz Developer API API.

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

GET STARTED

Start building with Mercedes-Benz Developer API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Mercedes-Benz Developer API API for, with concrete tasks.

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

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.

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.

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.

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

11 endpoints — the mercedes-benz developer api is the consolidated entry point for the developer-portal product family.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The developer-portal apiKey and any per-customer access tokens are stored in Jentic's encrypted vault. The agent calls operations through scoped references and never sees the raw key.

Intent-based discovery

Agents search 'lock mercedes', 'mercedes fuel level', 'find mercedes dealer' — Jentic resolves each intent to the correct operation under /vehicles, /configurator, or /dealers.

Time to first call

Direct integration: 3-7 days to register, implement consent flow, and wire the 11 endpoints. Through Jentic: under 1 hour to first read once credentials are vaulted.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Car Configurator

Deeper configurator surface (24 endpoints, saved configurations, full masterdata) than the embedded /configurator subset.

Use the standalone Configurator when the integration needs saved builds or full reference data; the developer API is enough for shallow configure flows.

Complementary

Remote Diagnostic Support

Adds DTC and ECU readouts that the developer API's status endpoint does not expose.

Add Remote Diagnostic Support when the use case requires fault codes or ECU snapshots, not just fuel and lock state.

Alternative

Smartcar

Multi-brand connected-car platform covering many manufacturers with a unified API surface.

Choose Smartcar when the integration must cover non-Mercedes vehicles; choose the Mercedes Developer API when the depth and brand fidelity of the official portal matter.

FAQs

Specific to using Mercedes-Benz Developer API API through Jentic.

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.