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/GemifinPriceListRequest HTTP/1.1
Host: data.oriem.cz
Content-Type: application/xml
Content-Length: length
<GemifinPriceListRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Gemini.Partner.Gemifin">
<Token>String</Token>
<UserId>0</UserId>
</GemifinPriceListRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<GemifinPriceListReturn xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Gemini.Partner.Gemifin">
<Data xmlns:d2p1="http://schemas.datacontract.org/2004/07/Plugin.Data.Gemini.Dto">
<d2p1:GemifinPriceListGpDto>
<UID xmlns="http://schemas.datacontract.org/2004/07/Rosa.Domain">0</UID>
<d2p1:AcceptancePayment>0</d2p1:AcceptancePayment>
<d2p1:Eyes>OneEye</d2p1:Eyes>
<d2p1:LensType>0</d2p1:LensType>
<d2p1:PriceExpectation>0</d2p1:PriceExpectation>
<d2p1:RefundAmount>0</d2p1:RefundAmount>
<d2p1:SlipAmount>0</d2p1:SlipAmount>
</d2p1:GemifinPriceListGpDto>
</Data>
<Error>false</Error>
<ErrorMessage>String</ErrorMessage>
</GemifinPriceListReturn>