Public events that include a venue, an organizer profile, and which include tickets that are currently available for sale, will automatically be added to our search index, and will be available via our event_search method.
Accessing public event information does not require additional user-authentication tokens.
Selling tickets is easy with Eventbrite. Provide a link to an event page to initiate our order workflow.
When a repeating event is returned, here is how to interpret the data:
- The first word in the string refers to when the event repeats: daily, weekly, or monthly.
- The first number in the string references the frequency of the event repeating.
- The “N,N,N,N,N,N,N” comma separated string represents the days of the week on which the event is occurring, starting from Monday. This would translate to: “Mon,Tues,Wed,Thurs,Fri,Sat,Sun.”
- The last section of the string refers to the last instance of the event.
<?xml version="1.0" encoding="utf-8" ?> <event> <id>4676119399</id> <repeat_schedule>weekly-1-Y,N,N,N,N,N,N-06/03/2013</repeat_schedule> <repeats>yes</repeats> <start_date>2013-07-01</start_date> </event>
This event repeats every one week on Monday, beginning on 6/1/13 and ending on 7/1/13.
repeats every one week on Friday, until 6/13/15
repeats every other week on Tuesday and Thursday, until 6/13/15
repeats every 1 month on the last Monday of the month, until 6/20/14
repeats every 1 month on 15th of the month, until 6/30/13
completely custom schedule. At this time, it’s not possible to pull these dates using the API, but these dates are available on the event page itself.
|id||The event ID. This should be stored as a numeric string or a long int.|
|title||The event title. (string)|
|description||The event description. (text/html)|
|category||The event category.|
|tags||The event tags/keywords. For SEO optimization, public events only.|
|start_date||The event start date and time, in ISO 8601 format (e.g., “2007-12-31 23:59:59″).|
|end_date||The event end date and time, in ISO 8601 format (e.g., “2007-12-31 23:59:59″).|
|timezone||The event timezone, usually returned as a GMT offset. The following information may be useful for converting the API response value to it’s Olson timezone equivalent.|
|created||The date and time the event was created, in ISO 8601 format (e.g., “2007-12-31 23:59:59″).|
|modified||The date and time the event was last modified, in ISO 8601 format (e.g., “2007-12-31 23:59:59″).|
|privacy||Private for a private event, Public for a public event.|
|password||Private event pages are only visible to those who know the related password.|
|capacity||The total event capacity. This attribute is used to limit sales based on a site’s maximum occupancy, the number of total seats available, or based on fire-safety regulation limitations. This count may be lower than the sum of all available tickets. When the event capacity is set to ’0′ (default), then sales will only be limited based on the per-ticket-type settings.|
|num_attendee_rows||The number of attendees that have registered for the event. Capacity minus num_attendee_rows equals the number of remaining available spaces at the selected event, except in cases where capacity is set to zero.|
|url||The event registration URL.|
|logo||The event logo URL. This field can only be set through our web interface.|
|logo_ssl||The event logo URL to use for SSL-encrypted connections.|
|status||The event status (“draft”, “live”, “started”, “ended”, or “canceled”).|
|background_color||Custom hexadecimal color for your registration page. Format: FFFFFF without the pound|
|text_color||Custom hexadecimal colors for your registration page.|
|link_color||Custom hexadecimal colors for your registration page.|
|title_text_color||Custom hexadecimal colors for your registration page.|
|box_background_color||Custom hexadecimal colors for your registration page.|
|box_text_color||Custom hexadecimal colors for your registration page.|
|box_border_color||Custom hexadecimal colors for your registration page.|
|box_header_background_color||Custom hexadecimal colors for your registration page.|
|box_header_text_color||Custom hexadecimal colors for your registration page.|
|venue||The event venue. For more information on the structure of this object, see our venues page.|
|organizer||The event’s “organizer profile” page. For more information about organizer profile pages, and their object structure, see our organizer profiles page.|
|tickets||The tickets entity will contain an array of the ticket types associated with this event. For more information on the structure of these objects, see our tickets page.|