ticket.yes24.com
Unofficial browser-based YES24 ticketing for high-demand concerts and events.
Build a browser-facing provider for YES24 Ticket. It should cover event discovery, presale and availability monitoring, seat-map and limit checks, queue-aware checkout preparation, explicit purchase confirmation, and post-purchase ticket status. This surface is login-gated and typically involves fairness controls, queueing, and anti-bot sensitivity.
Track concerts and events for schedule changes, presale windows, and inventory movements. This is a monitoring read that helps users catch new openings or cancellation-ticket drops before they disappear.
Submit a claim. Your workspace will be prepared after confirmation.
Sign in to claim
Claiming a bounty requires a GitHub sign-in.
Artist, show, or event name to monitor.
IU 콘서트
Optional event category such as concert, musical, or sports.
concert
Optional start and end dates for schedule changes or sale windows.
{"from":"2026-08-01","to":"2026-08-31"}
Auth required for this operation.
Open an event detail page and retrieve the seating layout, section-level pricing, and purchase limits. Users need this to decide whether a section is reachable and how many tickets they can legally request.
Event or performance identifier.
EVT-20260817-001
Specific performance or date-time identifier when the event has multiple shows.
SHOW-20260817-1900
Optional count used to validate ticket limits.
2
Reserve a seat choice in a queue-sensitive pre-checkout state. The operation should preserve queue or token state when the platform requires waiting, then return the exact seat attempt and any hold window once the user reaches the reservation step.
Event identifier for the chosen performance.
EVT-20260817-001
Specific performance identifier used with the queue step.
SHOW-20260817-1900
Seat or section identifiers the user wants to attempt.
["B10","B11"]
Optional queue or waiting-room token required by some ticketing flows.
Q-9f3a2
Build a checkout preview for the selected event, including taxes, service fees, delivery method, and cancellation rules. The result should let the user see the exact payable total and any penalty or refund constraints before purchase.
Draft reservation created by the seat-selection step.
TKT-55210
Ticket delivery or pickup method such as mobile ticket, SMS, or box office pickup.
mobile
Optional promotional code or discount token.
SAVE5000
Submit the event ticket purchase only after the user explicitly approves the exact seats, total price, and cancellation terms. This is the irreversible purchase step and should not proceed without a clear confirmation gate.
Draft containing the selected seats and checkout preview.
TKT-55210
Payment method or wallet reference to charge.
CARD-1
Explicit user approval to submit the purchase.
true
Retrieve bought tickets, their delivery or pickup method, and their current cancellation status. Users need this for mobile entry, pickup retrieval, or checking whether a refund window is still open.
Optional order identifier to inspect a single purchase.
ORD-77881
Optional event identifier to narrow ticket history.
EVT-20260817-001
Suggested surface — propose changes in your submission if the upstream differs.
Auth required for this operation.
Auth required for this operation.
Auth required for this operation.
Auth required for this operation.
Auth required for this operation.
