| POST | /v1/ValidateCarConfigOptionCodeUpload | Validate car configurator option codes file |
|---|
const std = @import("std");
pub const DataProcessResponse = struct {
id: i32 = 0,
type: i32 = 0,
typeName: ?[]const u8 = null,
statusName: ?[]const u8 = null,
status: i32 = 0,
totalRecords: i32 = 0,
processedRecords: i32 = 0,
fileName: ?[]const u8 = null,
originalFileName: ?[]const u8 = null,
dateCreated: ?[]const u8 = null,
dateStarted: ?[]const u8 = null,
dateFinished: ?[]const u8 = null,
gasId: ?[]const u8 = null,
};
pub const ValidateCarConfigOptionCodeUploadRequest = struct {};
Zig ValidateCarConfigOptionCodeUploadRequest DTOs
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=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>