/bazarclub/events

POST /api/bazarclub/events

Price: 1 credit

Get full details of a BAZAR.club event by its slug: title, description, category, start/end date, venue address and city, ticket price range, ticket purchase link, organizer contacts, gallery images, and — for touring shows — the list of individual dated performances (tours).

How to use it

Get the full profile of a single BAZAR.club event by its slug. Returns title, tour_name, description, start_at/end_at, doors_open_at, city and address, price_min/price_max with currency, ticket_url, video_url, organizer social contacts, gallery images, is_tour/is_event flags, created_at/published_at, and tours[] (each dated sub-performance of a touring show with its own slug, date and city). Use the slug from bazarclub/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 — Event slug (examples: "delirium-in-boston")

Response

• @type string (default: "BazarclubEvent")
• id integer required
• alias string required
• tour_name string nullable
• description string nullable
• status string nullable
• author string nullable
• category string nullable
• city string nullable
• address string nullable
• start_at string nullable
• end_at string nullable
• doors_open_at string nullable
• price_min number nullable
• price_max number nullable
• currency string nullable
• ticket_url string nullable
• video_url string nullable
• image string nullable
• images array (default: [])
• is_tour boolean (default: false)
• is_event boolean (default: false)
• organizer object nullable
  • @type string (default: "BazarclubOrganizer")
  • instagram string nullable
  • facebook string nullable
  • telegram string nullable
  • whatsapp string nullable
  • website string nullable
  • email string nullable
  • phone string nullable
• tours array (default: [])
  • @type string (default: "BazarclubTourShow")
  • id integer required
  • alias string nullable
  • start_at string nullable
  • city string nullable
• created_at string nullable
• published_at string nullable
• source_url 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 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.