POST | /Admin/ReplaceUserImage |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
PhotoID | body | int | No | |
ImageData | body | string | No | |
AdminID | body | int | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
PhotoID | form | int | No | |
MemberID | form | long | No | |
MainPhoto | form | bool | No | |
Locked | form | bool | No | |
Rejected | form | bool | No | |
FileName | form | string | No | |
Classification | form | int | No | |
Width | form | int | No | |
Height | form | int | No | |
ProfileType | form | bool | No | |
IsRefer | form | bool | No | |
PhotoFolderID | form | int | No | |
Featured | form | bool | No | |
DateCreated | form | DateTime | No | |
IsAutoReview | form | bool | No | |
SortNumber | form | int | No | |
MemberLikeCount | form | int | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /Admin/ReplaceUserImage HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/json
Content-Type: application/json
Content-Length: length
{"PhotoID":0,"ImageData":"String","AdminID":0}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"PhotoID":0,"MemberID":0,"MainPhoto":false,"Locked":false,"Rejected":false,"FileName":"String","Classification":0,"Width":0,"Height":0,"ProfileType":false,"IsRefer":false,"PhotoFolderID":0,"Featured":false,"DateCreated":"\/Date(-62135596800000-0000)\/","IsAutoReview":false,"SortNumber":0,"MemberLikeCount":0}