Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | path | long | No | |
Scammer | body | bool | No | |
TitleApproved | body | bool | No | |
AboutMeApproved | body | bool | No | |
LookingToMeetApproved | body | bool | 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>
<PostAdminProfileApproval xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<AboutMeApproved>false</AboutMeApproved>
<Id>0</Id>
<LookingToMeetApproved>false</LookingToMeetApproved>
<Scammer>false</Scammer>
<TitleApproved>false</TitleApproved>
</PostAdminProfileApproval>
</soap12:Body>
</soap12:Envelope>