/mticket/events/search

POST /api/mticket/events/search

Price: 5 credits

List MTicket events: the cross-country top-events feed, or events for one country, optionally narrowed to a city or category. Returns event cards with title, image, start date, city, country, venue, price and ticket url.

How to use it

List MTicket events. Set count for how many to return. With country='all' you get the cross-country top-events feed. Pick a specific country to list that country's events, and optionally narrow by city (slug like warszawa/berlin/prague) or category (concert/tour/circus/sport); city and category require a specific country. Each item has title, alias, source_url, image, start_at, city, country, venue, price (price_min/price_max)+currency and ticket_url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• country string — Country site to list events from (all = the cross-country top-events feed) (default: "all"; one of: "all", "belgium", "bulgaria", "croatia", "cyprus", "czech", "denmark", "finland", "france", "germany", "hungary", "ireland", "italy", "latvia", "lithuania", "luxembourg", "netherlands", "poland", "portugal", "romania", "slovakia", "slovenia", "spain", "sweden", "switzerland", "turkey", "united_kingdom")
• city string nullable — City slug to list events in one city (e.g. warszawa, berlin, prague)
• category string nullable — Event category to filter by (one of: "concert", "tour", "circus", "sport")
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "MticketEvent")
• id string nullable
• description string nullable
• alias string required
• source_url string required
• category string nullable
• image string nullable
• images array (default: [])
• performers array (default: [])
• start_at string nullable
• end_at string nullable
• city string nullable
• country string nullable
• venue string nullable
• address string nullable
• price number nullable
• price_min number nullable
• price_max number nullable
• currency string nullable
• ticket_url string nullable
• doors_open string nullable
• availability string nullable
• event_status string nullable
• attendance_mode string nullable
• sessions array (default: [])
  • @type string (default: "MticketEventSession")
  • start_at string nullable
  • weekday string nullable
  • doors_open string nullable
  • price number nullable
  • price_min number nullable
  • price_max number nullable
  • currency string nullable
  • buy_url string nullable
• lang 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.