Mercedes.VehicleManagement.API

<back to all web services

CentralVehiclesCsvRequest

Vehicle
Requires Authentication
The following routes are available for this service:
POST/v1/{VehicleType}/Vehicle/CentralCsvFilter central vehicle data for CSV
CentralVehiclesCsvRequest Parameters:
NameParameterData TypeRequiredDescription
MinbodyintNo
MaxbodyintNo
NoPortArrivalDatebodyboolNo
VehicleTypepathstringYes
CentralStockResponse Parameters:
NameParameterData TypeRequiredDescription
VehiclesformIEnumerable<CsvVehicleData>Yes
CsvVehicleData Parameters:
NameParameterData TypeRequiredDescription
CommissionNumberformstringYes
RetailerformstringYes
DescriptionformstringYes
ModelformstringYes
ColourformstringYes
FuelTypeformstringYes
TransmissionformstringYes
OtrformstringYes
DaysSincePortArrivalformint?No
OfferAmountformstringYes
OfferExpiryformstringYes
ActiveOffersformList<string>Yes
ModifiedformstringYes
RetailPriceformstringYes
VinformstringYes
ElectricRangeformintNo
ElectricConsumptionformintNo
CampaignMessagesTotalformintNo
CampaignPersonalisedOfferTotalformintNo

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

HTTP + JSV

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: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	min: 0,
	max: 0,
	noPortArrivalDate: False,
	vehicleType: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	
}