Community articleUpdating a community event instance
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 community event instance, send a replacement community event instance content entry document in Atom format to the existing community event instance's edit web address.
Tags: commapi


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

All existing community event instance 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. See "Retrieving event instances from a given community" and "Retrieving event instances that belong to a given event" for more information.

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

Note: This request needs authentication.

Input

An Atom entry document containing the updated Atom document for the community event instance. The content type must be specified as application/atom+xml.

Event instance fields that allow update

Output

An Atom entry document of community event instance content.

Input
Method URI Description
PUT /communities/calendar/atom/calendar/event Value of the href attribute of the <link> element with a rel="edit" attribute value for each entry that represents an event instance in event instances feed.
Content Type: application/atom+xml
Use the table below that represents the expected fields:
Name Type Optional Description
content
string Yes The description of event instance
<snx:startDate>
string Yes The start date/time of this event instance. Specify the date using a date-time value that conforms to RFC3339. In addition, an uppercase "T" character must be used to separate date and time, and an uppercase "Z" character must be present in the absence of a numeric time zone offset. For example: 2009-01-04T20:32:31.171Z.
<snx:endDate>
string Yes The end date/time of this event instance. Specify the date using a date-time value that conforms to RFC3339. In addition, an uppercase "T" character must be used to separate date and time, and an uppercase "Z" character must be present in the absence of a numeric time zone offset. For example: 2009-01-04T20:32:31.171Z.
<snx:allday>
string Yes Whether this is an "all day" event.
<snx:location>
string Yes Location of this event instance.
Name Type Optional Description
eventInstUuid
string No Event Instance ID
Output
Content Type: application/atom+xml
Code Description
200
Indicates that the community event instance was successfully found and updated. If an error occurs, this header will contain one of the error codes below.
400
Bad Request.
403
Forbidden.
404
Not Found.