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 /xml/reply/GetPersonDataForWVA HTTP/1.1
Host: equipstage3.e-isg.com
Content-Type: application/xml
Content-Length: length
<GetPersonDataForWVA xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<ColorDescription>String</ColorDescription>
<Operation>String</Operation>
<PersonName>String</PersonName>
<UserID>String</UserID>
</GetPersonDataForWVA>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<PersonDataforWVA xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<AccountNumber>String</AccountNumber>
<AgencyClass>String</AgencyClass>
<AuthorizedRepresentatives>String</AuthorizedRepresentatives>
<ColorCode>String</ColorCode>
<Discount>0</Discount>
<EligibilityExpDate>0001-01-01T00:00:00</EligibilityExpDate>
<EmployeeDetailsEmailAddress>String</EmployeeDetailsEmailAddress>
<EmployeeDetailsOfficePhone>String</EmployeeDetailsOfficePhone>
<FullName>String</FullName>
<IsValidEligibilityExpDate>String</IsValidEligibilityExpDate>
<LicenseExpDate>0001-01-01T00:00:00</LicenseExpDate>
<PeopleAddress>String</PeopleAddress>
<PeopleAuthRep>String</PeopleAuthRep>
<PeopleCity>String</PeopleCity>
<PeopleCounty>String</PeopleCounty>
<PeopleID>0</PeopleID>
<PeopleName>String</PeopleName>
<PeopleState>String</PeopleState>
<PeopleZipCode>String</PeopleZipCode>
<People_ID_Internal>String</People_ID_Internal>
<Status>String</Status>
<Taxable>false</Taxable>
</PersonDataforWVA>