/eventbrite/events/tickets

POST /api/eventbrite/events/tickets

Price: 10 credits

Get Eventbrite event ticket and pricing information by event id or event URL: sales status, free and sold-out flags, price range and currency, number of ticket classes, availability flags (available tickets, waitlist, early-bird, buy-one-get-one), donations and add-ons flags, and sales start/end dates. The domain parameter selects the country marketplace.

How to use it

Fetch Eventbrite ticket information for a single event by id (e.g. 1439262917129) or event URL. Returns one item with event_id, sales_status, is_free, is_sold_out, min_price, max_price, currency, ticket_class_count, has_available_tickets, has_bogo_tickets, has_early_bird_tickets, waitlist_available, has_donations, has_addons, and sales_start_at/sales_end_at (unix seconds, UTC). Use the domain parameter to select the country marketplace.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — Eventbrite marketplace domain (country site). (default: "eventbrite.com"; one of: "eventbrite.com", "eventbrite.com.ar", "eventbrite.com.au", "eventbrite.at", "eventbrite.be", "eventbrite.com.br", "eventbrite.ca", "eventbrite.cl", "eventbrite.co", "eventbrite.dk", "eventbrite.fi", "eventbrite.fr", "eventbrite.de", "eventbrite.hk", "eventbrite.ie", "eventbrite.it", "eventbrite.com.mx", "eventbrite.nl", "eventbrite.co.nz", "eventbrite.com.pe", "eventbrite.pt", "eventbrite.sg", "eventbrite.es", "eventbrite.se", "eventbrite.ch", "eventbrite.co.uk")
• event string required — Eventbrite event id (e.g. 1439262917129) or an event page URL containing it (examples: "1439262917129", "https://www.eventbrite.com/e/curlfest-2026-tickets-1439262917129"; minLength: 1)

Response

• @type string (default: "EventbriteTickets")
• event_id string required
• sales_status string nullable
• is_free boolean nullable
• is_sold_out boolean nullable
• min_price number nullable
• max_price number nullable
• currency string nullable
• ticket_class_count integer nullable
• has_available_tickets boolean nullable
• has_bogo_tickets boolean nullable
• has_early_bird_tickets boolean nullable
• waitlist_available boolean nullable
• has_donations boolean nullable
• has_addons boolean nullable
• sales_start_at integer nullable
• sales_end_at integer 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 event id, or the page has no event) 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.