Included with Enterprise Advanced

The ticket broker API for inventory tracking, sold data, and alerts

A ticket data API for brokers. Pull the tracked primary inventory and ticket resale data that power Flare, from Ticketmaster, AXS, Tickets.com, and StubHub, into your own scripts, spreadsheets, and AI tools. Get real-time seat-level Ticketmaster availability, set alerts from code, and read what fired.

Instant API access after checkout Cancel anytime
Ticketflipping API graphic: REST and JSON endpoints for ticket inventory, sold data, and alerts
Endpoints17
Marketplaces6
Trusted by thousands of brokers since 2015
Data from
Ticketmaster
AXS
Tickets.com
StubHub
TickPick
Vivid Seats
What you get

A ticket data API you read, write, and plug into anything

Ticket resale data and primary inventory come from the same engine behind Flare, the ticket broker software thousands of resellers use. It is exposed as plain JSON so your own tools can read the market, write your alerts, and automate the rest.

Read

Read the market in one call

  • Event analytics: inventory now and 24h, 7d, 30d ago
  • Section-level inventory and pricing
  • Real-time seat-level Ticketmaster availability
  • Sold data from Vivid Seats, listing trends from StubHub
See the data
Write

Write your favorites and alerts from code

  • Favorite events by ID, or by name, date, and venue
  • Drop and low alerts on Ticketmaster and AXS
  • Price and peak alerts on StubHub and TickPick
  • One feed of every alert that fired
See alerts
Integrate

Plug it into anything that speaks HTTPS

  • Plain JSON over HTTPS, no SDK required
  • A Python example on every endpoint
  • Works from Claude Code and OpenAI tools
  • Daily quotas you can check in your account
See integrations
Every endpoint

A ticket data API built around how brokers actually buy

Seventeen endpoints, one token. Read tracked inventory and pricing, pull sold comps, fetch live Ticketmaster availability, and manage favorites and alerts, all in the same JSON format. Daily limits shown are the Enterprise ADV allowances.

Event Analytics & Inventory Tracking

Ticketmaster, AXS, Tickets.com, and StubHub inventory now and 24h, 7d, and 30d ago, plus capacity and min, median, average, and max price, in one call.

10,000 calls/day

Section-Level Inventory & Pricing

Primary and resale counts per section with the lowest primary and all-in price, plus AXS section sold-out status.

Ticketmaster + AXS

TM Live: Real-Time Seat Data

Ticketmaster availability fetched the moment you ask: Ticketmaster's own section and offer data, or seat-level availability merged with prices.

500 weighted calls/day

Vivid Seats Sold Data

Individual sales by zone, section, row, quantity, price, and date, so you price with real numbers, not guesses.

1,000 calls/day

Listing Trends & Inventory History

Daily StubHub listing counts with average, min, and max price, and a daily inventory series for the primary events you track.

30 exports/day each

Event Catalog & Top Moving Events

The Ticketmaster and AXS catalog filtered to events added since a date, plus the day's biggest inventory movers, built for a once-a-day pull that can take a minute or more.

4 + 5 calls/day

Favorites Sync

Favorite Ticketmaster and AXS events by ID or by name, date, venue, and market. Favorite StubHub and TickPick events by ID.

500 writes/day each

Drop, Low, Price & Peak Alerts

Create and update alerts from code, target sections, and filter StubHub and TickPick listings by fees, pairs, parking, piggyback, platinum, limited view, and ADA.

500 writes/day each

Triggered Alerts Feed

Everything that fired in the last 1 to 168 hours, up to 500 rows a call, ready to relay to Slack, Discord, or your POS.

2,000 calls/day
One call

See how any event is selling in one request

Send one Ticketmaster, AXS, Tickets.com, or StubHub event ID and get back the numbers a buying decision needs.

  • Current inventory and the count 24 hours, 7 days, and 30 days ago
  • Capacity and min, median, average, and max price
  • A per-section breakdown of primary and resale inventory with prices on Ticketmaster and AXS events
  • Consistent JSON errors with clear status codes: 400, 401, 403, 404, 429
Book a demo
# base URL https://flare.ticketflipping.com
GET /api/get-event-analytics
    ?token=YOUR_TOKEN
    &source_event_id=0F005E32A6FB3D5C
    &market=TM&include_sections=true

