PUT | /RestApi/comments-api/comments |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Key | body | string | No | |
Message | body | string | No | |
Status | body | string | No | |
Name | body | string | No | |
body | string | No | ||
CustomData | body | string | No | |
Rating | body | decimal? | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Key | form | string | No | |
Name | form | string | No | |
Message | form | string | No | |
DateCreated | form | DateTime | No | |
ProfilePictureUrl | form | string | No | |
ProfilePictureThumbnailUrl | form | string | No | |
Status | form | string | No | |
form | string | No | ||
ThreadKey | form | string | No | |
AuthorIpAddress | form | string | No | |
CustomData | form | string | No | |
Rating | form | decimal? | 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.
PUT /RestApi/comments-api/comments HTTP/1.1
Host: www.asg.com.au
Accept: application/json
Content-Type: application/json
Content-Length: length
{"Key":"String","Message":"String","Status":"String","Name":"String","Email":"String","CustomData":"String","Rating":0}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"Key":"String","Name":"String","Message":"String","DateCreated":"\/Date(-62135596800000-0000)\/","ProfilePictureUrl":"String","ProfilePictureThumbnailUrl":"String","Status":"String","Email":"String","ThreadKey":"String","AuthorIpAddress":"String","CustomData":"String","Rating":0}