Attendee records that are collected as part of the event registration process can be accessed through automated feeds. These feeds can be used to extract registration records for use in other systems.
Note This topic assumes that you are familiar with the http protocol and how URL parameters work.
The registration feed is accessed by issuing an http request in the following format.
The filename of the http request must include the calendar webname. This is a unique ID assigned to the calendar in the Trumba calendar settings. For more information about a calendar's Web name, see Find a calendar's web name.
The following table lists the parameters you can use to retrieve specific registration information. All parameters are optional.
| Parameter | How to use it |
|---|---|
| startdate |
Limits records to events that start on or after a specified date or on or after the day specified by one of the following strings: today, yesterday, or tomorrow.
For example, to generate a feed with only future and no past events, use this URL:
|
| enddate | Limits records to events that end on or before a specified date or on or before the day specified by one of the following strings: today, yesterday, or tomorrow.
For example, to generate a feed with only past and no future events, use this URL:
|
| Limits records to the the specified attendee email address. | |
| eventid | Limits records to the specific event ID. If eventid is specified, the startdate and enddate parameters are ignored. |
| changedate | Limits records to registrations that were added or updated after the specified date and time. If not specified then all registraiton records for the events are included. Date/time format is yyyymmddThhmm, for example 20161205T1615 for 5 Dec. 2016, 4:15pm. The time is considered in UTC and hours should be specified in 24 hour time. |
You must specify a Trumba account username and password through HTTP BASIC authentication in order to access the feed. The request should be made using a secure "HTTPS" request to ensure that authentication credentials are secure. The specified account must either own the calendar or have been granted "Can add, delete and change content" access to the calendar.
The output of the feed is returned in CSV (comma separated value) format and includes the following fields.
| Field | Description |
|---|---|
| Event ID | The unique ID of the event. |
| Event Description | The title of the event. |
| Event Date/Time | The start date and time of the event in the calendar timezone. Format is mm/dd/yyyy hh:mm AM/PM. |
| [Custom Fields] | One or more custom fields that you set to show in registration reports and feeds. The number and names of fields will vary. |
| Attendee Name | The name of the attendee. |
| Attendee Email | The email address of the attendee. |
| Response | The response provided by the attendee. Values may include Registered, Wait List, Decline and Tentative. |
| No. | The number of attendees signed up under this email address including guests. |
| Amount | The amount paid by the attendee when signing up. This field is included only for paid events where the payment was processed through Trumba. |
| Price Label | The label assigned to each pricing option (relevant only when the event organizer set up multiple pricing options). This field is included only for paid events where the payment was processed through Trumba. |
| Response Date | The date/time of the attendee's response. |
| Last Modified Date | The date/time that this attendee record was last modified. |
| Reg Form | The name of the registration form used to collect information from the attendee. |
| Comments | Comments supplied by the attendee through the Standard registration form. |
| [Custom Questions] | Multiple fields specifying answers to custom questions. The number and names of fields will vary depending on which custom registration forms were used. |
