anchor.diff:  < 200
   < Content-Type: application/json
   {
  -  "id1" : { "your_rating" : 2},
  -  "id2" : { "your_rating" : 3},
  +  "id1" : { "rating" : 2},
  +  "id2" : { "rating" : 3},
   }
   
   
   Rate content.
   
  -##### Request parameters
  +##### Request parameter
   
   * `id` unique identifier of the document in Searchisko to store personalized content rating for.
  -* `my_rating` value of rating. Mandatory number from 1 to 5 (1 - worst, 5 - best). 
  -
  -POST /rest/rating/{id}{?my_rating}
  -< 200
  +
  +##### Request content
  +JSON with rating value to store. `rating` field is mandatory.
  +
  +```
  +{
  +  "rating" : 2
  +}
  +```
  +
  +POST /rest/rating/{id}
  +< 200
  +< Content-Type: application/json
   
   
   --
  
positive.code: 
  ##### Request parameters
  
  * `id` unique identifier of the document in Searchisko to get personalized content rating for.
  
  ##### Response content
  
  The response contains a JSON object where `your_rating` holds number value of rating which is number from 1 to 5.
  
  ```
  {
    "your_rating" : 2
  }
  ```
  
  
negative.code: [This document describes structure of main content object](https://github.com/searchisko/searchisko/blob/master/documentation/rest-api/content/dcp_content_object.md) which can be pushed to and retrieved or searched from DCP.
  
  # Authentication
  ## Provider authentication
  Some operation calls on REST API have to be authenticated by the Provider. The caller provides credentials (`provider` and `pwd`) via standard HTTP Basic authentication.
  
  ## User authentication
  Some operation calls on REST API have to be authenticated by the User (eg. Personalized content rating API).
  
  When Searchisko REST API is called directly from Web browser, it may be configured to cooperate with CAS SSO authentication server.
  In this case user is authenticated from his SSO session established against CAS SSO server when 'User Authentication Status API' is called.
  
  
  # Description of usual server HTTP response codes
  
  