/afishamira/events

POST /api/afishamira/events

Price: 5 credits

Get a full Afisha Mira event by id or page URL: title, description, start and end dates, city, region, country, venue and address, category, performers, ticket price range and currency, external ticket link, image, event status and the event page URL.

How to use it

Fetch a single Afisha Mira event by numeric id or by the slug from its page URL (https://afishamira.com/event/{slug}/). Returns one item with id, title, alias (slug), description, start_at/end_at, city, region, country, venue, address, category, performers, price/price_max, currency, ticket_url (external vendor), image, event_status, source_url and lang.

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 id or page URL slug (examples: "gruppa-sekret-v-kelne-sekret-fm", "https://afishamira.com/event/balet-lebedinoe-ozero-v-vilnyuse/"; minLength: 1)

Response

• @type string (default: "AfishamiraEvent")
• id integer required
• alias string nullable
• description string nullable
• start_at string nullable
• end_at string nullable
• city string nullable
• region string nullable
• country string nullable
• venue string nullable
• address string nullable
• category string nullable
• performers array (default: [])
• price number nullable
• price_max number nullable
• currency string nullable
• ticket_url string nullable
• image string nullable
• event_status string nullable
• source_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 — Event not found (well-formed but nonexistent 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.