RAPP.Mercedes.VanCustomerAccount.Api

VehicleDetails

The following routes are available for this service:
POST	/vehicledetails/

**VehicleDetails** Parameters:
Name	Parameter	Data Type	Required	Description
CIAMId	body	string	No
ChassisNumber	body	string	No

**VehicleDetailsResponse** Parameters:
Name	Parameter	Data Type	Required
Status	form	ReturnStatus	No
KeeperName	form	string	No
DriverName	form	string	No
AfterSaleName	form	string	No
RegistrationDate	form	DateTime?	No
AcquisitionDate	form	DateTime?	No
FuelType	form	string	No
LastKnownMileage	form	int	No
SellingRetailer	form	string	No
ServicingRetailer	form	string	No
Colour	form	string	No
BodyType	form	string	No
Model	form	string	No
RegistrationNumber	form	string	No
ChassisNumber	form	string	No
Return	form	int	No

**ReturnStatus** Parameters:
Name	Parameter	Data Type	Required	Description
ReturnCode	form	string	No
Message	form	string	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 /vehicledetails/ HTTP/1.1 
Host: webservices.mbukdatabase.co.uk 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"CIAMId":"String","ChassisNumber":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Status":{"ReturnCode":"String","Message":"String"},"KeeperName":"String","DriverName":"String","AfterSaleName":"String","RegistrationDate":"\/Date(-62135596800000-0000)\/","AcquisitionDate":"\/Date(-62135596800000-0000)\/","FuelType":"String","LastKnownMileage":0,"SellingRetailer":"String","ServicingRetailer":"String","Colour":"String","BodyType":"String","Model":"String","RegistrationNumber":"String","ChassisNumber":"String","Return":0}