Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
CountryId | body | short | No | |
HeaderMessage | body | string | No | |
BodyMessage | body | string | No | |
Subject | body | string | No | |
MemberID | body | long | No | |
Handle | body | string | No | |
EmailAddress | body | string | No | |
SenderHandle | body | string | No | |
SenderAge | body | string | No | |
SenderState | body | string | No | |
SenderImgSrc | body | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .soap12 suffix or ?format=soap12
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /soap12 HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<PostSendAdminInteractionEmail xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<BodyMessage>String</BodyMessage>
<CountryId>0</CountryId>
<EmailAddress>String</EmailAddress>
<Handle>String</Handle>
<HeaderMessage>String</HeaderMessage>
<MemberID>0</MemberID>
<SenderAge>String</SenderAge>
<SenderHandle>String</SenderHandle>
<SenderImgSrc>String</SenderImgSrc>
<SenderState>String</SenderState>
<Subject>String</Subject>
</PostSendAdminInteractionEmail>
</soap12:Body>
</soap12:Envelope>