Legacy Profiles API
Added by IBM contributorPaul Bastide | Edited by Claudia R Elbourn on June 8, 2015
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Gets the profile data for each user out of the SmartCloud Business Support Systems. (It is not limited to a single User.) Deprecated in September 2014. Users must configure their profiles if they want to be searchable, and administrators must explicitly allow users in the organization to be searchable.

For each of the following examples, the output representation can be JavaScript™ Object Notation (JSON), Atom XML, or XML format.

Input
Method URI Description
GET /lotuslive-shindig-server/social/rest/people/@me/@self Returns the profile record of the logged in user.
If the user is in the same organization as the requestor or connected with the request, the response contains the complete profile record of the user. If the user is not part of the same organization as the requestor, is not connected with the request, but is searchable, the response contains only the user ID, display name, job title, organization ID, organization name, and photo. If the user is not part of the same organization as the requestor, is not connected with the request, and is not searchable, the response is empty.
GET /lotuslive-shindig-server/social/rest/people/lotuslive:user:{subscriberId}/@self Returns the profile record of the {user_guid} user.
If the user is in the same organization as the requestor or connected with the request, the response contains the complete profile record of the user. If the user is not part of the same organization as the requestor, is not connected with the request, but is searchable, the response contains only the user ID, display name, job title, organization ID, organization name, and photo. If the user is not part of the same organization as the requestor, is not connected with the request, and is not searchable, the response is empty.
Use the table below that represents the expected fields:
Name Type Optional Description
subscriberId
string Yes Global unique ID (GUID) which identifies the user
Name Type Optional Description
format
string Yes Format enables a user to change from json, atom or text.
Name Type Optional Description
Accept
string Yes Get my profile and specify response Format in 'Accept' request header.
responseFormat could be application/json, application/xml or application/atom+xml.