Mercedes.VehicleManagement.API

CurrentDataProcessRequest

The following routes are available for this service:
GET	/v1/GetUserCurrentDataProcess

**CurrentDataProcessResponse** Parameters:
Name	Parameter	Data Type	Required
Type	form	int	No
TotalRecords	form	int	No
OriginalFileName	form	string	Yes
DateStarted	form	string	Yes
DateFinished	form	string	Yes
DataProcessResultLogs	form	List<DataProcessLog>	Yes
FailedCount	form	int	No
SuccessCount	form	int	No

**DataProcessJob** Parameters:
Name	Parameter	Data Type	Required
Id	form	int	No
GasId	form	string	Yes
DateCreated	form	string	Yes
ProcessedRecords	form	int	No
Status	form	int	No
StatusName	form	string	Yes
FileName	form	string	Yes

**DataProcessLog** Parameters:
Name	Parameter	Data Type	Required
Id	form	int	No
DataProcess_Id	form	int	No
RowNumber	form	int	No
FailureReasonId	form	int	No
FailureReason	form	string	Yes
MetaData	form	string	Yes
MetaData2	form	string	Yes
HasFailed	form	bool	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.

GET /v1/GetUserCurrentDataProcess HTTP/1.1 
Host: uat-api-vehicle-mgt-mb-dhc.rapp-customers.co.uk 
Accept: application/json

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

{"type":0,"totalRecords":0,"originalFileName":"String","dateStarted":"String","dateFinished":"String","dataProcessResultLogs":[{"id":0,"dataProcess_Id":0,"rowNumber":0,"failureReasonId":0,"failureReason":"String","metaData":"String","metaData2":"String","hasFailed":false}],"failedCount":0,"successCount":0,"id":0,"gasId":"String","dateCreated":"String","processedRecords":0,"status":0,"statusName":"String","fileName":"String"}