{
  "status": "success",
  "data": {
    "current_inventory": 1842,
    "primary_resale_inventory": 1250,
    "inventory_30d_ago": 2100,
    "inventory_7d_ago": 1950,
    "inventory_24h_ago": 1880,
    "capacity": 50000,
    "min_price": 45.00,
    "median_price": 125.50,
    "max_price": 500.00,
    "avg_price": 150.75,
    "section_inventory_summary": [
      { "section": "101",
        "primary_inventory": 120,
        "resale_inventory": 12,
        "min_primary_price": 129.50,
        "min_price_all_in": 119.75 },
      ...
    ]
  }
}
Diagram of the Ticketflipping API alert loop: your script sets a drop, low, price, or peak alert, Flare watches the market, and your script polls the triggered alerts feed
Alerts

Set ticket price alerts from code, then read what fired

Alerts are the same objects you set in Flare, so a script can create them for every event you favorite, and one endpoint returns everything that triggered across your account.

Drop and low alerts on primary Watch Ticketmaster and AXS favorites for inventory drops or low counts, on the whole event or only the sections you choose, ignoring platinum and ADA seats if you want.
Price and peak alerts on secondary Get alerted when the lowest StubHub or TickPick listing on a favorite falls below a price you set, or rises above one, with fee, pairs, parking, piggyback, platinum, limited-view, and ADA filters. Update or delete alerts in the same call.
Section targeting Pull the valid section names for an event by its Flare event ID, then alert only on the sections you care about.
One feed of what fired Poll the triggered alerts feed for the last 1 to 168 hours, up to 500 rows a call, and relay it to Slack, Discord, SMS, or your POS.
Sold data + history

Vivid Seats sold data: price with real sales, not guesses

Pull individual Vivid Seats sales for the events you track, then build your own comps by zone, section, row, and quantity before you list.

Ticketflipping API sold data response for a Vivid Seats event, listing recent sales by zone, section, row, quantity, price, and sale time
Sold comps by section and row Every sale carries zone, section, row, quantity, price, and the sale timestamp.
What cleared this week Sort by sale date to see which quantities and price points actually moved in the days before you list.
Listing trends (StubHub) Export a daily series of total listings with average, min, and max price for the StubHub events you track.
Inventory history you can keep Export the daily inventory series for the primary events you track and store it for your own charts and models.
Python + Claude Code + OpenAI

Plug the ticket market into the tools you already use

Every endpoint is a plain HTTPS GET or POST, so anything that can make a web request can use it: a Python script, a spreadsheet, an automation, or an AI assistant. Inside Flare, members can also ask the Ticketflipping AI Assistant.

A Python example on every endpoint Copy the request from the docs, paste your token, and you have real data in your terminal in minutes.
Works from Claude Code and OpenAI tools Expose the endpoints as tools and let an assistant tell you how an event is selling or what a section sold for, or have it set a drop alert on your favorites.
Feeds your POS, sheets, and chat JSON drops straight into pandas, Google Sheets scripts, Zapier, Make, n8n, Slack, or Discord.
Python example calling the Ticketflipping API get-event-analytics endpoint and printing inventory, capacity, median price, and section data Ticketflipping API endpoints exposed as tools to Claude Code and OpenAI assistants, with a sample question, tool call, and answer
Membership

API access is included with Enterprise Advanced

One membership, everything in the lower tiers, plus the API on top. Enterprise ADV limits are listed below, and membership caps on favorites and sold-data tracking still apply. Higher and flexible limits are available for custom packages.

Enterprise Advanced
$999/mo
For businesses looking for API access, Historical Sales Data, and more.
  • API Access
  • Historical Data for ALL events
  • 2500 Favorites (Alerts)
  • 200 Sold Data Tracking
+6 more featuresShow less
  • ALL Lower Tier Features
  • ALL Top Moving Event List
  • Event Alerts (Drop, Low, Price)
  • Price HeatMap
  • 50 AI Inquiries/Day
  • Integrate with Claude Code & OpenAI
Get Started
Instant API access after checkout. Cancel anytime.
10,000 per day Event analytics calls, the endpoint behind most daily reports.
2,000 per day Triggered alert reads, enough for a poll every 15 minutes with room to spare.
1,000 per day Sold data pulls, plus 1,000 reads each for favorites and primary alerts.
500 per day TM Live calls, where a seat-level call counts as 3, plus 500 writes each for favorites and alerts.
Questions

