Deleting following relationships using the Administration API
Added by IBM contributorIBM | Edited by IBM contributorLDD Webmaster on July 1, 2014
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Profiles administrators may delete following relationships between other users. To delete a relationship, use the HTTP DELETE method.



Profiles administrators may delete following relationships between other users. To delete a relationship, use the HTTP DELETE method.

Administrators may delete or decline connections on behalf of other users. Deleted connections cannot be restored.

The caller must specify parameters to identify the desired action and the people involved in the following relationship. The source user is the person following someone, the target user is the person being followed.

Input

None.

Output

None.

 

 

Input
Method URI Description
DELETE /profiles/admin/atom/following.do Profiles administrators may delete following relationships between other users.
Name Type Optional Description
action
enumerated No This parameter is required. Potentially required source and target parameters are give for each action.
To remove a single following relationship provide source and target parameters and the following statement:
action=unfollow
To stop a user from following all people, provide a source parameter and the following statement:
action=unfollowall
To remove all followers for a user, provide a target parameter and the following statement:
action=removeallfollowers
Authorized values:
  • unfollow
  • unfollowall
  • removeallfollowers
sourceEmail
string Yes Internet email address of the user.
Format the HTTP request using the proper URL encoding. For example, the encoded form of the @ symbol is %40 as in the following:
adam_eventide%40garden.com
Note: Do not use if configured to prevent email addresses from being displayed. Doing so will return an error code 400 for an invalid request. Use the key or userid parameters instead.
sourceKey
string No An ID generated by Profiles to identify a person.
Note: A user's key value is contained in the element with a class attribute value of x-profile-key in the user's profile feed. You can access a user's feed by searching all profiles by name, which returns information you can then use to retrieve the person's feed.
sourceUserid
string Yes A unique ID that represents a specific person. To determine a person's user ID, you can search all profiles for the person by name. The returned feed identifies the person's user ID in the <snx:userid> element.
targetEmail
string Yes Internet email address of the user.
Format the HTTP request using the proper URL encoding. For example, the encoded form of the @ symbol is %40 as in the following:
adam_eventide%40garden.com
Note: Do not use if configured to prevent email addresses from being displayed. Doing so will return an error code 400 for an invalid request. Use the key or userid parameters instead.
targetKey
string No An ID generated by Profiles to identify a person.
Note: A user's key value is contained in the element with a class attribute value of x-profile-key in the user's profile feed. You can access a user's feed by searching all profiles by name, which returns information you can then use to retrieve the person's feed.
targetUserid
string Yes A unique ID that represents a specific person. To determine a person's user ID, you can search all profiles for the person by name. The feed that is returned identifies the person's user ID in the <snx:userid> element.
Output
Code Description
200
Indicates that the connection was successfully deleted.
400
Bad Request.
403
Unauthorized.
404
Not Found.