General IBM Connections feed retrieval
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 following feeds represent the URLs that can be used to retrieve information regarding the current users activity stream

Details


As per the OpenSocial standard, a given users Activity Stream is retrievable by:
1. Specifying that user (@me in the URLs below, IBM Connections does not generally allow retrieval of other users streams)
2. Specifying the group in question (@all in the URLs below, IBM Connections does not generally allow filtering by groups except in the case of status updates)
3. Specifying the application. Each application can be described by the appropriate id. In the case of 3rd Parties, this will be the generator id that was submitted with the event. @all can be used if a single stream of events from all applications is desired.

In each case, the event stream in will be returned filtered as requested. The following applications will work as expected but have specific additional considerations that are discussed in more detail in later sections.

  • @communities - this covers any events you receive as a result of communities you are following and so the generator id you will see can be from the submitting component application and not always 'communities'
  • @tags - this covers any events you receive as a result of tags you are following and so the generator id you will see will be from the submitting component application and never 'tags'
  • @people - this covers any events you receive as a result of people you are following and so the generator id you will see can be from the submitting component application and not always 'profiles'
  • @status - this covers status updates that may be received from either the profiles application or the communities application

Note: In the case of tags, profiles and status_updates above, you will only ever see public events that comply with this filter. Communities will show all events so long as you are following and have access to the community in question.

My Activity Stream: /activitystreams/@me/@all

Filtered by Blogs: /activitystreams/@me/@all/blogs

Filtered by Activities: /activitystreams/@me/@all/activities

Filtered by Files: /activitystreams/@me/@all/files

Filtered by Forums: /activitystreams/@me/@all/forums

Filtered by Wikis: /activitystreams/@me/@all/wikis

Filtered by Profiles: /activitystreams/@me/@all/@people

Filtered by Status Updates: /activitystreams/@me/@all/@status

Filtered by Tags: /activitystreams/@me/@all/@tags

Filtered by Communities: /activitystreams/@me/@all/@communities

Filtered by Bookmarks: /activitystreams/@me/@all/bookmarks

Filtered by Third-Party Apps: /activitystreams/@me/@all/[generatorid]

Single event details: /activitystreams/@me/@all/@all/[eventid]

Object History: /activitystreams/@me/@all/blogs?filterBy=object&filterOp=equals&filterValue=[blogid]
Input
Method URI Description
GET /connections/opensocial/{auth}/rest/activitystreams/@me/@all My activity stream
GET /connections/opensocial/{auth}/rest/activitystreams/@me/@all/{application} My activity stream filtered by application
GET /connections/opensocial/{auth}/rest/activitystreams/@me/@all/{eventid} Single event details
GET /connections/opensocial/{auth}/rest/activitystreams/@me/@all/{generatorid} My application stream filtered by Third-Party Apps
GET /connections/opensocial/{auth}/rest/activitystreams/@me/@all/{application}?filterBy=object&filterOp=equals&filterValue={appItemId} My activity stream object history
Name Type Optional Description
application
enumerated Yes Application type
Authorized values:
  • activities
  • blogs
  • files
  • forums
  • wikis
  • @people
  • @status
  • @tags
  • @communities
  • bookmarks
eventId
string Yes Specific event Id
generatorid
string Yes Generator ID
appItemId
string Yes e.g. blogId . Used when getting object history
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.