kktix.com APIkktix.com ↗
Access KKTIX event data via API: search events by date, price, and category, retrieve ticket availability, and get organizer details across Taiwan's top ticketing platform.
curl -X GET 'https://api.parse.bot/scraper/ee10a9d3-88df-4f29-89e3-99d413d63281/search_events?page=1&query=music' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for events with various filters. Returns a paginated list of events matching the criteria in Atom feed format.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination |
| query | string | Search keyword to filter events by title or description |
| end_at | string | End date filter in YYYY-MM-DD format |
| tag_ids | string | Comma-separated category tag IDs to filter by (use get_event_categories to find IDs) |
| start_at | string | Start date filter in YYYY-MM-DD format |
| max_price | integer | Maximum ticket price filter in TWD |
| min_price | integer | Minimum ticket price filter in TWD |
{
"type": "object",
"fields": {
"entry": "array of event objects with url, published, title, summary, content, and author fields",
"title": "string, search result page title",
"updated": "string, ISO 8601 timestamp of last update"
},
"sample": {
"data": {
"entry": [
{
"url": "https://kpmc.kktix.cc/events/poppoppo2024",
"title": "POP! POP! POP! 流行音樂互動展",
"author": {
"uri": "https://kpmc.kktix.cc",
"name": "高雄流行音樂中心"
},
"content": "時間：2026/01/01 10:00(+0800) ~ 2026/12/31 10:00(+0800)",
"summary": "高雄流行音樂中心，就是 音 樂 的 發 聲 地",
"published": "2026-01-01T10:00:00.000+08:00"
}
],
"title": "Search Event: music - KKTIX",
"updated": "2026-05-14T10:13:31.315+08:00"
},
"status": "success"
}
}About the kktix.com API
The KKTIX API exposes 6 endpoints covering event discovery, ticket inventory, and organizer data from kktix.com, Taiwan's primary event ticketing platform. Use search_events to query events by keyword, date range, price range, and category tag IDs, or call get_event_details to retrieve per-event metadata including venue, capacity, ticket types, and organizer contact information.
Event Search and Discovery
The search_events endpoint accepts up to seven filter parameters — including query for keyword matching, start_at / end_at for date windowing, min_price / max_price in TWD, and tag_ids for category filtering. Results are paginated via the page parameter and return an entry array where each object includes the event url, title, summary, content, and author. To find valid tag_ids, call get_event_categories first; it returns a flat list of category objects with id, name_zh_tw, name_en, name_ja, and animation_class fields covering all categories used on the platform.
Event Details and Ticket Availability
get_event_details takes an event slug — extractable from any URL returned by search_events — and returns a structured event object (name, start/end times, location, capacity, pricing options), a tickets array with per-type id, name, price, start_at, and capacity info, and an organization object with the organizer's name, slug, public_domain, and contact_url. For real-time stock checks, get_event_tickets returns the same ticket array alongside an inventory map keyed by ticket ID and a register_status string (IN_STOCK, CLOSED, or SOLD_OUT). When an event is sold out or closed, the tickets array will be empty.
Featured Events and Organizer Feeds
get_featured_events pulls the KKTIX homepage's promoted content, returning an events array with id, slug, name, start_at, register_status, public_url, and description_summary, plus a headline_banner array of announcement objects with id, subject, and url. For organizer-level browsing, get_organizer_events takes an organizer subdomain and returns an Atom-style feed of all their events, matching the same entry structure as search_events. Organizer subdomains are available in the author field of search results or the slug field of the organization object from event details.
- Monitor ticket availability for high-demand events using
get_event_ticketsand theinventorymap - Build a Taiwan event calendar filtered by date range and ticket price using
search_eventsparameters - Track which categories have the most active listings by combining
get_event_categoriestag IDs withsearch_events - Aggregate an organizer's full event history and upcoming shows via
get_organizer_events - Display homepage-level featured events and banner announcements using
get_featured_events - Extract venue, capacity, and pricing data for event analytics pipelines using
get_event_details
| 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 | 250 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 KKTIX have an official developer API?+
How do I filter search results by category?+
get_event_categories first to retrieve the full list of category objects, each with an id field. Pass one or more of those IDs as a comma-separated string to the tag_ids parameter of search_events. The name_zh_tw, name_en, and name_ja fields on each category let you match IDs to human-readable names in Traditional Chinese, English, or Japanese.What does `register_status` indicate in ticket responses?+
register_status reflects the current registration state of an event. Known values are IN_STOCK (tickets available), SOLD_OUT (no inventory remaining), and CLOSED (registration has ended or not yet opened). When the value is CLOSED or SOLD_OUT, the tickets array returned by get_event_tickets will typically be empty.Does the API cover past events or only upcoming ones?+
search_events accepts start_at and end_at parameters, so you can query date ranges that include past events. However, ticket inventory via get_event_tickets is only meaningful for active events — closed events return an empty tickets array. There is no dedicated endpoint for historical attendance or sales data. You can fork this API on Parse and revise it to add an endpoint targeting historical event archives if that coverage matters for your use case.