Mercedes-Benz Mercedes me · Rate Limits

Mercedes Me Rate Limits

Mercedes-Benz documents quota enforcement implicitly through `429 Quota limit is exceeded` responses on every operation in every published Swagger spec (Car Configurator, Dealer, Remote Diagnostic Support, Vehicle Images). Specific request-per-minute and per-day limits are not published in the public spec — they are set per API key/subscription on the developer portal. The Sandbox/Tryout tier is hard-capped on the platform side; the production tiers are governed by partner contract.

Mercedes Me Rate Limits is the machine-readable rate-limit profile for Mercedes-Benz Mercedes me on the APIs.io network, conforming to the API Commons Rate Limits specification.

The profile also includes 4 backoff/retry policies defined.

Tagged areas include Automotive, Connected Car, Connected Vehicle, Daimler, and Fleet Management.

0 Limits
AutomotiveConnected CarConnected VehicleDaimlerFleet ManagementMercedes meMercedes-BenzOEMTelematicsVehicle Data

Policies

Each issued Mercedes-Benz developer API key has a quota counted across all endpoints of the subscribed product. Exceeding the quota returns HTTP 429 with no Retry-After body content per the published Swagger specs (the description string "Quota limit is exceeded" is the only signal).
The *_tryout basePaths (e.g. /configurator_tryout/v1) are hard-capped for free-tier sandbox use. Exact limit values are dictated by the developer portal subscription, not published in the spec.
Connected-vehicle APIs (Vehicle Status, Fuel Status, EV Status, Vehicle Lock Status, PAYD) are additionally throttled at the per-vehicle level to protect on-vehicle modems and avoid waking the vehicle excessively. Limits are set by Mercedes-Benz operations and are not published.
Fleet API Kafka Push topics are sized per partner subscription. Throughput is not a typical HTTP 429 — instead the Kafka consumer experiences lag or partition rebalancing if a partner cannot keep up. No public quota number is published.