Flag a comment as inappropriate 

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

See Authenticating requests for information about how to authenticate the request.

To flag a blog comment as inappropriate...

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:
   

   <link 
    rel="self" 
    type="application/atom+xml" 
    href="http://example.com/blogs/modtest/feed/comment/atom?commentid=
     3e1a6146-71af-414e-8b19-4da2f5d0a875&amp;lang=en_us"/>

   
   

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:
   

   <?xml version="1.0" encoding="utf-8" ?>
   <entry xmlns="http://www.w3.org/2005/Atom">
   <id>ignored</id>
   <title>ignored</title>
   <author><name>ignored</name></author>
   <category 
    scheme="http://www.ibm.com/xmlns/prod/sn/issue" 
    term="001" 
    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>
   </entry>

   
   

3. Pass the report entry document in with the POST request detailed in the table.
   

Table 1. Atom API request details

Method	Resource	URI	Input representation
POST	Inappropriate content reporting mechanism	/{homepage}/api/reports/comments Note: {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. Note: Starting with version 3, use this URI to flag a post.	report
POST	Inappropriate content reporting mechanism	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.	report

Input

Provide a report Atom entry document. The content type of the Atom entry document must be application/atom+xml.

Output

None.

Returned HTTP headers

HTTP/1.1 204

Indicates that the flag was accepted. If an error occurs, this header contains one of the error codes.

Errors

• HTTP/1.1 400 Bad Request

• HTTP/1.1 401 Unauthorized

• HTTP/1.1 403 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.

• HTTP/1.1 404 Not Found : Can be returned when the content you are trying to flag is no longer available. It has been deleted, for example.

• HTTP/1.1 405 Not Found: Can be returned when flagging is disabled.

Parent topic

Flag blog content

Related reference
Getting a list of inappropriate content flag options for Blogs
Navigate Blogs subscription API resources
Navigate Blogs publishing API resources
Report entry content

   

 

});

+

Search Tips   |   Advanced Search