Mercedes.VehicleManagement.API

ValidateCarConfigOptionCodeUploadRequest

CarConfigOptionCodeValidate

The following routes are available for this service:
POST	/v1/ValidateCarConfigOptionCodeUpload	Validate car configurator option codes file

**DataProcessResponse** Parameters:
Name	Parameter	Data Type	Required
Id	form	int	No
Type	form	int	No
TypeName	form	string	Yes
StatusName	form	string	Yes
Status	form	int	No
TotalRecords	form	int	No
ProcessedRecords	form	int	No
FileName	form	string	Yes
OriginalFileName	form	string	Yes
DateCreated	form	string	Yes
DateStarted	form	string	Yes
DateFinished	form	string	Yes
GasId	form	string	Yes

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

HTTP + XML

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

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

<ValidateCarConfigOptionCodeUploadRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Mercedes.VehicleManagement.API.Shared.POCO.DataProcess.CarConfiguratorOptions" />

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

<DataProcessResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Mercedes.VehicleManagement.API.Shared.POCO.DataProcess">
  <DateCreated>String</DateCreated>
  <DateFinished>String</DateFinished>
  <DateStarted>String</DateStarted>
  <FileName>String</FileName>
  <GasId>String</GasId>
  <Id>0</Id>
  <OriginalFileName>String</OriginalFileName>
  <ProcessedRecords>0</ProcessedRecords>
  <Status>0</Status>
  <StatusName>String</StatusName>
  <TotalRecords>0</TotalRecords>
  <Type>0</Type>
  <TypeName>String</TypeName>
</DataProcessResponse>