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