Performing Event Searches with the SeatGeek API in JavaScript/

...

/

Events

Events

Learn how to search for live events using the SeatGeek API.

We'll cover the following...

Event endpoints are one of the most critical endpoints for the SeatGeek API. They allow us to request any event with tickets available for purchase on the SeatGeek platform. The endpoints for events are as follows:

  • The events endpoint: Fetches a paginated list of events using certain search parameters.
  • The specific event endpoint: Fetches details about a specific event by providing an event ID as a path parameter.

The events endpoint

To fetch a list of all events, we use the following endpoint URL:

https://api.seatgeek.com/2/events

Request parameters

We can use the following query parameters with the URL given above when fetching a list of events:

Name

Category

Syntax

Description

ID

optional

id

This parameter fetches specific events using unique event IDs. We can use the id parameter multiple times in the same API call. The default value of this parameter is null.

All other URL parameters are overridden when using this parameter, and the SeatGeek API ignores them even if they’re passed in the HTTP request.

Performers

optional

performers.{FIELD}


performers[{SPECIFICITY}].{FIELD}

This parameter filters the event results according to specific performer parameters.

The performers parameter supports two fields, id and slug, which we can use interchangeably in the same API call.

The performers parameter supports the following values of specificity: home_team, away_team, primary, and any. We use the primary specificity to look up events with a trending performer.

We can use a comma-separated list of performer IDs to filter event results based on specific performers. The default value of performers.{FIELD} is null, and if we use the performer parameter, the default value of performers[{SPECIFICITY}].{FIELD} is any.

Venue

optional

venue.{OPERATOR}

This parameter filters the event results according to specific venue parameters.

The venue parameter supports all the URL parameters we use for the venues endpoint, like venue.city, venue.id, or venue.state. We can use a comma-separated list of venue IDs to filter event results based on specific venues.

Datetime

optional

datetime_utc


datetime_utc.{OPERATOR}


datetime_local


datetime_local.{OPERATOR}

This parameter filters the event results according to a specific date and time range. We can use the datetime parameter two times at most in the same API call. The datetime parameter has two types, datetime_utc and datetime_local, which have the same functionality. The only distinction is that one is for UTC, and the other is for local time zones.

This parameter accepts the ISO 8601 time string format (YYYY-MM-DDTHH:MM:SS) and YYYY-MM-DD. The datetime parameter supports the following operators: gt, gte, lt, and lte. The default value for this parameter is null.

Query

optional

q

This parameter performs a broad search for events by looking up all possible sections of the response document. Since this parameter is a broad search, the search results can be unexpected. The default value for this parameter is null.

Taxonomies

optional

taxononmies.{FIELD}

This parameter filters the event results according to specific event types by using taxonomies. The taxonomy parameter supports all the URL parameters we use for the taxonomies endpoint. The taxonomies parameter supports the following values of the field: name, id, and parent_id. The default value for this parameter is null.

...