Bubilet APIbubilet.com.tr ↗
Access event listings, sessions, ticket pricing, and trending events from bubilet.com.tr across Istanbul, Ankara, Izmir, and other Turkish cities.
What is the Bubilet API?
The Bubilet API exposes 7 endpoints covering event discovery, session scheduling, and ticket availability across major Turkish cities. Use search_events to find concerts, theatre, and sports events by keyword and city, or call get_trending_events to retrieve ordered popularity rankings with full pricing and stock data. Response objects include session-level fields like remainingTickets, discountedPrice, seatGroupName, and serviceFee.
curl -X GET 'https://api.parse.bot/scraper/4b5d6ef5-cfdb-42ae-b9e6-7917a1e38381/search_events?query=konser&city_id=34' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for events by keyword and city. Returns matching events, venues, and performers. Each event includes id, name, slug, venue, session date, and detailed session list. The search term matches against event names, performers, and venues. An empty query returns zero results (the site requires a search term), so supply a keyword.
| Param | Type | Description |
|---|---|---|
| query | string | Search keyword (event name, artist, venue). An empty string yields no events. |
| city_id | integer | City ID. Accepted values: 34=Istanbul, 6=Ankara, 35=Izmir, 7=Antalya, 16=Bursa, 26=Eskisehir. |
{
"type": "object",
"fields": {
"events": "object containing count (integer) and items (array of event objects with id, name, slug, venueName, sessionDate, sessionId, sessionDetails)",
"venues": "object containing count (integer) and items (array of venue matches)",
"performers": "object containing count (integer) and items (array of performer matches)"
},
"sample": {
"data": {
"events": {
"count": 125,
"items": [
{
"id": 45,
"name": "Haluk Levent Konseri",
"slug": "haluk-levent-konseri",
"cityId": 34,
"venueId": "1451",
"cityName": "İstanbul",
"sessionId": 239328,
"venueName": "Jolly Joker Vadistanbul",
"venueSlug": "jolly-joker-vadistanbul",
"sessionDate": "2026-06-26T18:00:00+00:00",
"sessionDetails": [
{
"cityId": 34,
"sessionId": 239328,
"venueName": "Jolly Joker Vadistanbul",
"sessionDate": "2026-06-26T18:00:00+00:00"
}
]
}
]
},
"venues": {
"count": 0,
"items": []
},
"performers": {
"count": 0,
"items": []
}
},
"status": "success"
}
}About the Bubilet API
Event Discovery and Search
The search_events endpoint accepts a query string and an optional city_id (34=Istanbul, 6=Ankara, 35=Izmir, 7=Antalya, 16=Bursa, 26=Eskisehir) and returns three grouped result sets: events, venues, and performers, each with a count and an items array. Event items carry id, name, slug, venueName, sessionDate, and a full sessionList. An empty query string returns zero results, so a meaningful keyword is required. The get_events_this_friday endpoint narrows results further — it resolves the upcoming Friday date automatically and returns only events with a confirmed session on that day, reporting the resolved date in target_date (YYYY-MM-DD format).
Session and Ticket Detail
get_event_sessions takes an event_id from any discovery endpoint and returns an items array of session objects, each with sessionId, venueName, date, price, discountedPrice, remainingTickets, and hasSeatSelection. Once you have a sessionId, pass it to get_session_tickets for ticket-category-level detail: the response includes sessionTickets (an array with seatGroupName, price, discountedPrice, remainingTickets, and serviceFee) plus isSessionActive indicating whether the session is currently open for purchase.
Trending and Category Listings
get_todays_trending_events returns today's trending list for a city in ranked order. The trending_signal field is always trendler_list_order and the rank is positional (1-based), not a numeric score. The coverage object reports any event IDs whose detail fetch failed and any category feeds that were unavailable. get_istanbul_concerts is specific to Istanbul's Konser category: it pages through events sorted ascending by earliest upcoming session date, with each event object including artist, venue_name, venue_address, discounted_price, and session timing. Pagination is controlled via page and page_size (1–100), and the response includes total_events and has_next.
The Bubilet API is a managed, monitored endpoint for bubilet.com.tr — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when bubilet.com.tr 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 bubilet.com.tr 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 a weekend event planner app using get_events_this_friday to surface same-week concerts and shows in Turkish cities
- Track ticket availability and price drops for specific events by polling get_session_tickets for remainingTickets and discountedPrice changes
- Aggregate Istanbul concert schedules sorted by date using get_istanbul_concerts with pagination for a listings calendar
- Display trending events by city using get_todays_trending_events with trendler_list_order rankings for a 'what's hot' widget
- Search for events by artist or venue name via search_events and display performer-level and venue-level match groups separately
- Compare seat categories and service fees across ticket tiers for a session using seatGroupName and serviceFee fields from get_session_tickets
- Monitor stock levels across multiple sessions of an event by iterating get_event_sessions results and checking remainingTickets per session
| 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.