SeatGeek Integration

Localist is able to connect with the SeatGeek API to automatically import event data to your organization’s platform. These feeds are set up on a per-platform basis (arranged during license agreements) andLocalist’s communication with SeatGeek is only SeatGeek -> Localist.

Platform Admin

SeatGeek Import Data

The SeatGeekAPI provides the following fields that match fields in Localist. If a Localist field is not listed, it is because a matching field is not provided by the SeatGeek API.

  • External ID
  • Name
  • Category (Event Type)
  • Date From
  • Start Time
  • Location
  • Address
  • City,State &Zip
  • Latitude & Longitude
  • Ticket URL
  • Photo URL
  • Event URL
  • Cost

SeatGeek Event Types

All SeatGeek events are categorized with a set list of filters. In order for the events to be properly filtered on your platform your filter lists must include at least the top 3 level filters: Sports, Theatre and Music. If you’d like to expand your filter list to include more specific filters you may add filters from the following list – they must match exactly as they follow (nesting is not taken into consideration when matching, for example the filter can be a child or a parent):

  • Sports
  • Baseball
  • MLB
  • NCAA Baseball
  • Minor League Baseball
  • Football
  • NFL
  • NCAA Football
  • Basketball
  • NBA
  • NCAA Basketball
  • NCAA Womens Basketball
  • WNBA
  • NBA DLeague
  • Hockey
  • NHL
  • NCAA Hockey
  • Minor League
  • Soccer
  • MLS
  • NCAA Soccer
  • European Soccer
  • International Soccer
  • World Cup
  • Auto Racing
  • Nascar
  • Nascar Sprintcup
  • Nascar Nationwide
  • Indycar
  • F1
  • Monster Truck
  • Motorcross
  • Golf
  • PGA
  • LPGA
  • Fighting
  • Boxing
  • MMA
  • Wrestling
  • WWE
  • Tennis
  • Animal Sports
  • Horse Racing
  • Rodeo
  • Extreme Sports
  • Olympic Sports
  • Concert
  • Music Festival
  • Theatre
  • Classical
  • Classical Opera
  • Classical
  • Classical Orchestral Instrumental
  • Cirque du Soleil
  • Broadway Tickets National
  • Comedy
  • Family
  • Dance Performance Tour
  • Film
  • Literary

Importing Places from SeatGeek

To add place profiles that match the events in SeatGeek you can use their API. This needs to be done before adding the event feed to ensure that the events connect to the place profile.

  • Build a SeatGeek API call according to city or zip code

    SeatGeek’s API defaults to providing 10 results at a time. To increase this add &per_page=200 (or more) to the end of your call.

  • In another tab, openhttp://konklone.io/json/

    Copy all results to the first box on konklone

  • Once entered, the data will be converted into a table format below
  • Select Download the entire CSV

    Remove all columns except C (name), G (state), I (postal_code) and L (address)
    Rename postal_code to Zip

  • Export your spreadsheet as a CSV
  • To upload, navigate via Places > +Bulk Add Places in your admin dashboard

Importing a SeatGeek Feed

Unlike other feeds, such as ICS or RSS, aSeatGeek feed will need to be set up by Localist Support.SeatGeek feeds are filtered by zip code. By default, all events that are within a 50 mile radius of the given zip code will be included in the feed, but this can be modified on a per-feed basis. For example, a Baltimore City zip code may include events in the Washington DC area.To see an example of what kinds of events and the amount you can expect to see imported into your calendar, visit seatgeek.com and enter your zip code in the search field.

To set up, contact support at support@localist.com with the following details:

  • Zip code(s) you will be pulling from
  • Pending Queue confirmation:
    • Option 1: Send all events to the pending queue where they will be individually approved before being posted live on the calendar.
    • Option 2: Have all events skip the pending queue and be posted live on the calendar upon import without any admin approval.

HEADS UP: Upon saving, the feed will initially import once. After the initial import, the feed will import once a day and overnight. Any changes will not be reflected in Localist until after each nightly import.

Important Feed Import Details

Feed Data Takes Precedent

1. Data imported by a feed into Localist will always take precedent over data that has been added or updated in the Localist event. Only the following 3 details can be locked and cut off from further updating:

  • Name
  • Description
  • Event Place

2. All other details that are brought in via a feed must be changed at the feed source. If it is changed in any way in Localist then the changes will only stick until the next feed import, at which time it will revert back to the data in the feed.

  • Exception: If a piece of data is not provided by the feed then any changes or additions in Localist will stick even after the next import. For example, if the feed only provides name/date/time/description/place then anything else, such as a tag or custom field, will remain as updated in Localist.

3. If fields in a feed match fields in Localist then the data must match exactly to what is saved in Localist. It is not possible to assign aliases or alternative spellings. For example, place names must match the place landing pages and filters must match the taxonomy on your platform in order to connect properly.

Deleting a Feed Event

1. Deleted in Localist: If an event has been imported to the calendar then deleted, it will reappear if it is sent back over through the feed. Since feed data takes precedent, if the event is present in the feed then it will be re-added to Localist.

  • Exception: If an event is rejected from the pending queue then it will not re-appear. If the event is deleted while still in the pending queue then it will be re-imported into the queue.

2. Deleted at the feed source: If an event is removed from the feed source, the event in Localist will not be removed. This is because it is impossible for Localist to determine wether the event has been deleted/cancelled or if the event is just not present in the feed. In this case you will need to delete the instance in the feed and in Localist.