TickerDocs
Tools

get_event_sections

Shows one event's market by section: prices and tickets over time, the listings on sale, levels, one series across sections, or a map.

When to use it

  • You want to know which part of the house is rising or falling in price, or to read resale vs face value section by section, as price context. For one market alone under its own section names, set source to that market.
  • You want the listings on sale, cheapest first or section by section, with view listings; or one price line across a few sections together, like a whole level, with view aggregate. Across a performer's run or a list of events, view find names the shows with listings in a section or on a level, for a ticket count and price, in one call.
  • You want how the house is laid out: each section's level, the sections close to it and the one opposite, with view levels; or a picture of the house, each section colored by its lowest price or its tickets, with view map.
  • You want seats open this minute: use get_event_sections_live. For a past moment or one section over hours, use it with view at or series.

Inputs

  • view (string): prices (the default): the prices and tickets of each section. listings: the listings on sale, one per row. aggregate: one series across the sections in sections. levels: each section's level, the sections close to it and the section opposite. find: across a performer's upcoming events or a list of events, the events with listings in a section or on a level, with the cheapest and median price per section and market, and no_match saying why an event has none. It takes performer_id or event_ids, not event_id. map: the event's section map as a picture, each section colored by one market's lowest price or its tickets on sale (color_by), and each drawn section's number in the data beside the picture. One of prices, levels, listings, aggregate, find, map.
  • event_id (string): The event, by its Ticker id. Find it with search_events.
  • source (string): all (the default): vs, tm_primary and tm_resale side by side, one row per section. A market code reads that one market alone, under its own section names. vs, tmr, sh, sg and aq are the resale market; tm, sgp and mlb (the team's own primary market for a baseball game) are the primary market. mlb answers current prices only, with no history. With listings, all reads every listing market your plan includes, and vs, sh, sg, tmr or sgp reads one. With aggregate, one of vs (the default), sh, sg, tmr or sgp. With map, the market whose sections color the map: vs (the default), tmr, sh, sg, sgp, tm or aq. It does not apply to levels. One of all, vs, tmr, sh, sg, sgp, tm, mlb, aq.
  • sections (array of strings): With prices and listings, only these sections, by any market's own label, like 108 or FL2, or by section_key, like FLOOR-10. Leave it out for the whole house. With aggregate, the sections to combine, required.
  • limit (integer): The most rows to return. With prices, the sections when you leave out sections: 40 by default, and a value above 200 reads as 200. With levels: 200 by default, and a value above 1000 reads as 1000. Sections come in the order the app lists them: numbered sections by number, then named areas like the floor. With listings: 50 listings by default, and a value above 100 reads as 100.
  • include_history (boolean): With prices, set false for current prices only, without history.
  • range (string): How far back to read: 3d, 7d (the default), 30d, 90d or all, counted back from today. With prices, the reach of each section's history; with aggregate, the span of the series. One of 3d, 7d, 30d, 90d, all.
  • granularity (string): With prices, the history's detail: daily (the default), one point per date, that date's last reading, or intraday, every reading the history holds, as the app charts it. One of daily, intraday.
  • exclude (string): Comma separated listings to leave out: zone (Unassigned seats, where the seller holds no specific seats yet; vs) and view (Limited view, where the market says the seats see the stage or field only in part; vs, sg, sgp and sh). Leave it out to count every listing. excluded in the answer names what was left out, and a price with nothing left is null. Up to 64 characters.
  • order (string): With listings: price (the default) reads the cheapest first, by the price after fees and then before; section walks the listings market by market, then by section, row and price. One of section, price, deal_score.
  • cursor (string): With listings, next_cursor from the page before, with the same source, order and sections, for the next page. Up to 400 characters.
  • all_in_price_min_usd (number): With listings, only listings at or above this all-in price per ticket, in dollars. From 0 to 90071992547409.9.
  • all_in_price_max_usd (number): With listings, only listings at or under this all-in price per ticket, in dollars. From 0 to 90071992547409.9.
  • quantity (integer or array of integers): With listings, only listings that can sell this many tickets together, or any one of a list of up to 8 counts, like [2, 4]. A listing's stated splits decide when it has some, and its listed quantity otherwise. From 1 to 65535.
  • row (string): With listings, only this row, matched without case or surrounding spaces. Up to 128 characters.
  • parking (string): Parking passes listed inside the event: hide (the default) leaves them out, include adds them as a parking group on the first page, at most 200, and only lists the passes alone. On a parking event the passes are its listings at any value. One of hide, include, only.
  • performer_id (string or integer): With find, one performer's 50 soonest upcoming events, by its Ticker id (pf plus ten characters). event_ids wins when you send both.
  • event_ids (array of strings): With find, the events to read, at most 50, by Ticker id or a marketplace's. Up to 50 items.
  • level (string): With find, only this level. A number like 100 or 100s is the sections numbered 100 to 199, leaving out suites, boxes, lofts, the floor and pits. A word like lower or mezzanine is a level whose name holds it. An event with no such level comes back in no_match with the levels it has. Up to 40 characters.
  • min_quantity (integer): With find, at least this many tickets together in one listing. The default is 1. From 1 to 100.
  • max_price (number): With find, at or under this price per ticket, in dollars, on price_basis.
  • price_basis (string): With find, all_in (the default) for the price with fees or pre_fee for the price before fees. A listing with no price on that basis does not match, and unpriced_on_basis counts it. One of all_in, pre_fee.
  • color_by (string): With map, what colors each section: price (the default), its lowest price, or tickets, the tickets on sale in it (on tm, the seats open). One of price, tickets.
  • render (boolean): With map, include the map image ahead of the data. Set false for the data only, a smaller answer.
  • 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

How did prices in sections 108 and 110 move this week?

{ "event_id": "ev3rp4z4zhq1", "sections": ["108", "110"] }

What are the cheapest listings in section 108 right now?

{
  "event_id": "ev8k2m4q7x1a",
  "view": "listings",
  "sections": ["108"],
  "limit": 20
}

How has the price of the lower level moved this month, sections 101 to 104 together?

{
  "event_id": "ev5n7w2c9d4k",
  "view": "aggregate",
  "sections": ["101", "102", "103", "104"],
  "range": "30d"
}

What comes back

  • prices with source all: one row per section, with section, section_key and tm_section, the primary seller's own label for it, then one block per market: vs for the resale market with the widest section coverage, tm_primary for the primary market's face value and tm_resale for the primary seller's own resale market. section_key names the same section on every market, so the markets line up by it. Each block has the lowest, median and highest price, before fees and all-in, with available_tickets and as_of, and history over range, one point per date unless granularity is intraday. A block is null when the section is not offered in that market. Null never means zero.
  • prices with a market code: source, as_of and one row per section with section and section_key, the lowest, median, highest and average price, before fees and all-in, the face value where the market states one, available_tickets, total_listings and history. sections_total, sections_returned and truncated say whether limit cut the list.
  • listings: one row per listing with its market in source, section and section_key, row, quantity, price before fees and aip_price all-in, face_value, captured_at (when the listing last changed), seen_at (when a read last saw it on sale) and ticker_listing_id, the same on every read. listings_total counts them all; rows_truncated true means more follow, and next_cursor reads them. No seller is named.
  • aggregate: points, one per read, each with the lowest and median price and the middle half of prices (p25_price to p75_price), before fees and all-in, total_tickets and total_listings, over the listings inside the sections asked, never an average of section medians. matched_section_keys names each asked section the event has.
  • map: the map image first unless render is false, cyan for the cheapest sections or the fewest tickets, yellow for the most expensive or the most tickets, and gray for a section with no number on that market. Beside it come price_basis (all_in or price), colored, the count of sections with a number, min_price and max_price or min_tickets and max_tickets, and sections, each drawn section's price or tickets by section_key, cheapest or most tickets first. drawn false means the event has no map to draw, and sections is empty.
  • A market your plan does not include is left out and named in withheld, with the plan that includes it. unavailable names a market whose listings could not be read right now; its absence says nothing about the market.

Limits and quota

  • Reads only: it changes nothing.
  • Each call spends one MCP request.
  • A heavy tool: an account runs two at a time, and a third waits.
  • The resale prices in vs are on every plan. The tm_primary and tm_resale blocks are on the Max plan and above. With source, every market code but vs is on the Max plan and above, and a market your plan does not include is refused with a plan_required error.
  • Markets meet on section_key, never on a label. When one market lists two sections under the same key, each keeps its own row.
  • An input the view does not take, like cursor with prices, is refused by name. A market that does not price by section never appears here.
  • At intraday, or with aggregate, an answer too long for one result keeps the newest points and says so. Name fewer sections, or ask for daily.

On this page