TicketsData API documentation

Introduction: What the TicketsData API does, its base URL, endpoints and what each call costs: event search, captures and matches across six ticket marketplaces.

Authentication: Authenticate with your TicketsData API key as a bearer token. One key per account; what 401, 402 and 403 mean.

Quickstart: Search for an event and capture its live ticket listings in two API calls, with cURL, Node and Python examples.

Captures and async: How captures work: waiting for a result or getting 202 and polling, failed captures and error codes.

Event information: The event block returned with every capture: name, UTC and venue-local start time, venue, capacity and seat map.

Coverage and price basis: Which fields each marketplace returns, list vs base vs all-in prices, and how fees are reported, so you can compare prices fairly.

Webhooks: Get a signed capture.completed or capture.failed callback. Payload, delivery and retries, and verifying the signature in Node or Python.

Errors: HTTP status codes and error codes returned by the TicketsData API, what each means, and which are safe to retry.

Rate limits and quotas: Requests per minute, monthly and hourly plan limits, rate-limit headers, and how many requests each call uses.

Search events: GET /v1/events/search: find an event on Ticketmaster, StubHub, Vivid Seats, SeatGeek and Gametime at once, grouped into real-world events.

Create a capture: POST /v1/captures: capture one event’s current ticket listings on one marketplace, with parameters and examples.

Get a capture: GET /v1/captures/{id}: read a capture you started, including one that is still running.

Match an event: POST /v1/matches: find one event on every marketplace and get each one’s ticket summary side by side.

Get a match: GET /v1/matches/{id}: read a match you started, including one that is still running.

List marketplaces: GET /v1/marketplaces: the supported ticket marketplaces, how each identifies events, and what each returns.

The Capture object: Every field of a capture: status, event information, summary, sections, listings, coverage and errors.

The Match object: Every field of a match: the source event, the lowest price and each marketplace’s status and ticket summary.