/eventcartel/events/search

POST /api/eventcartel/events/search

Price: 20 credits

Search EventCartel events with filters for category, city, date range, featured status, artist and venue. Returns a paginated list of upcoming events with id, title, category, start/end date, location, minimum price and currency, status, and poster image.

How to use it

Browse EventCartel's event listings. Filter by category (concert, theater, family, party, festival, quizzes, sport, conference, networking, fashion, movies), city slug, start date range (start_after / start_before as YYYY-MM-DD), featured flag, artist or venue. Set count to how many events you want. Each item has id, title, category, start_at, end_at, location, price_min, currency, status and image. Use the id with eventcartel/events to get full event details.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string nullable — Filter by event category (one of: "concert", "theater", "family", "party", "festival", "quizzes", "sport", "conference", "networking", "fashion", "movies")
• city string nullable — Filter by city slug, e.g. new-york (examples: "new-york")
• start_after string nullable — Only events starting on or after this date (YYYY-MM-DD) (examples: "2026-07-01")
• start_before string nullable — Only events starting on or before this date (YYYY-MM-DD) (examples: "2026-12-31")
• featured boolean nullable — Only featured events
• artist string nullable — Filter by artist id or slug
• venue string nullable — Filter by venue id
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "EventCartelSearchEvent")
• id integer required
• category string nullable
• start_at string nullable
• end_at string nullable
• location string nullable
• price_min number nullable
• currency string nullable
• status string nullable
• is_multiple_event boolean (default: false)
• future_event_count integer nullable
• image 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 — The entity was not found, or a precondition failed 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.