Mercedes.VehicleManagement.API

<back to all web services

SecuredStatusRequest

Vehicle
Requires Authentication
The following routes are available for this service:
POST/v1/Vehicle/SecuredStatusSet secured status for vehicle
SecuredStatusRequest Parameters:
NameParameterData TypeRequiredDescription
CommissionNumberbodystringYes
VehicleTypebodystringYes
ReasonbodystringYes
SecuredbodyboolNo
ValidateSecuredStatusResponse Parameters:
NameParameterData TypeRequiredDescription
ValidateVehicleResponsesformList<ValidateVehicleResponse>Yes
ValidateVehicleResponse Parameters:
NameParameterData TypeRequiredDescription
CommformstringYes
FailureReasonformstringNo
FailureReasonIdformint?No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /v1/Vehicle/SecuredStatus HTTP/1.1 
Host: uat-api-vehicle-mgt-mb-dhc.rapp-customers.co.uk 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"commissionNumber":"String","vehicleType":"String","reason":"String","secured":false}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"validateVehicleResponses":[{}]}