Live event inventory check API

Check an event’s live inventory in one API call. Every capture counts what is listed right now on the marketplace you choose — tickets, listings and tickets per section — with the venue’s capacity alongside, so you can see how much is left and where.

Inventory changes by the minute: listings sell, get repriced and new ones appear. A count from this morning is already stale by the evening of a big on-sale.

Each marketplace also counts differently — per listing, per ticket, per section. TicketsData returns the same counts from every marketplace: summary.ticketCount and summary.listingCount for the event, and quantity and listingCount for each section.

How it works

1. Find the event: Search by team, artist or venue to get the event’s ID or URL on each marketplace, or start from a link you already have.

2. Check its inventory: Capture the event. One request returns the live counts for that marketplace, plus every listing if you want the detail.

3. Check every marketplace at once: A match finds the same event on the other marketplaces and returns each one’s ticket count and cheapest price side by side. It uses 3 requests.

4. Watch it change: Repeat the check on a schedule and store the counts to see an event selling through, or alert when a section drops below a threshold.

Questions

What does the ticket count mean?

summary.ticketCount is the number of tickets listed for sale on that marketplace at the moment of the capture; summary.listingCount is the number of listings they’re in. It is not the venue’s unsold seats — venue.capacity gives the venue’s size.

Can I get ticket counts per section?

Yes. data.sections lists every section with its ticket quantity, number of listings and lowest price, so you can see which parts of the venue are running low.

How many requests does an inventory check use?

One per capture, or 3 for a match across every marketplace. Failed requests are free.

Is it real-time?

Yes. Each capture reads the marketplace’s current listings when you ask; nothing is served from yesterday’s data.