TicketWeb APIticketweb.com ↗
Search TicketWeb event listings by keyword, date range, location, and sold-out status. Returns event IDs, dates, venue details, and pagination info.
What is the TicketWeb API?
The TicketWeb API exposes one endpoint, search_events, that queries TicketWeb's full event catalog and returns up to 20 results per page, each containing 8+ fields including event ID, name, URL, local start date/time, venue details, and listing status. You can filter by keyword, date window, city, and sold-out status, making it straightforward to pull structured event data without visiting the site directly.
curl -X GET 'https://api.parse.bot/scraper/ae0040c3-3248-494e-9853-452131ac951f/search_events?query=jazz' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace ticketweb-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: TicketWeb SDK — search events, inspect results."""
from parse_apis.ticketweb_com_api import TicketWeb, InputFormatInvalid
client = TicketWeb()
# Search for jazz events near Chicago, capped to 5 total results.
for event in client.events.search(query="jazz", location="Chicago, IL", limit=5):
print(event.name, "|", event.date_text, event.time_text)
print(" Venue:", event.venue_name, "-", event.location)
if event.availability:
print(" Availability:", event.availability)
# Drill into the first result of a date-filtered search.
try:
hit = client.events.search(
query="jazz",
start_date="2026-10-01",
end_date="2026-10-31",
hide_sold_out=True,
limit=1,
).first()
except InputFormatInvalid as e:
print("Bad input:", e.message)
hit = None
if hit is not None:
print("First October jazz event:", hit.name)
print(" Start:", hit.start_date)
print(" Performers:", ", ".join(hit.performers))
print(" Tickets:", hit.url)
print("exercised: events.search")
Searches TicketWeb's event listings for a keyword and returns one page of matching events (20 per page, ordered by event date as the site lists them). Each event row carries the event and venue identifiers, an ISO-like local start date/time, the listing status label as shown on the site (for example 'Find Tickets', 'Sold Out' or 'Cancelled'), performers and a listing image. When a location is supplied the site groups results into a 'Near <city>' section followed by other locations; the `section` field on each event and the `sections` summary preserve that grouping. Paging is controlled by `page` (1-based; omitted means page 1); `total_pages` comes from the site's pager and `has_more` tells whether a later page exists. A keyword with no matches or a page past the last one returns an empty `events` array with `total_pages` 0. One request per call.
| Param | Type | Description |
|---|---|---|
| page | integer | 1-based results page number. |
| queryrequired | string | Free-text search keyword (artist, event or venue name, genre). |
| end_date | string | End of an inclusive event-date window, ISO date YYYY-MM-DD. Must be supplied together with start_date. |
| location | string | City to prioritise, as 'City, ST' (one shape: Chicago, IL). Matching events are returned first in a 'Near <city>' section, followed by events elsewhere in the country. |
| start_date | string | Start of an inclusive event-date window, ISO date YYYY-MM-DD. Must be supplied together with end_date. |
| hide_sold_out | boolean | When true, events the site marks as sold out are excluded from the page. |
{
"type": "object",
"fields": {
"page": "integer, the page returned",
"query": "echo of the search keyword",
"events": "array of event rows: event_id (string), name, url, start_date (local 'YYYY-MM-DDTHH:MM', null if not published), date_text and time_text as displayed, venue_name, venue_id (string), venue_url, location ('City, ST'), performers (array of names), image URL, availability (schema.org value such as 'InStock', null when not offered), status (site label such as 'Find Tickets', 'Sold Out', 'Cancelled'), section (label of the grouping the row belongs to)",
"has_more": "boolean, true when page < total_pages",
"sections": "array of {label, count}: the site's result groupings on this page (e.g. 'Near Chicago', 'United States - Other Locations') and how many events each holds",
"total_pages": "integer, number of result pages the site's pager exposes (0 when there are no results)"
},
"sample": {
"data": {
"page": 1,
"query": "jazz",
"events": [
{
"url": "https://www.ticketweb.com/event/the-high-society-new-orleans-birdland-theater-tickets/14881333",
"name": "The High Society New Orleans Jazz Band",
"image": "https://www.ticketweb.com//i/00/13/47/83/93_Listings.jpg?v=3",
"status": "Find Tickets",
"section": "United States - All Locations",
"event_id": "14881333",
"location": "New York, NY",
"venue_id": "553788",
"date_text": "Thu Sep 17",
"time_text": "4:30 PM Doors - 6:45 PM",
"venue_url": "https://www.ticketweb.com/venue/birdland-theater-new-york-ny/553788",
"performers": [
"The High Society New Orleans Jazz Band"
],
"start_date": "2026-09-17T17:30",
"venue_name": "Birdland Theater",
"availability": "InStock"
}
],
"has_more": true,
"sections": [
{
"count": 20,
"label": "United States - All Locations"
}
],
"total_pages": 5
},
"status": "success"
}
}About the TicketWeb API
What the API Returns
The single search_events endpoint accepts a required query string (artist name, event title, venue name, or genre) and returns a paginated list of matching events from TicketWeb. Each event row includes event_id, name, url, start_date (a local ISO-formatted datetime like 2024-11-15T19:30, or null when not yet published), date_text, time_text, and the listing status label as it appears on the site. Pagination metadata is returned as page, total_pages, and has_more.
Filtering and Location
Two optional date parameters — start_date and end_date — must be supplied together as YYYY-MM-DD strings to restrict results to a specific window. The location parameter accepts a city in City, ST format (e.g., Chicago, IL); when provided, geographically nearby events surface first under a labeled section such as Near Chicago. The hide_sold_out boolean removes events the site marks as sold out from the returned page. The page parameter (1-based) steps through result pages when has_more is true.
Sections and Result Groupings
Each response includes a sections array that mirrors how TicketWeb groups results on the page — for example, [{"label": "Near Chicago", "count": 5}, {"label": "United States - Other Locations", "count": 15}]. The count in each section reflects how many results from that page belong to that grouping, which is useful for understanding geographic distribution of results without issuing additional requests.
Pagination Behavior
Results are ordered by event date as the site presents them. total_pages returns 0 when no results match the query. When iterating through a large result set, increment the page parameter and check has_more to determine whether more pages exist. Note that TicketWeb's pager exposes a finite number of pages, so total_pages reflects the site's own pager ceiling rather than an unbounded count.
The TicketWeb API is a managed, monitored endpoint for ticketweb.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ticketweb.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official ticketweb.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build an event discovery feed filtered by city and date range using
location,start_date, andend_date. - Monitor availability by periodically calling
search_eventswithhide_sold_out: trueto detect when sold-out shows reopen. - Aggregate artist touring schedules by querying an artist name and iterating through all result pages.
- Power a venue-specific event calendar by passing a venue name as the
queryparameter. - Track listing status labels over time to identify events that transition from available to sold out.
- Identify geographic demand patterns using the
sectionsarray to compare local vs. national result counts for a given artist.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does TicketWeb have an official developer API?+
What does the `sections` field in the response represent?+
sections array reflects the result groupings TicketWeb applies to a search page — for example, Near Chicago and United States - Other Locations. Each entry includes a label and a count of how many events on that page fall into that group. This is useful when using location to understand how many results are geographically local versus national.Does the API return ticket prices or purchase links for individual events?+
url (a direct link to the TicketWeb listing), event name, start date/time, venue identifiers, and listing status, but does not include ticket price tiers or seat-level availability data. You can fork this API on Parse and revise it to add an endpoint that retrieves pricing details from individual event pages.How does date filtering work, and what happens if only one date is provided?+
start_date and end_date must always be supplied together as a pair in YYYY-MM-DD format. Providing only one of the two parameters will not apply a date filter. Both fields are optional, but they are interdependent — neither has effect without the other.Does the API cover events outside the United States?+
sections labels returned by the API. International coverage is limited to what the site itself indexes. The location parameter currently only accepts a City, ST format, so non-US location filtering is not directly supported. You can fork this API on Parse and revise it to handle international city formats if TicketWeb adds broader international coverage.