/eventbrite/organizers/events

POST /api/eventbrite/organizers/events

Price: 1 credit

List an Eventbrite organizer's upcoming events by organizer id or organizer URL. Each item includes id, name, url, summary, start and end date/time with timezone, online flag, cancellation flag, image, venue with address and coordinates, price range, and sales status. The domain parameter selects the country marketplace.

How to use it

List an Eventbrite organizer's upcoming events by id (e.g. 64371789233) or organizer URL. Set count to how many results you want. Each item has id, name, url, summary, start_at/end_at (unix seconds, UTC) plus start_local/end_local and timezone, is_online, is_cancelled, image, venue (name, address, city, region, country, postal_code, latitude, longitude), price (min_price, max_price, currency, is_free), and sales_status. 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")
• organizer string required — Eventbrite organizer id (e.g. 64371789233) or an organizer page URL containing it (examples: "64371789233", "https://www.eventbrite.com/o/curly-girl-collective-64371789233"; minLength: 1)
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "EventbriteOrganizerEvent")
• id string required
• name string required
• url string required
• summary string nullable
• start_at integer nullable
• end_at integer nullable
• start_local string nullable
• end_local string nullable
• timezone string nullable
• is_online boolean nullable
• is_cancelled boolean nullable
• image string nullable
• venue object nullable
  • @type string (default: "EventbriteVenue")
  • id string nullable
  • name string nullable
  • address string nullable
  • city string nullable
  • region string nullable
  • country string nullable
  • postal_code string nullable
  • latitude number nullable
  • longitude number nullable
• price object nullable
  • @type string (default: "EventbritePrice")
  • min_price number nullable
  • max_price number nullable
  • currency string nullable
  • is_free boolean nullable
• sales_status 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.