Mercedes Benz APIs
12 APIs125 Endpoints4 Categories
Categories
API Catalog
Car Configurator
The Mercedes-Benz Car Configurator API exposes the same configuration logic that powers the Mercedes-Benz online configurator - vehicle masterdata, market and model browsing, initial and updated configurations, and saved-configuration retrieval - across 24 endpoints. Configurations are scoped by market and class so a client can fetch the right body styles, models, and option packages for a given country, then walk a customer through option selection or restore a previously saved build. The API is well suited to dealer tools, third-party automotive aggregators, and brand-experience apps that need authoritative Mercedes vehicle data.
24 endpointsCar Configurator
The Mercedes-Benz Car Configurator API exposes the same configuration engine that powers the official mercedes-benz.com configurator. It returns market-specific masterdata for bodies, classes, models, lines, and option packages, builds initial valid configurations, applies user changes with constraint validation, and persists saved configurations under shareable IDs. Markets, vehicle classes, available equipment, and pricing all vary by region, so every operation is scoped to a marketId.
24 endpointsCar Configurator
Jentic publishes the only available OpenAPI specification for Car Configurator, keeping it validated and agent-ready. The Mercedes-Benz Car Configurator API exposes the configuration engine that powers mercedes-benz.com, returning market-scoped masterdata for bodies, classes, models, and lines, building initial valid configurations, applying option changes with rule validation, and persisting saved configurations under shareable IDs. Markets, classes, equipment, and pricing all vary by region, so every operation is parameterised by marketId.
Connect 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.