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/GenerateDlmsReceiptAcknowledgementAsync HTTP/1.1
Host: equipstage2.e-isg.com
Content-Type: application/xml
Content-Length: length
<GenerateDlmsReceiptAcknowledgementAsync xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel.Dlms.Transactions">
<DoNotPublishOutboundDocument>false</DoNotPublishOutboundDocument>
<EventTag>String</EventTag>
<DirectGenerate>false</DirectGenerate>
<DlmsTransactionIDToRegenerate xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</DlmsTransactionIDToRegenerate>
<DoDAACCodeOfAFPM>String</DoDAACCodeOfAFPM>
<DocumentNumber>String</DocumentNumber>
<IdentificationID>00000000-0000-0000-0000-000000000000</IdentificationID>
<Notes>String</Notes>
<QuantityToAcknowledge>0</QuantityToAcknowledge>
<SuffixCode>String</SuffixCode>
<TransactionTypeCode>String</TransactionTypeCode>
<UserID>String</UserID>
</GenerateDlmsReceiptAcknowledgementAsync>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<z:anyType xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:z="http://schemas.microsoft.com/2003/10/Serialization/" />