Flagging a comment as inappropriate
Added by IBM contributorIBM | Edited by Claudia R Elbourn on June 15, 2015
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

To flag a blog comment as inappropriate, send an Atom entry document containing the report to the Blogs content reporting mechanism.

To flag a blog comment as inappropriate, complete the following steps:







1. Find the self link of the blog comment that you want to flag by retrieving a feed of blog comments. Make a note of the value of its href attribute. For example:
2. Create a report entry document in Atom format. In it, define the blog comment that you want to flag by including a <link> element that specifies the web address you noted in the previous step in its href attribute. For example:
3. Pass the report entry document in with the POST request detailed in the table.

Method URI Description
POST /blogs/{homepage}/api/reports/comments Inappropriate content reporting mechanism.
Note: Starting with version 3, use this URI to flag a post.
POST /blogs/{homepage}/api/reports/entries/{commentId} Value of the href attribute of the <link> element with the rel="http://www.ibm.com/xmlns/prod/sn/reports" attribute for each blog entry.
Note: This method is available for backwards compatibility.
Content Type: application/atom+xml
Sample Request:
<?xml version="1.0" encoding="utf-8" ?>

<entry xmlns="http://www.w3.org/2005/Atom">







 label="Legal issue"/>

<link rel="related" href="self url from the subscription feed"/>

<content type="text">This comment contains content that is against company policy</content>

Name Type Optional Description
string No {homepage} represents the blog handle of the blog configured to be the home page of the Blogs application. The handle is defined when the home page blog is created by the administrator.
string Yes Id of the blog comment
Content Type: application/atom+xml
Code Description
Indicates that the flag was accepted. If an error occurs, this header contains one of the error codes.
Bad Request. Returned when no matching user record can be found.
Unauthorized. Returned when no authenticated user or no userid, email, or key parameter are provided on the request.
Forbidden. Can be returned when issue category support is enabled, but no category element was provided in the report entry or when flagging is disabled and you attempt to flag content.
Not Found. Can be returned when the content you are trying to flag is no longer available. It has been deleted, for example.
Method Not Allowed. Can be returned when flagging is disabled.