This method deletes a specified comment, allowing moderators to delete any comments and users to delete their own comments.
If a moderator deletes a comment, the points that were awarded for that comment via Gamification will also be removed.
Note: Only logged-in users can delete their comments.
us1.gigya.com- For the US data center.
eu1- For the European data center.
au1- For the Australian data center.
ru1- For the Russian data center.
cn1- For the Chinese data center.
If you are not sure of your site's data center, see Finding Your Data Center.
|||categoryID||string||The identifier of the comments category to delete.|
|||streamID||string||The identifier of the comments stream to delete.|
|||commentID||string||The identifier of the comment to delete.|
The unique ID of a logged-in user, whose comment is to be deleted, when a user is deleting their own comment. This is the UID you receive from Gigya after a successful login of this user.
An admin can additionally use UID as a validation tool to ensure the comment being deleted is the correct one. If the UID is supplied, it will verify the specified comment is connected to the specified UID, otherwise, a No_user_permission error is returned.
|||note||object||The note is a custom object, which may include additional information about the reason for the deletion and who performed it.|
Each REST API request must contain identification and authorization parameters.
Some REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as client-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your implementation when using server-to-server REST calls, it is Recommended Best Practice to always sign the request or use a secret. A non-exhaustive list of REST APIs that this may apply to are as follows:
Please refer to the Authorization Parameters section for details.
A field that does not contain data will not appear in the response.