/cyprusbz/events

POST /api/cyprusbz/events

Price: 1 credit

Get a single Cyprus.BZ event by its public id or url slug. Returns the full event: title, full description, frequently asked questions, start and end time, city, venue and address with coordinates, price range, category, spoken languages, organizer details, ticket link, source, lineup of performers and image. Set locale to choose the language of the localized texts (ru, en, el).

How to use it

Get one Cyprus.BZ event by public id (e.g. 00003015 or 3015, as returned by cyprusbz/events/search) or url slug. Returns id, alias, title, description (full), faq (question/answer list), start_at, end_at, multiday, city / city_slug / city_emoji, venue / venue_alias, address, latitude, longitude, venue_maps_url, is_free, price_min, price_max, price_text, currency, category / category_slug / category_slugs, languages (spoken), available_locales (locales with localized content), age_restriction, organizer / organizer_contact / organizer_website, ticket_url, source, source_url, performers (name, alias, image) and image. locale (ru/en/el) selects the language of the localized texts; a slug is locale-specific while the public id is not.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• event string required — Event public id (e.g. 00003015 or 3015) or url slug (examples: "00003015", "echo-wants-her-voice-back-2026")
• locale string — Language of localized texts (default: "ru"; one of: "ru", "en", "el")

Response

• @type string (default: "CyprusbzEvent")
• id string required
• alias string nullable
• description string nullable
• start_at string nullable
• end_at string nullable
• is_multiday boolean nullable
• city string nullable
• city_slug string nullable
• city_emoji string nullable
• venue string nullable
• venue_alias string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• venue_maps_url string nullable
• is_free boolean nullable
• price_min number nullable
• price_max number nullable
• price_text string nullable
• currency string nullable
• category string nullable
• category_slug string nullable
• category_slugs array (default: [])
• languages array (default: [])
• available_locales array (default: [])
• age_restriction string nullable
• organizer string nullable
• organizer_contact string nullable
• organizer_website string nullable
• ticket_url string nullable
• source string nullable
• source_url string nullable
• performers array (default: [])
  • @type string (default: "CyprusbzPerformer")
  • name string required
  • alias string nullable
  • image string nullable
• faq array (default: [])
  • @type string (default: "CyprusbzFaqItem")
  • question string required
  • answer string required
• image 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 — Event not found for the given id or slug 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.