SeatGeek

Array of SeatGeek event IDs to display. Use eventSearch to find event IDs first. The events will be displayed in the order provided.

The type of user intent. "discovery" = open-ended exploration, recommendations, or comparing options (e.g. "what's happening this weekend", "best concerts near me", "cheapest NBA games"). "specific_search" = looking for a known event, performer, or team (e.g. "Yankees games"). "purchase" = ready to buy tickets (e.g. "get me 2 tickets to..."). "price_check" = checking prices or availability without strong buy intent. "gift" = buying for someone else. "market_comparison" = comparing prices or options across ticket marketplaces (e.g. "are these tickets cheaper on SeatGeek?").

Short descriptor for the carousel header, such as "Events in New York" or "Upcoming Yankees events" or "Events this weekend"

The user's original message exactly as they typed it.

SeatGeek event ID to display listings for. Use eventSearch to find event IDs.

The type of user intent. "discovery" = open-ended exploration, recommendations, or comparing options (e.g. "what's happening this weekend", "best concerts near me", "cheapest NBA games"). "specific_search" = looking for a known event, performer, or team (e.g. "Yankees games"). "purchase" = ready to buy tickets (e.g. "get me 2 tickets to..."). "price_check" = checking prices or availability without strong buy intent. "gift" = buying for someone else. "market_comparison" = comparing prices or options across ticket marketplaces (e.g. "are these tickets cheaper on SeatGeek?").

Maximum price per ticket including fees (e.g., 200 for tickets under $200). Keep blank unless the user specifies a budget.

Sort order for listings. "top-picks" (default) = best overall value, balancing seat quality and price — good for general browsing. "price-low" = cheapest tickets first — use when the user wants the lowest price or cheapest option. "price-high" = most expensive tickets first. "best-seat" = highest seat quality first regardless of price — use when the user wants the best seats, closest to the stage/field/court, or premium experience. "deal-score" = best deals first, where the price is lowest relative to the seat quality — use when the user wants the best bang for their buck.

Number of tickets needed (e.g., 2, 4).

The user's original message exactly as they typed it.

Filter concerts by music genre. Only applies when searching for concerts — ignore this field for sports, theater, comedy, or any non-concert taxonomy. Only use when the user is explicitly looking for a specific genre (e.g. "country concerts", "rock shows"). If they are looking for a specific performer, use the performerQuery field instead.

Search for events that start on or before this datetime. Format as ISO 8601, represented in unqualified local time without a timezone offset. Example: 2026-01-13T23:59:59

Search for events that start on or after this datetime. Format as ISO 8601, represented in unqualified local time without a timezone offset. Example: 2026-01-13T00:00:00

The type of user intent. "discovery" = open-ended exploration, recommendations, or comparing options (e.g. "what's happening this weekend", "best concerts near me", "cheapest NBA games"). "specific_search" = looking for a known event, performer, or team (e.g. "Yankees games"). "purchase" = ready to buy tickets (e.g. "get me 2 tickets to..."). "price_check" = checking prices or availability without strong buy intent. "gift" = buying for someone else. "market_comparison" = comparing prices or options across ticket marketplaces (e.g. "are these tickets cheaper on SeatGeek?").

latitude,longitude coordinates for a specific named location (e.g. 'events in Chicago'). Only provide this when useGeolocation is false. Ignored when useGeolocation is true.

Maximum ticket price in dollars. Filters events where the lowest available ticket price is at most this amount. Only set when the user specifies a price ceiling (e.g. "events under $100", "cheap events under $30").

Minimum ticket price in dollars. Filters events where the lowest available ticket price is at least this amount. Only set when the user specifies a price floor (e.g. "events over $50").

Page number for paginated results (default: 1). Use when the user wants to see more results beyond the first page.

Filter events to a particular performer (teams, bands, artists, musicians, comedians, etc.). Only set this when the user asks for events by a specific performer. To search for events featuring multiple performers (AND match), separate performer names with a comma — e.g. "New York Yankees,New York Mets". Only use comma-separated performers when the user explicitly asks for events that feature ALL of those performers together (e.g. matchups, co-headliners). Do not use commas for separate searches.

How the first performer should be matched. "home_team" = only home games for that team. "away_team" = only away games. "primary" = performer is the primary/headliner. "any" = default, matches the performer in any role. Only use when the user explicitly asks for home or away games (e.g. "Yankees home games", "Celtics away schedule"). If multiple performers are provided, this only applies to the first one.

Number of events per page (default: 15). Only change this if you know you need more or fewer results — e.g. set to 10 for a quick glance, or 50+ when scanning a full season schedule.

Filter sports events by season phase. "preseason" = preseason games only. "inseason" = regular season only (excludes pre/postseason). "postseason" = playoff/postseason games only. "nonpreseason" = regular season + postseason (excludes preseason). Only use when the user specifically asks about a season phase (e.g. "playoff games", "regular season schedule").

Sort order for results. "popularity" (default) = most relevant/popular events first. "date" = chronological order. Price sorts order events by ticket price (e.g. "lowest_price.asc" = cheapest events first). "distance.asc"/"distance.desc" = sort by proximity to the user — only works when useGeolocation is true or locationCoordinates is provided. Only change from the default when the user explicitly asks for a specific ordering.

Filter events by category. Only set this when the user explicitly asks for a category of events (e.g. "concerts", "NFL games"). Do not set this when the user asks for a specific performer — use performerQuery instead. Taxonomies have different levles of specificity. For example, baseball includes mlb, ncaa_baseball, etc. sports includes every type of sport. Use the most specific taxonomy the user is asking for.

When true, we will only return events near the user. Only set this to true when the user asks for events near them. For all other location-based requests, set this to false and use locationCoordinates.

The user's original message exactly as they typed it.

Filter events to a particular venue (stadiums, arenas, theaters, etc.). Only set this when the user explicitly asks for events at a specific venue. Do not set this alongside performerQuery unless the user specifically asks for a performer at a particular venue.