/eventcartel/events

POST /api/eventcartel/events

Price: 20 credits

Get full details of an EventCartel event by its id: title, description, category, start and end date/time, venue with address and city/country, ticket price, organizer, artists, poster image and the ticket purchase link.

How to use it

Get the full profile of a single EventCartel event by its numeric id. Returns title, description, category, start_at/end_at, multi-date schedule, venue (name, address, city, country), price_min and currency, organizer, artists, images, and the ticket_url to buy tickets.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — EventCartel event id (examples: "123456")

Response

• @type string (default: "EventCartelEvent")
• id integer required
• description string nullable
• category string nullable
• status string nullable
• tour_id integer nullable
• start_at string nullable
• start_ts integer nullable
• end_at string nullable
• doors_open string nullable
• is_past boolean (default: false)
• is_multiple_event boolean (default: false)
• occurrences array (default: [])
  • @type string (default: "EventCartelOccurrence")
  • id integer required
  • start_at string nullable
  • end_at string nullable
  • location string nullable
  • source_url string nullable
• venue string nullable
• address string nullable
• city string nullable
• country string nullable
• state string nullable
• price_min number nullable
• currency string nullable
• age_restriction string nullable
• organizer string nullable
• artists array (default: [])
• image string nullable
• images array (default: [])
• ticket_url 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.