TickerDocs
Tools

search_events

Finds events by name, performer, venue or date, and gives their Ticker event ids.

When to use it

  • You know an event by its name, performer, venue or date, and you need its event_id for another tool.
  • You want events by a plain fact: a date range, an on-sale or presale window, a venue, a performer, or when Ticker added them.
  • You want events in a place: a city, a state or province, or a country.
  • To rank or filter events by price, demand or inventory, use screen_events. Words like hottest, top or movers are a sort there, not search text. Rows from screen_events, list_matches and the analytics tools already carry event_id and event_url. Do not search again to get a link for them.

Inputs

  • search (string): Names to look for: an event, a performer or a venue, like taylor swift or Red Sox Yankees. The words can come in any order. Each word of three or more letters must be in the event's name, its performer or its venue, and short joining words like vs and the are ignored. Events whose name holds every word come first. Use a venue's official name, not a nickname. Leave it out to browse by the other inputs alone.
  • query (string): The same as search. Use search; when you send both, this one is ignored.
  • status (string, default active): Only events in this state. active keeps the events Ticker tracks now. When a search with a status finds nothing, it runs again over every status, and the result says so. One of active, inactive, cancelled.
  • venue_id (string): Only events at this venue, as a Ticker venue id from get_venue_schedule with view venues.
  • performer_id (string or integer): Only events this performer headlines, as a Ticker performer id.
  • monitoring_priority (integer): Only events at this exact coverage level: 1 is the closest coverage, 10 the lightest. From 1 to 10.
  • monitoring_priority_min (integer): Only events at this coverage level or lighter: 1 is the closest coverage, 10 the lightest. From 1 to 10.
  • monitoring_priority_max (integer): Only events at this coverage level or closer. From 1 to 10.
  • category_id (integer): Only events in this category, by its Ticker id.
  • capacity_min (integer): Only venues with at least this many seats.
  • capacity_max (integer): Only venues with at most this many seats.
  • primary_sold_min (number): Only events with at least this percent of the primary house taken, 0 to 100.
  • primary_sold_max (number): Only events with at most this percent of the primary house taken, 0 to 100.
  • primary_left_min (integer): Only events with at least this many primary tickets still on sale.
  • primary_left_max (integer): Only events with at most this many primary tickets still on sale.
  • tmr_get_in_min (number): Only events whose lowest all-in price on the primary market's own resale is at least this many dollars.
  • tmr_get_in_max (number): Only events whose lowest all-in price on the primary market's own resale is at most this many dollars.
  • resale_to_primary_min (number): Only events whose resale vs face value, all-in, is at least this ratio. 1 means resale is priced at face value.
  • resale_to_primary_max (number): Only events whose resale vs face value, all-in, is at most this ratio.
  • sold_1d_min (integer): Only events with at least this many completed sales in the last day.
  • sold_3d_min (integer): Only events with at least this many completed sales in the last 3 days.
  • sold_7d_min (integer): Only events with at least this many completed sales in the last 7 days.
  • city (string or array of strings): Only events in this city, any case, like Las Vegas. Send up to 20 to match any of them: a metro area spans several city names (New York, Brooklyn, Flushing, Newark), so list each. Up to 100 characters.
  • state (string or array of strings): Only events in this state or province, by its code, like NV or ON. Send up to 20 to match any of them. US and Canada only; filter other countries by country. Up to 100 characters.
  • country (string or array of strings): Only events in this country, by its two-letter code, like US, GB or NL. Send up to 20 to match any of them.
  • date_from (date-time): Only events on or after this time. ISO 8601, with or without a time zone offset, like 2026-11-01T00:00:00-05:00.
  • date_to (date-time): Only events on or before this time.
  • onsale_from (date-time): Only events whose public on-sale starts on or after this time. Events with no known on-sale date are left out.
  • onsale_to (date-time): Only events whose public on-sale starts on or before this time. Events with no known on-sale date are left out.
  • presale_scope (string): Which presale presale_from and presale_to match: first (the default), the first presale, or any, any named presale. One of first, any.
  • presale_from (date-time): Only events whose first presale starts on or after this time. Events with no known presale date are left out.
  • presale_to (date-time): Only events whose first presale starts on or before this time. Events with no known presale date are left out.
  • created_from (date-time): Only events Ticker added on or after this time. Use it to find new dates.
  • created_to (date-time): Only events Ticker added on or before this time.
  • include_past (boolean, default false): Also include events whose date has passed. Without date_from, past events go back 90 days.
  • sort_by (string): The order of the rows. Sorting by onsale_date or presale1_date keeps only the events that have that date. One of local_date, utc_date, event_name, status, monitoring_priority, onsale_date, presale1_date, created_at, sold_24h.
  • sort_order (string): asc puts the soonest first, desc the latest first. One of asc, desc.
  • page (integer, default 1): The page of results.
  • limit (integer, default 25): Rows per page, at most 100. A larger number reads as 100. A long page can come back cut short; see below.
  • parking (string, default hide): Parking passes sold as their own event: hide (the default) leaves them out, only returns parking alone, include returns parking beside every other event. Under hide, a search for parking by name still finds it. One of hide, include, only.

Examples

When does Zach Bryan play Madison Square Garden?

{ "search": "Zach Bryan Madison Square Garden" }

Which events go on public sale next week, in the order they open?

{
  "onsale_from": "2026-10-19T00:00:00-04:00",
  "onsale_to": "2026-10-25T23:59:59-04:00",
  "status": "active",
  "sort_by": "onsale_date",
  "limit": 50
}

What is on in Las Vegas next weekend?

{
  "city": "Las Vegas",
  "date_from": "2026-11-27T00:00:00-08:00",
  "date_to": "2026-11-29T23:59:59-08:00"
}

What comes back

  • One row per event, with event_id, event_url, event_name, local_date, utc_date, status, onsale_date, presale1_date and performer_id. Pass event_id to any other tool.
  • A short venue on each row: venue_id, venue_name, city and state.
  • currently_priced on each row: false means the event exists in Ticker but has no current prices.
  • retried_including_inactive is true when the search with a status found nothing and ran again over every status.
  • total and totalPages, an estimate of how many events match.
  • A page too large for one answer comes back as its first rows with meta.truncated. Narrow the search or the dates; do not repeat the same call.

Limits and quota

  • Reads only: it changes nothing.
  • Each call spends one MCP request.
  • Carries no prices or market numbers. Use screen_events or get_event_analytics for those.
  • Upcoming events only, unless you set include_past.
  • Parking passes and other non-admission items are left out, unless your search is about parking.

On this page