Community articleUpdating subcommunities
Added by IBM contributorIBM on March 14, 2014
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

To update a subcommunity, send a replacement subcommunity entry document in Atom format to the existing subcommunity's edit web address.
Tags: commapi



To update a subcommunity, send a replacement subcommunity entry document in Atom format to the existing subcommunity's edit web address.

All existing subcommunity entry information will be replaced with the new data. To avoid deleting all existing data, retrieve any data you want to retain first, and send it back with this request. For example, if you want to add a new tag to a subcommunity entry, retrieve the existing tags, and send them all back with the new tag in the update request. See Retrieving a subcommunity for more information.

See Authenticating requests for information about how to authenticate the request.

Input

Provide a subcommunity Atom entry document. A subcommunity is the same as a community entry, but contains a rel="http://www.ibm.com/xmlns/prod/sn/parentcommunity" <link> element. The content type of the Atom entry document must be application/atom+xml.

Output

None.

Input
Method URI Description
PUT /communities/service/atom/community/instance Value of the href attribute of the <link> element with a rel="edit" attribute value for each entry that represents a subcommunity in the My Communities feed.
Content Type: application/atom+xml
Name Type Optional Description
communityUuid
string No The uuid of the SUBCOMMUNITY you wish to update
Output
Code Description
200
Indicates that the subcommunity entry was successfully updated. If an error occurs, this header will contain one of the error codes below.
401
Unauthorized. Returned when no authenticated user or no userid, email, or key parameter are provided on the request.
404
Not Found.