/interpark/tickets/search

POST /api/interpark/tickets/search

Price: 1 credit

Search Interpark Ticket shows by keyword with genre, region, sale status, show dates and sort: name, genre, dates, venue, rating, review count and badges

How to use it

Without sale_statuses ended shows are included. Pass a returned id to interpark/tickets, interpark/tickets/schedules or interpark/tickets/reviews. Rows typed @interpark_sports_game are sports events: interpark/tickets answers them while they are on sale and may stop answering later.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "뮤지컬", "아이유"; minLength: 1)
• sort string — Result order (default: "recommended"; one of: "recommended", "best_selling", "ending_soon", "newest")
• genres array — Genres to include (default: []; one of: "musical", "concert", "play", "classic", "exhibition", "sports", "family")
• regions array — Regions to include (default: []; one of: "seoul", "gyeonggi", "incheon", "gyeongnam", "busan", "gyeongbuk", "daegu", "jeonnam", "gwangju", "jeonbuk", "sejong", "chungnam", "daejeon", "chungbuk", "gangwon", "jeju", "ulsan")
• sale_statuses array — Sale statuses to include (default: []; one of: "upcoming", "on_sale", "ended")
• toping_discount boolean — Only shows with a toping membership discount (default: false)
• date_from integer nullable — Show date range start, unix seconds (min: 0)
• date_to integer nullable — Show date range end, unix seconds (min: 0)
• count integer required — Max number of results (min: 1; max: 5000)

Response

• @type string (default: "InterparkSearchItem")
• id string required
• url string required
• goods_key string nullable
• name string nullable
• genre string nullable
• image string nullable
• start_date integer nullable
• end_date integer nullable
• region string nullable
• venue string nullable
• rating number nullable
• review_count integer nullable
• badges array (default: [])
• closed_notice string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.