UPFRONT tickets
find_ticket_groupsUPFRONT's own listings for one event that can be bought now, cheapest first. event_id is UPFRONT's event id (eventId in event results); this does not search by name or place.
quantity: the exact number of tickets needed together ("for two people" is 2). When set, only listings that sell that many as ONE group are returned; two separate listings can't be combined into one group. max_price/min_price: the per-ticket price in dollars, fees included. max_total_price: the budget for the whole group, in dollars, as the user stated it ("$200 for two" is 200). Needs quantity; UPFRONT works out the per-ticket limit from it. section: a section name or number ("112", "Floor", "Mezzanine"): only that section's listings. limit: how many listings to return (default 10, at most 25). eticket_only / instant_download_only: only listings with that delivery method. min_days_before_event / max_days_before_event: only listings released within that window before the event ("last-minute").
Returns:
totalListings, lowestAllInPrice, highestAllInPrice: across every listing matching the filters, not only those returned.
listings: the cheapest matches, each with section, row, allInPrice (per ticket, every fee included), totalAllInPrice (the group's price, when quantity is set), quantities (how many can be bought together from this listing), notes, standardSection, deliveryMethods and url.
moreListings: how many matched but weren't returned. Parking-only listings are left out, except on a parking event, where every listing is a parking pass.
notes (what the seller wrote, e.g. "Obstructed view") and standardSection (UPFRONT's name for the section, when matched) are the only view or location signals on a listing; there is no view-quality score. When they say nothing, no view information is available for that listing. Distance, height, cover and a picture of the view come from UPFRONT's section facts, at venues with an UPFRONT seating chart.
url is the link to buy exactly that listing (section, row and quantity) on UPFRONT; it is null only when the listing can't be bought.
{"error": "search_failed"} means the lookup failed after retries, not that no tickets exist. An empty listings list with no error means nothing matched the filters passed; it says nothing about why.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| section | No | ||
| event_id | Yes | ||
| quantity | No | ||
| max_price | No | ||
| min_price | No | ||
| eticket_only | No | ||
| max_total_price | No | ||
| instant_download_only | No | ||
| max_days_before_event | No | ||
| min_days_before_event | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| listings | Yes | ||
| quantity | No | ||
| moreListings | Yes | ||
| totalListings | Yes | ||
| lowestAllInPrice | Yes | ||
| highestAllInPrice | Yes |