Ticket price tracking API

Build price history, drop alerts and “best time to buy” features. Capture an event on a schedule and store what you need from each result: the cheapest ticket, the median price, how many tickets are left, and the cheapest price for buying 2 or 4 together.

Ticket prices move every hour, and each marketplace shows them differently: some include fees, some don’t, some list per ticket and some per group. Tracking them yourself means maintaining a separate integration per marketplace.

With one capture call per event you get the same summary fields from every marketplace, with each price’s basis stated, so a time series built today still compares correctly next month.

How it works

1. Find the events to watch: Search by team, artist or venue. Leave out dates to get every upcoming date, then keep the event IDs you want to track.

2. Capture on a schedule: Run a capture per event as often as your plan allows — hourly near the event date, daily further out. Each completed capture uses one request; failed ones are free.

3. Alert or chart: Compare each new point with the last one: notify users when the cheapest price drops below their target, or chart the median to show where prices are heading.

Questions

How often can I track an event?

As often as your plan’s hourly and monthly requests allow. Each completed capture uses one request, so 500 requests a month covers about 16 events once a day.

Which price should I store?

summary.minPrice for the cheapest ticket and summary.medianPrice for the typical price. Check coverage.priceBasis so you know whether prices include fees on that marketplace.

Do you keep price history for me?

No. Each capture returns the market as it is now; you store the points you care about. That keeps your history in your own database and format.