Mercedes-Benz Mercedes me · API Governance Rules
Mercedes-Benz Mercedes me API Rules
Spectral linting rules defining API design standards and conventions for Mercedes-Benz Mercedes me.
8 Rules
error 2
warn 6
Rule Categories
mercedes
Rules
warn
mercedes-me-operation-id-camel-case
Mercedes-Benz operationIds follow the lowerCamelCase pattern with a method suffix (e.g. marketsGET, modelConfigurationsGET, onlineCodePOST).
$.paths[*][get,post,put,delete,patch].operationId
warn
mercedes-me-vehicleid-param
Vehicle-keyed paths must accept a `vehicleId` (VIN/FIN) path parameter.
$.paths[?(@property.match(/vehicles\//))]
warn
mercedes-me-summary-title-case
Operation summaries should use Title Case for consistency across Mercedes-Benz API products.
$.paths[*][get,post,put,delete,patch].summary
error
mercedes-me-host-must-be-mercedes
Mercedes-Benz APIs must be hosted at api.mercedes-benz.com.
$.host
error
mercedes-me-https-only
All Mercedes-Benz APIs must be served over HTTPS only.
$.schemes
warn
mercedes-me-apikey-or-oauth
Mercedes-Benz APIs must declare apiKey (for sandbox/reference APIs) or oauth2 (for vehicle APIs) security definitions.
$.securityDefinitions
warn
mercedes-me-error-codes-documented
Every operation should document 401, 429, and 500 in addition to its happy-path response.
$.paths[*][get,post,put,delete,patch].responses
warn
mercedes-me-no-trailing-slash
Mercedes-Benz API paths should not have a trailing slash.
$.paths[*]~