The same data fields are returned for each successful API request (Search and Geo). The following is a breakdown of the data fields that are returned for each successful Events API request:

This is an example of an XML response:
<Event_Title>Book launch and signing at Carlow Library</Event_Title>
<Event_Description>Full details HTML goes here, including links back to website, etc. Use as much HTML code as you like here.</Event_Description>
<Issued_By>Carlow Local Authorities</Issued_By>

The following outlines each response field:

File Name type Description
Event_ID int Unique ID for each event that is published on the website.
Event_GUID text This is a global UID. Useful if you are using this data to create feeds
Event_Day text Two-Digit day of the Month (Range: 01-31)
Event_Month text Two-Digit month of the year (Range: 01-12)
Event_Year text Four-Digit Year (eg, 2013, 2014, etc)
Event_Hour text Start Date of the Event as a 24-Hour 2-digit value (Range: 00-23)
Event_Minute float Start Minute of the event as a 2-digit value (Range: 00-59)
Event_Title text The event title, max length is 100 characters.
Event_Description text The event description where HTML code is parsed cleanly
Venue_Name text The venue name
Venue_Lat float The Venue latitude value (eg 53.12345)
Venue_Lng float The Venue longitude value (eg -7.12345)
Issued_By text The local authority who issued this event. Useful for filtering events from certain Councils.
Venue_Distance float This is only delivered as part of the eventgeo API result and refers to the direct distance between the search coordinates (lat & lng) with the venue location in metres (eg, 1000)