POST | /updatemileage/ |
---|
using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using RAPP.Mercedes.VanCustomerAccount.Api.ServiceModel.SitecoreServiceModels;
namespace RAPP.Mercedes.VanCustomerAccount.Api.ServiceModel.SitecoreServiceModels
{
public partial class ReturnStatus
{
public virtual string ReturnCode { get; set; }
public virtual string Message { get; set; }
}
public partial class UpdateMileage
{
public virtual string CIAMId { get; set; }
public virtual string ChassisNumber { get; set; }
public virtual int Mileage { get; set; }
}
public partial class UpdateMileageResponse
{
public virtual ReturnStatus Status { get; set; }
}
}
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 /updatemileage/ HTTP/1.1
Host: webservices.mbukdatabase.co.uk
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<UpdateMileage xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RAPP.Mercedes.VanCustomerAccount.Api.ServiceModel.SitecoreServiceModels">
<CIAMId>String</CIAMId>
<ChassisNumber>String</ChassisNumber>
<Mileage>0</Mileage>
</UpdateMileage>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <UpdateMileageResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RAPP.Mercedes.VanCustomerAccount.Api.ServiceModel.SitecoreServiceModels"> <Status> <Message>String</Message> <ReturnCode>String</ReturnCode> </Status> </UpdateMileageResponse>