Ticket broker API questions, answered

What brokers and developers ask before they connect.

Can I get live Ticketmaster availability through the API?
Yes. The TM Live endpoint fetches Ticketmaster availability at the moment you call it and returns Ticketmaster's own section and offer data, or seat-level availability merged with prices. Seat-level calls use 3 quota units and a short per-minute burst limit applies. When our shared upstream capacity is momentarily saturated, a section-level call may return the most recent cached read, marked as cached and not charged to your quota, or a 503 you can retry in a moment.
How can I track how many tickets are left on Ticketmaster?
Ticketmaster inventory tracking is one call. Call get-event-analytics with the Ticketmaster event ID and you get the current inventory, the counts from 24 hours, 7 days, and 30 days ago, capacity, and price stats. Add include_sections=true for a per-section breakdown of primary and resale inventory. The same call works with AXS, Tickets.com, and StubHub event IDs. The section breakdown is available for Ticketmaster and AXS.
How do I get Vivid Seats sold data for an event?
Call get-sold-data with the Vivid Seats event ID and market=VS. Every sale comes back with zone, section, row, quantity, price, and the sale timestamp, so you can build comps by section before you list. Sold data is available for the Vivid Seats events you track, within your membership's sold-data tracking cap.
How do I set a ticket price drop alert from code?
Favorite the event, then POST the alert. Ticketmaster and AXS favorites take drop and low alerts on primary or resale inventory, scoped to the whole event or to named sections. StubHub and TickPick favorites take price and peak alerts with listing filters, and can be favorited in the same call with auto_favorite. Read what fired from the triggered alerts feed.
Can I get historical ticket price and inventory data for an event?
Yes, as exports. Listing trends returns a daily series of total listings with average, min, and max price for a StubHub event you track, and inventory export returns the daily inventory series for a primary event you track. Both are built to run occasionally and store, with 30 calls a day each.
Can I get AXS inventory or sold-out status by section?
Yes. Call get-event-analytics with include_sections=true for an AXS event and you get per-section inventory and pricing plus a section status: available, sold_out, not_on_sale, unavailable, pending, or unknown_empty. The last one means AXS was checked but did not give enough evidence to classify the event as sold out.
Which marketplaces does the Ticketflipping API cover?
Event analytics for Ticketmaster, AXS, Tickets.com, and StubHub. Inventory history for the primary events you track. Real-time seat-level data for Ticketmaster. Sold data for Vivid Seats. Listing trends for StubHub. Favorites and price or peak alerts for StubHub and TickPick. Drop and low alerts for Ticketmaster and AXS. See the Toolbox for marketplace coverage inside the browser extension.
Can I use it from Claude Code, OpenAI tools, or my own scripts? Do I need to be a developer?
Every endpoint is a plain HTTPS GET or POST with a Python example in the docs. Anything that can make a web request can call it, including Claude Code and OpenAI tools set up with the endpoints as tools. You do not need to be a developer to start. Book a demo and we will walk through it on your own events.
What are the Ticketflipping API rate limits?
Enterprise ADV limits reset daily. Event analytics: 10,000 calls. Triggered alert reads: 2,000, plus 2,000 secondary alert reads. Sold data: 1,000 pulls, with 1,000 reads each for primary favorites, secondary favorites, and primary alerts. Writes: 500 each for primary favorites, secondary favorites, primary alerts, and secondary alerts, plus 500 section lookups and 500 weighted TM Live calls. Exports: 30 each for listing trends and inventory history. Catalog: 4 pulls, and top movers: 5, both meant for once a day. Higher and flexible limits are available for custom packages. Membership caps on favorites and sold-data tracking still apply, and the API reaches beyond them with live pulls such as TM Live.
How much does the Ticketflipping API cost, and where are the docs?
API access is included with Enterprise Advanced at $999/mo and is enabled instantly after checkout. See pricing for the full membership comparison. The complete documentation and your unique token sit inside your Flare account once it is active, and you authenticate by sending that token as a query parameter over HTTPS. Questions before you sign up: mail@ticketflipping.com.

Ready to plug the ticket market into your own tools?

Use the Ticketflipping API to track inventory, price from real sales, and automate your alerts, all from the tools you already run.

Instant API access after checkout Cancel anytime Trusted by thousands of brokers since 2015