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/post_pm_notificationList HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: application/xml
Content-Length: length
<post_pm_notificationList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.admin.pmTenant">
<email>String</email>
<token>String</token>
<tokensecret>String</tokensecret>
</post_pm_notificationList>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<post_pm_notificationListResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post.admin.pmTenant">
<message xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post">String</message>
<result xmlns="http://schemas.datacontract.org/2004/07/TenantSDK.post">0</result>
<notifications xmlns:d2p1="http://schemas.datacontract.org/2004/07/TenantSDK.post">
<d2p1:post_notifications>
<d2p1:creadate>0001-01-01T00:00:00</d2p1:creadate>
<d2p1:idnumber>0</d2p1:idnumber>
<d2p1:idtenant1>0</d2p1:idtenant1>
<d2p1:message>String</d2p1:message>
<d2p1:read_by>String</d2p1:read_by>
<d2p1:read_date>0001-01-01T00:00:00</d2p1:read_date>
<d2p1:read_yn>false</d2p1:read_yn>
<d2p1:related_table>String</d2p1:related_table>
<d2p1:related_tableID>0</d2p1:related_tableID>
</d2p1:post_notifications>
</notifications>
</post_pm_notificationListResponse>