TickerDocs
Tools

get_sales

Shows completed sales and primary seats taken, as the Sales tab reads them: a list, a ranking, or per section.

When to use it

  • You want the latest completed sales for an event, a performer, a venue or your Watchlist: leave view out.
  • You want the events or sections that sold the most in the last hour, day or week: view top.
  • You want primary seats taken per section (view primary), or one event's completed sales per section and date (view sections).
  • For one event's sales beside each market's interest per hour, use get_event_analytics with view sales.

Inputs

  • view (string, default list): list (the default): completed sales, newest first. top: the ranking. primary: primary seats taken per section. sections: one event's completed sales per section and date. One of list, top, primary, sections.
  • event_id (string): One event, by its Ticker id (ev plus ten characters). sections needs it.
  • performer_id (string or integer): One performer's events, by its Ticker id (pf plus ten characters).
  • venue_id (string): One venue's events, by its Ticker id (vn plus ten characters).
  • scope (string): watchlist: only the events your account watches, with your team's shared stars and without archived ones. One of watchlist.
  • market (string): With top, secondary (completed resale sales, the default) or primary (primary seats taken). With sections, one market code. Leave it out for every market your plan reads, each its own entry. One of secondary, primary, vs, sh.
  • window (string): With top, how far back: 1h (the default), 6h, 24h or 7d. One of 1h, 6h, 24h, 7d.
  • by (string): With top, rank event (the default) or section. One of event, section.
  • section (string): With list, only sales whose section contains this text, any case. With primary, only sections whose code contains it. Up to 64 characters.
  • row (string): With list, only sales in this row, exact, any case. Up to 16 characters.
  • date_from (string): With list or primary, at or after this day (YYYY-MM-DD, from 00:00 UTC) or instant. Up to 40 characters.
  • date_to (string): With list or primary, before this instant, or through this whole day. Leave both dates out for the last 24 hours, or for every sale when list names an event. Up to 40 characters.
  • days (string): With sections, how many dates (UTC), today last: 7 (the default), 14 or 28. One of 7, 14, 28.
  • page (integer): With list or primary, the page, from 1. From 1 to 10000.
  • limit (integer): With list or primary, rows per page. Leave it out for 50; at most 100.

Examples

What sold for this show in the last day?

{ "event_id": "ev3rp4z4zhq1" }

Which events sold the most this week?

{ "view": "top", "window": "7d" }

Break this event's sales down by section for the last two weeks.

{ "view": "sections", "event_id": "ev3rp4z4zhq1", "days": "14" }

What comes back

  • list: completed sales, newest first, with section, row, price and price_all_in. Each is the listing's last listed state before the sale, and price_basis names that basis beside the rows.
  • top: at most 50 events or sections, with total and truncated.
  • primary: sections ranked by primary seats taken.
  • sections: sections_by_day, one entry per market, never summed.
  • A completed sale is one recorded sale. The Sales numbers screen_events ranks on (ea.sales_*) are a different measure.
  • Fields your plan does not include are named in withheld.

Limits and quota

  • Reads only: it changes nothing.
  • Each call spends one MCP request.
  • The Pro plan opens sales. Below it you get a plan_required error that names the plan, not an empty answer.
  • list and primary need a scope: event_id, performer_id, venue_id or scope watchlist. Only top reads the whole market.
  • An input the chosen view does not take is refused by name.
  • top with market primary across the whole market or a wide scope is a heavy call.

On this page