Ticketek APImarketplace.ticketek.com.au ↗
Search Australian resale ticket listings on Ticketek Marketplace. Get event performances, venue details, seat info, and live pricing via 4 structured endpoints.
What is the Ticketek API?
The Ticketek Marketplace API gives developers structured access to Australian resale ticket data across 4 endpoints, covering event search, performance schedules, and seat-level pricing. The get_ticket_listings endpoint returns per-listing fields including price_cents, price_including_fees_cents, section, row, quantity, and ticket category — all tied to a specific performance ID retrieved from get_event_products.
curl -X GET 'https://api.parse.bot/scraper/4d50429b-63fa-481e-a7b5-dfff33691c4a/search_events?page=1&limit=10&keyword=concert' \ -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 marketplace-ticketek-com-au-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: Ticketek Marketplace SDK — browse resale tickets with bounded calls."""
from parse_apis.ticketek_marketplace_api import TicketekMarketplace, BrisbaneTicketReport, ResourceNotFound
client = TicketekMarketplace()
# Search events by keyword — limit= caps total items fetched across all pages.
for event in client.events.search(keyword="comedy", limit=5):
print(event.title, event.content_id, event.available_tickets_count)
# Drill into one event's performances via sub-resource navigation.
event = client.events.search(keyword="concert", limit=1).first()
if event:
for performance in event.performances.list(limit=3):
print(performance.when, performance.venue_name, performance.available_tickets_count)
# Get ticket listings for this performance
for listing in performance.listings.list(limit=3):
print(listing.category_name, listing.price_display, listing.quantity, listing.section, listing.row)
# Constructible resource — fetch listings directly by known product_id.
perf = client.performance(product_id="EBPH2026839LL")
try:
for listing in perf.listings.list(limit=5):
print(listing.price_display, listing.price_including_fees_display, listing.is_ga_standing)
except ResourceNotFound as exc:
print(f"Performance not found: {exc}")
# Composite Brisbane search — find all tickets on a given day.
report = client.brisbaneticketreports.search(keyword="Brisbane", day=15, month=8)
print(report.search_keyword, report.target_day, report.total_available_tickets, report.has_ga_standing_tickets)
print("exercised: events.search / performances.list / listings.list / brisbaneticketreports.search")
Full-text search over events listed on Ticketek Marketplace. keyword matches event titles; results are paginated. Each event carries an available_tickets_count indicating current resale inventory. Events with 0 tickets are still returned (useful for monitoring). Paginate via page parameter.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (1-based). |
| limit | integer | Results per page (max 100). |
| keyword | string | Search keyword to filter events by title. |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"events": "array of event objects with title, content_id, from_date, to_date, available_tickets_count, feature_image",
"keyword": "string, the search keyword used",
"has_next": "boolean, whether more pages are available",
"page_size": "integer, number of results per page",
"total_count": "integer, total number of matching events"
},
"sample": {
"data": {
"page": 1,
"events": [
{
"title": "Mamma Mia!",
"to_date": "2026-09-20T08:00:00Z",
"from_date": "2026-09-04T09:30:00Z",
"content_id": "ABBASOPH26",
"feature_image": "sfx357028.jpg",
"available_tickets_count": 1
}
],
"keyword": "concert",
"has_next": true,
"page_size": 10,
"total_count": 440
},
"status": "success"
}
}About the Ticketek API
Event Search and Discovery
The search_events endpoint accepts a keyword string and returns paginated results with per-event fields: title, content_id, from_date, to_date, available_tickets_count, and feature_image. Pagination is controlled via page and limit (up to 100 per page), and the has_next boolean tells you whether further pages exist. The content_id returned here is the key you need to drill into performances.
Performances and Venue Data
get_event_products takes a content_id from search results and returns each individual performance as a product object. Fields include product_id, date, when, venue_name, venue_city, venue_state, and venue_address. This is the layer between an event and its specific ticket listings — you must retrieve a product_id here before querying ticket availability.
Ticket Listings and Pricing
get_ticket_listings accepts a product_id (performance-level, not a content_id) and returns an array of listing objects with quantity, price_cents, price_display, price_including_fees_cents, category name, section, and row. The response also includes total_listings and a has_ga_standing_tickets boolean indicating whether any general admission standing inventory is present.
City and Date Composite Lookup
The get_brisbane_tickets_on_date endpoint (despite the name, it accepts any keyword and filters by venue_city) combines event search, performance filtering by day and optional month, and ticket listing retrieval into a single response. It returns ticket_types with full seat and pricing detail, brisbane_events_on_day with venue and availability summaries, total_available_tickets, and a ga_standing_note field describing GA standing stock in human-readable form.
The Ticketek API is a managed, monitored endpoint for marketplace.ticketek.com.au — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when marketplace.ticketek.com.au 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 marketplace.ticketek.com.au 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?+
- Track resale price trends for a specific artist's tour by polling
get_ticket_listingsacross multipleproduct_idvalues over time. - Build a live event calendar for a target city by combining
search_eventswithget_event_productsfiltered byvenue_city. - Alert users when ticket
available_tickets_countdrops below a threshold for a watchedcontent_id. - Compare face-value vs resale pricing by mapping
price_centsandprice_including_fees_centsacross multiple performances of the same event. - Identify GA standing availability at a venue using the
has_ga_standing_ticketsflag fromget_ticket_listings. - Aggregate all available ticket categories and sections for a given city and date using
get_brisbane_tickets_on_date. - Surface low-quantity resale listings by filtering
get_ticket_listingsresults wherequantityequals 1 or 2.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Ticketek Marketplace have an official public developer API?+
What does `get_event_products` return, and how is it different from `search_events`?+
search_events returns event-level records identified by content_id — one record per event, regardless of how many performances it has. get_event_products takes a content_id and returns each individual performance as a separate product with its own product_id, date, time (when), and full venue fields including venue_city, venue_state, and venue_address. You need a product_id from this endpoint before you can query ticket listings.Can I retrieve seller information or buyer transaction history through this API?+
Does the `get_brisbane_tickets_on_date` endpoint only work for Brisbane?+
keyword parameter accepts any artist name, event name, or city, and the underlying filtering matches on venue_city from performance data. You can target other cities by passing city-relevant keywords. The endpoint currently does not accept a direct city parameter for explicit filtering — you can fork it on Parse and revise the logic to add a dedicated city input.