/vecher/events

POST /api/vecher/events

Price: 1 credit

Get full Vecher event details by event id or event page URL: title, description, start and end time, city, country, address, ticket price and currency, external ticket, website and Facebook urls, image and the organizer (Russian-language events across Australia and New Zealand).

How to use it

Fetch one Vecher event by id (e.g. 385) or its event URL. Returns one item with id, title, description, start_at and end_at (ISO 8601 UTC), category, city, country, address, price, currency, is_free, ticket_url, website_url, facebook_url, image, organizer and source_url. Discover events via vecher/events/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• event string required — Vecher event id or event page URL (examples: "385", "https://vecher.com.au/events/385"; minLength: 1)

Response

• @type string (default: "VecherEvent")
• id string nullable
• description string nullable
• category string nullable
• start_at string nullable
• end_at string nullable
• city string nullable
• country string nullable
• venue string nullable
• address string nullable
• price number nullable
• currency string nullable
• is_free boolean nullable
• ticket_url string nullable
• website_url string nullable
• facebook_url string nullable
• image string nullable
• organizer object nullable
  • @type string (default: "VecherOrganizer")
  • id string nullable
  • name string required
  • image string nullable
  • description string nullable
• source_url string nullable
• lang string (default: "ru")

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 — Event not found (well-formed but nonexistent event id) 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.