TickerDocs
Tools

get_event_analytics

Shows every number for one event as it reads now, its sale windows, or with `range` how its numbers read on past dates.

When to use it

  • You have one event and want all of its numbers, a few named ones, or when it goes on sale. For its completed sales, the seats taken and each market's sales and interest, set view to sales.
  • You want the performer's other dates in the same city: set view to same_city, and add played true for the dates that already took place.
  • You want what a number read on an earlier date, like the median price 30 days before the show: pass range.
  • You want to compare or rank many events: use screen_events. You want the reason a number moved: use research_event. It replaces get_event_analytics_history and get_event_sale_windows, whose names still answer: see Old names.

Inputs

  • event_id (string, required): The event, by its Ticker id (ev plus ten characters), as search_events and the other tools return it.
  • columns (array of strings): The columns to return, spelled as list_screen_columns gives them in the ea group, without the ea. prefix. Now: leave it out for every column; presales and onsale name the sale windows. With range: leave it out for a headline set (listings, the median and lowest price, before fees and all-in, the share of tickets left and the main signal columns).
  • range (string): Read the history instead of the numbers now: one row per past date, as far back as this reaches. all reaches back up to one year. One of 7d, 14d, 28d, 90d, all.
  • view (string): sales: the event's completed sales, the seats taken, and each market's sales and interest. It takes no range: the newest sales come first. same_city: the performer's other upcoming dates in this event's city and state, the ones Ticker found most recently first, at most 20. One of sales, same_city.
  • limit (integer): With sales, the most completed sales to return: 20 when you leave it out, at most 50. From 1 to 50.
  • section (string): With sales, only the sales whose section contains this text, in any case, like 104. Up to 64 characters.
  • row (string): With sales, only the sales in this row, exact, in any case. Up to 16 characters.
  • by_section_days (string): With sales, also return sections_by_day: the completed resale sales of each section, one count per date (UTC) over 7, 14 or 28 dates, today last. Where your plan reads sh, also its best selling sections by date. One of 7, 14, 28.
  • played (boolean): With same_city, true returns the performer's dates in this city that already took place, the most recent first, at most 20. Max plan and above.
  • currency (string): usd or venue. For an event at a Canadian or UK venue, venue gives every price in the venue's currency (Canadian dollars or pounds) at one exchange rate for the event, so the cheapest market and any order stay the same, and the answer names currency, venue_currency, fx_rate and fx_rate_date. Leave it out for USD. Any other event is always in USD. One of usd, venue.

Examples

Give me everything Ticker has on this event, and when it goes on sale.

{ "event_id": "ev3rp4z4zhq1" }

What is the median price for this show now, and how far did it move this week?

{
  "event_id": "ev8k2m4q7x1a",
  "columns": [
    "median_price_current",
    "median_price_pct_7d",
    "tickets_current",
    "tickets_delta_7d"
  ]
}

Has this act played this city before?

{ "event_id": "ev3rp4z4zhq1", "view": "same_city", "played": true }

What comes back

  • Now: one object with the event's columns, plus event_id, event_url and event_name. days_to_event counts the days to the event and goes below zero after it. partial_row true means some numbers are missing: read a null there as unknown, not as zero.
  • presales, each named presale window with name, start and end, and onsale, the public window. An empty presales is the normal answer: most events state none. They come on a full read, or when columns names them.
  • prediction_markets when a market covers the event, each with a yes-probability from 0 to 1, information and not advice. primary_sources lists the primary-market sources with data for the event. A columns pick never removes either.
  • With range: one row per date, oldest first, with as_of_date, days_to_event, partial_row and the columns. days_missing lists dates with no row: never fill one in. plan_capped true when your plan cut the history, with withheld naming the plan that reads further back.
  • An event with no numbers yet answers available false and a one-line reason; null means no such event. A column your plan does not include is left out and named in withheld.

Limits and quota

  • Reads only: it changes nothing.
  • Each call spends one MCP request.
  • The Max plan and above include the columns that read the tm, tmr, gt, mlb, sg and sh sources. The Pro plan and above include the weather and roof columns.
  • With range, the Free plan reaches back 30 days, and the Pro plan and above read the full history. A column your plan does not include is refused there with a plan_required error.
  • The Max plan and above include events that have already taken place.
  • played is on the Max plan and above.

On this page