Notification feeds
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

There are 3 types of notification queries available from the Activity Stream. These are queries that in some way specifically relate to the querying user as opposed to events relating to people or objects that a user has chosen to follow.

Details


Filtering of a user's stream based on notification events is done with pseudo groups -

 

Notifications for me: /activitystreams/@me/@notesforme

 

Notifications from me: /activitystreams/@me/@notesfromme

Responses to my content: /activitystreams/@me/@responses
Input
Method URI Description
GET /connections/opensocial/{auth}/rest/activitystreams/@me/{pseudoGroup} Notification events query
Name Type Optional Description
pseudoGroup
enumerated No Notifications for me: @notesforme
Notifications from me: @notesfromme
Responses to my content: @responses
Authorized values:
  • @notesforme
  • @notesfromme
  • @responses
auth
enumerated No The authorization protocol being used by your application to access Connections Cloud.
Authorized values:
  • basic
  • oauth
Name Type Optional Description
Authorization
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(twatson@us.ibm.com:password).
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
Output
Content Type: application/json
Code Description
401
Unauthorized. Returned when no authenticated user or no userid, email, or key parameter are provided on the request.