service=addAttendeeActivity
Returns an XML payload containing the results of the attendee add activity method. The ‘stat’ attribute is used to indicate the success or failure of the request. Extended description of all options are listed below.
Sample Request URL: [End Point URL]/?do=cnt.getservice&service=addAttendeeActivity&[Parameter List]
Parameter Options:
*apiKey: Valid API key
*attendeeID: Numeric value used to identify the attendee record to update. attendeeID or registrationNumber required.
registrationNumber: String value used to identify the attendee record to update. attendeeID or registrationNumber required.
eventIDs: Comma delimited list of event to be added to a person’s activity list. eventIDs or eventID required
eventID: Numeric value identifying an event to be added to a person’s activity list. eventIDs or eventID required.
pendingTest - sets the pending post test flag when saving an activity.
conflictsAllowed - Turns off the conflict error messages.
removeConflicts - turns off the scheduling conflicts messages and inactivates the existing conflicting activities.
conflictBuffer -
conflictLevel -
The results of this call are either success for failure. Both XML payloads are described next.
Sample Success XML Payload: Includes list of the activity identifiers added.
<?xml version='1.0' encoding='UTF-8'?>
<rst stat='ok' version='1.0'>
<result stat='ok' />
<activities>
<activity id=’1234’ />
<activity id=’1235’ />
</activities>
</rst>
</xml>
The ‘id’ attribute will contain the added activity record identifier. This value can be ignored on updates but must be stored when adding items in order to perform updates or deletions at a later date.
Sample Failure XML Payload:
<?xml version='1.0' encoding='UTF-8'?>
<rst stat='ok' version='1.0'>
<result stat='fail' msg='see reason nodes'>
<reason>Scheduled items cannot be altered.</reason>
</result>
</rst>
</xml>
Sample Parameter Lists:
Sample Multiple Events Request:
Add: attendeeID=10930&eventIDs=10000,1001,1002