Mercedes.VehicleManagement.API

CentralVehiclesCsvRequest

Vehicle

The following routes are available for this service:
POST	/v1/{VehicleType}/Vehicle/CentralCsv	Filter central vehicle data for CSV

**CentralVehiclesCsvRequest** Parameters:
Name	Parameter	Data Type	Required
Min	body	int	No
Max	body	int	No
NoPortArrivalDate	body	bool	No
VehicleType	path	string	Yes

**CentralStockResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Vehicles	form	IEnumerable<CsvVehicleData>	Yes

**CsvVehicleData** Parameters:
Name	Parameter	Data Type	Required
CommissionNumber	form	string	Yes
Retailer	form	string	Yes
Description	form	string	Yes
Model	form	string	Yes
Colour	form	string	Yes
FuelType	form	string	Yes
Transmission	form	string	Yes
Otr	form	string	Yes
DaysSincePortArrival	form	int?	No
OfferAmount	form	string	Yes
OfferExpiry	form	string	Yes
ActiveOffers	form	List<string>	Yes
Modified	form	string	Yes
RetailPrice	form	string	Yes
Vin	form	string	Yes
ElectricRange	form	int	No
ElectricConsumption	form	int	No
CampaignMessagesTotal	form	int	No
CampaignPersonalisedOfferTotal	form	int	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/{VehicleType}/Vehicle/CentralCsv HTTP/1.1 
Host: uat-api-vehicle-mgt-mb-dhc.rapp-customers.co.uk 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"min":0,"max":0,"noPortArrivalDate":false,"vehicleType":"String"}

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

{}