POST /api/vecher/events/search
Price: 5 credits
List upcoming Vecher events (Russian-language events across Australia and New Zealand). Filter by city and category; with no filter, returns the full upcoming-events listing. Each event has id, title, category, start time, city, country, ticket price and currency, image and source url.
List upcoming Vecher events. Set count to how many you want. Filter by city_name (Sydney, Melbourne, Perth, Brisbane, Gold Coast, Adelaide, Hobart, 'Auckland (NZ)') and category_id (fun, concerts, kids, music, art, sport, education, social, outdoor). Each item has id, title, category, start_at (ISO 8601 UTC), city, country, price, currency, is_free, image and source_url. Use vecher/events with the id for full details.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)city_name string nullable — Restrict the listing to a single city (one of: "Auckland (NZ)", "Sydney", "Melbourne", "Perth", "Brisbane", "Gold Coast", "Adelaide", "Hobart")category_id string nullable — Restrict the listing to a single category (one of: "fun", "concerts", "kids", "music", "art", "sport", "education", "social", "outdoor")count integer required — Max number of events to return (min: 1)@type string (default: "VecherEvent")id string nullabledescription string nullablecategory string nullablestart_at string nullableend_at string nullablecity string nullablecountry string nullablevenue string nullableaddress string nullableprice number nullablecurrency string nullableis_free boolean nullableticket_url string nullablewebsite_url string nullablefacebook_url string nullableimage string nullableorganizer object nullable@type string (default: "VecherOrganizer")id string nullablename string requiredimage string nullabledescription string nullablesource_url string nullablelang string (default: "ru")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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.