Dealing with microblog recommendations
Added by IBM contributorIBM | Edited by Claudia R Elbourn on June 30, 2015
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

The microblogging API also supports the retrieval, addition and removal of recommendations for a microblog entry.


  • Only the id of the current user can be supplied (after /likes/) when making or deleting a recommendation. Other ids will return an HTTP 403 - Forbidden.
  • As status updates are generally public (except in the case of private communities) /ublog/@all/@all can generally be used equally well
  • The body of the POST is ignore
Method URI Description
GET /connections/opensocial/{auth}/rest/ublog/{userId}/@all/{postId}/likes/{userId} Get a recommendation for the current user if present
GET /connections/opensocial/{auth}/rest/ublog/{userId}/@all/{postId}/likes Get all users who have recommended this entry
POST /connections/opensocial/{auth}/rest/ublog/{userId}/@all/{postId}/likes/{userId} POST a recommendation for the current user
DELETE /connections/opensocial/{auth}/rest/ublog/{userId}/@all/{postId}/likes/{userId} Remove a recommendation for the current user
Content Type: application/json
Sample Request:
<!-- POST body ignored -->
Name Type Optional Description
string No is a any valid user id (including the current user in which case it is the same as specifying @me )
string No is the id returned for a microblog entry
enumerated No The authorization protocol being used by your application to access Connections Cloud.
Authorized values:
  • basic
  • oauth
Name Type Optional Description
enumerated No The authentication mechanism selected by your application to access the API.
Basic is the Base64 encoding of the IBM Connections Cloud username and password: Base64(username:password). For example, Base64(
Bearer is the oauth 2.0 access token that is generated when the user grants your application access to IBM Connections Cloud services.
See the reference topic "OAuth 2.0 APIs for web server flow" for more information.
Authorized values:
  • bearer
  • basic
Content Type: application/json
Code Description
Unauthorized. Returned when no authenticated user or no userid, email, or key parameter are provided on the request.