POST /api/ticketmaster/events/search
Price: 20 credits
Search Ticketmaster events by keyword (artist, event, team, or venue). Returns worldwide matches (domestic and international). Each item is an event with name, event page URL, start and on-sale dates, timezone, category, partner and availability flags, presale windows, the venue (name, address, city, state, country and coordinates), and the line-up of attractions. Optional filters: category segment and start/end date range.
Search Ticketmaster events by keyword. Results are worldwide (not limited to one country). Set count to how many events you want. Optional filters: category (Music, Sports, Arts & Theatre, Film, Miscellaneous), start_date/end_date (YYYY-MM-DD), sort (date or relevance). domain selects the marketplace/localization the request runs against (e.g. ticketmaster.com or ticketmaster.co.uk). Each item has id, name, discovery_id, url, image, start_at, end_at, onsale_at, date_display, span_multiple_days, timezone, category, is_partner, is_sold_out, is_cancelled, is_postponed, is_rescheduled, is_tba, is_virtual, is_local, has_limited_availability, ticketing_status, event_change_status, presales, venue and artists.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string required — Search keyword — an artist, event, team, or venue name (minLength: 1)count integer required — Max number of events to return (min: 1)category string nullable — Filter events by category segment (one of: "Music", "Sports", "Arts & Theatre", "Film", "Miscellaneous")start_date string nullable — Only events on or after this date (YYYY-MM-DD) (examples: "2026-09-01")end_date string nullable — Only events on or before this date (YYYY-MM-DD) (examples: "2026-10-01")sort string — Result order by relevance or event date (default: "relevance"; one of: "relevance", "date")domain string — Ticketmaster marketplace domain (default: "ticketmaster.com"; one of: "ticketmaster.com", "ticketmaster.co.uk", "ticketmaster.com.au", "ticketmaster.co.nz", "ticketmaster.ca", "ticketmaster.com.mx", "ticketmaster.com.br", "ticketmaster.cl", "ticketmaster.ie", "ticketmaster.de", "ticketmaster.at", "ticketmaster.ch", "ticketmaster.nl", "ticketmaster.be", "ticketmaster.fr", "ticketmaster.es", "ticketmaster.it", "ticketmaster.pl", "ticketmaster.cz", "ticketmaster.dk", "ticketmaster.no", "ticketmaster.se", "ticketmaster.fi", "ticketmaster.ae", "ticketmaster.co.za", "ticketmaster.co.il", "ticketmaster.sg")@type string (default: "TicketmasterEvent")id string requiredname string requireddiscovery_id string nullableurl string nullableimage string nullablestart_at string nullableend_at string nullableonsale_at string nullabledate_display string nullablespan_multiple_days boolean nullabletimezone string nullablecategory string nullableis_partner boolean nullableis_sold_out boolean nullableis_cancelled boolean nullableis_postponed boolean nullableis_rescheduled boolean nullableis_tba boolean nullableis_virtual boolean nullableis_local boolean nullablehas_limited_availability boolean nullableticketing_status string nullableevent_change_status string nullablepresales array (default: [])@type string (default: "TicketmasterPresale")name string nullablestart_at string nullableend_at string nullablevenue object nullable@type string (default: "TicketmasterEventVenue")id string nullablename string nullablecity string nullablestate string nullablecountry string nullablecountry_code string nullableaddress string nullablepostal_code string nullablelatitude number nullablelongitude number nullableurl string nullableimage string nullableartists array (default: [])@type string (default: "TicketmasterEventArtist")id string nullablename string nullableurl string nullableimage string nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.