Skip to content
/bounty
Sign in
All bounties

Interpark Ticket

Open
tickets.interpark.com

Unofficial browser-based Interpark ticketing for high-demand concerts and events.

Reward
₩500,000
Tier
Platinum
Auth
Browser
APIs
6 APIs
Working now
none
Posted
2026-07-07
Kind
New service
Lifecycle
  1. Open
  2. Claimed
  3. In review
  4. Finalizing
  5. Syncing
  6. Merged
  7. Paid

Scope

Build a browser-facing provider for Interpark 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.

Expected APIs

6
monitor-event-schedules-presales-availabilityMonitor event schedules, presales, and availability changesReadHard

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.

Inputs
  • event_namestringOptionalArtist, show, or event name to monitor.Example IU 콘서트
  • categorystringOptionalOptional event category such as concert, musical, or sports.Example concert
  • date_rangeobjectOptionalOptional start and end dates for schedule changes or sale windows.Example {"from":"2026-08-01","to":"2026-08-31"}
Outputs
event_idevent_namesale_statussale_start_atavailabilitypresale_status
Acceptance
  • Reports schedule or sale-window changes for the requested event set.
  • Surfaces availability or cancellation-ticket movement when the source exposes it.
  • Preserves presale and on-sale status details rather than collapsing everything into a generic listing.

Auth required for this API.

get-seat-map-section-prices-ticket-limitsGet seat map, section prices, and ticket limitsReadHard

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.

Inputs
  • event_idstringRequiredEvent or performance identifier.Example EVT-20260817-001
  • show_idstringOptionalSpecific performance or date-time identifier when the event has multiple shows.Example SHOW-20260817-1900
  • ticket_countnumberOptionalOptional count used to validate ticket limits.Example 2
Outputs
seat_mapsection_pricesticket_limitsremaining_seatssale_window
Acceptance
  • Returns a seat map or section map for the chosen performance.
  • Includes section prices and the event's ticket-per-account or ticket-per-order limit.
  • Fails clearly if the event requires a different show identifier or the session is not authorized.

Auth required for this API.

prepare-queue-aware-seat-selectionPrepare queue-aware seat selectionWriteHard

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.

Inputs
  • event_idstringRequiredEvent identifier for the chosen performance.Example EVT-20260817-001
  • show_idstringRequiredSpecific performance identifier used with the queue step.Example SHOW-20260817-1900
  • seat_idsarrayRequiredSeat or section identifiers the user wants to attempt.Example ["B10","B11"]
  • queue_tokenstringOptionalOptional queue or waiting-room token required by some ticketing flows.Example Q-9f3a2
Outputs
reserved_seatsqueue_statehold_expires_atselection_errors
Acceptance
  • Preserves queue or waiting-room context when the flow requires it.
  • Returns a temporary hold for the chosen seats when they can be locked.
  • Reports seat conflicts or queue rejection as structured errors instead of silently retrying.

Auth required for this API.

prepare-checkout-final-amount-cancellation-policyPrepare checkout with final amount and cancellation policyWriteMedium

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.

Inputs
  • booking_draft_idstringRequiredDraft reservation created by the seat-selection step.Example TKT-55210
  • delivery_methodstringOptionalTicket delivery or pickup method such as mobile ticket, SMS, or box office pickup.Example mobile
  • coupon_codestringOptionalOptional promotional code or discount token.Example SAVE5000
Outputs
final_amountservice_feesdelivery_methodcancellation_policydiscounts_applied
Acceptance
  • Shows a final amount that includes fees and any applied discounts.
  • Includes cancellation or refund rules tied to the selected event or ticket type.
  • Rejects incomplete drafts that do not have a locked seat or event reference.

Auth required for this API.

confirm-ticket-purchaseConfirm purchase only after explicit user approvalWriteHard

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.

Inputs
  • booking_draft_idstringRequiredDraft containing the selected seats and checkout preview.Example TKT-55210
  • payment_method_idstringRequiredPayment method or wallet reference to charge.Example CARD-1
  • user_confirmationbooleanRequiredExplicit user approval to submit the purchase.Example true
Outputs
order_idpayment_statusticket_countissued_atpickup_method
Acceptance
  • Requires an affirmative confirmation before the purchase is submitted.
  • Returns the issued order or reservation identifier with payment outcome.
  • Fails safely if the queue token, seat hold, or payment authorization has expired.

Auth required for this API.

list-tickets-pickup-cancellation-statusList tickets, pickup method, and cancellation statusReadMedium

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.

Inputs
  • order_idstringOptionalOptional order identifier to inspect a single purchase.Example ORD-77881
  • event_idstringOptionalOptional event identifier to narrow ticket history.Example EVT-20260817-001
Outputs
order_idpickup_methodticket_codeticket_countcancellation_status
Acceptance
  • Returns ticket or pickup details for authenticated purchases.
  • Exposes current cancellation eligibility or refund state for each order.
  • Allows filtering by order or event without losing the ticket code field.

Auth required for this API.

Suggested surface. Propose changes in your submission if the upstream differs.

Acceptance criteria

  • Service scaffolded from the public @apifuse/provider-sdk
  • All listed APIs implemented with Zod/Standard Schema input & output
  • Each API declares exactly one of healthCheck or healthCheckUnsupported
  • Real upstream fixture data included where applicable
  • bun run check and bun run test pass
  • Auth, credential and env-secret behavior documented. No real secrets committed

Evidence to submit

  • Workspace repository and main commit link
  • SDK version/tag and the create command used
  • API list with input/output summaries
  • healthCheck coverage table per API
  • bun run check and bun run test output

Ready to claim?

Submit a claim. Your workspace is prepared after confirmation.