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 /service/InsertCustomerShippingLocationRDB HTTP/1.1
Host: www.bernhardt.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<InsertCustomerShippingLocationRDB xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Emun.RestDb">
<BillAddress>String</BillAddress>
<BillAddress2>String</BillAddress2>
<BillAddress3>String</BillAddress3>
<BillCity>String</BillCity>
<BillCountry>String</BillCountry>
<BillFax>String</BillFax>
<BillName>String</BillName>
<BillPhone>String</BillPhone>
<BillState>String</BillState>
<BillZipcode>String</BillZipcode>
<BillingSource>0</BillingSource>
<CYForecast>0</CYForecast>
<ConId>String</ConId>
<ContactName>String</ContactName>
<Created>0001-01-01T00:00:00</Created>
<CreatedBy>String</CreatedBy>
<Custom10STR>String</Custom10STR>
<Custom11STR>String</Custom11STR>
<Custom12STR>String</Custom12STR>
<Custom13STR>String</Custom13STR>
<Custom14STR>String</Custom14STR>
<Custom15STR>String</Custom15STR>
<Custom1STR>String</Custom1STR>
<Custom2STR>String</Custom2STR>
<Custom3STR>String</Custom3STR>
<Custom4STR>String</Custom4STR>
<Custom5STR>String</Custom5STR>
<Custom6STR>String</Custom6STR>
<Custom7STR>String</Custom7STR>
<Custom8STR>String</Custom8STR>
<Custom9STR>String</Custom9STR>
<CustomerId>String</CustomerId>
<DNU>false</DNU>
<DefaultWarehouseId>String</DefaultWarehouseId>
<Email>String</Email>
<Exported>false</Exported>
<InfoReviewed>0001-01-01T00:00:00</InfoReviewed>
<Modified>false</Modified>
<NYForecast>0</NYForecast>
<NewLocation>false</NewLocation>
<PriceList>String</PriceList>
<RegionId>String</RegionId>
<Residential>false</Residential>
<SalesRep>String</SalesRep>
<SalesRep1Sellable>false</SalesRep1Sellable>
<SalesRep2>String</SalesRep2>
<SalesRep2Sellable>false</SalesRep2Sellable>
<SalesRep3>String</SalesRep3>
<SalesRep3Sellable>false</SalesRep3Sellable>
<SalesRep4>String</SalesRep4>
<SalesRep4Sellable>false</SalesRep4Sellable>
<SalesRep5>String</SalesRep5>
<SalesRep5Sellable>false</SalesRep5Sellable>
<ShipAddress>String</ShipAddress>
<ShipAddress2>String</ShipAddress2>
<ShipAddress3>String</ShipAddress3>
<ShipCity>String</ShipCity>
<ShipCountry>String</ShipCountry>
<ShipFax>String</ShipFax>
<ShipId>String</ShipId>
<ShipName>String</ShipName>
<ShipPhone>String</ShipPhone>
<ShipState>String</ShipState>
<ShipVia>String</ShipVia>
<ShipZipcode>String</ShipZipcode>
<SoldToId>String</SoldToId>
<Status>String</Status>
<StoreCategory>String</StoreCategory>
<StoreClass>String</StoreClass>
<StoreLocator>false</StoreLocator>
<StoreLocatorOrder>String</StoreLocatorOrder>
<StoreType>String</StoreType>
<Terms>String</Terms>
<TerritoryId>String</TerritoryId>
<WebSite>String</WebSite>
<_InfoReviewed>false</_InfoReviewed>
</InsertCustomerShippingLocationRDB>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<long xmlns="http://schemas.microsoft.com/2003/10/Serialization/">0</long>