Eventbrite shut down public event search on 12 December 2019, and the route is genuinely gone rather than permission-gated — GET /v3/events/search/ returns 404 today while live endpoints such as /v3/categories/ return 401 under the same conditions. What remains is scoped by organization, venue or series ID, which is exactly right for managing your own events and unusable for discovering anyone else's. If you arrived at the Eventbrite API wanting to search events you do not own, there is no configuration that gets you there.
Eventbrite is decisively better at everything downstream of discovery, because it is a ticketing system of record. For an organizer running their own events the API gives lifecycle control with no equivalent here: create, publish and cancel events, ticket classes and inventory, discounts, seat maps, embedded checkout, real payment processing and payouts, refunds, attendee check-in and organization-scoped webhooks. It is also simply a well-built API — OAuth2, continuation-token pagination, an expansion system that avoids N+1 fetches. It is a first-party operations API, which makes it the right tool for selling tickets to events you own and the wrong tool for aggregating events you do not.
If what you needed was the search endpoint that went away, this is a direct answer: nationwide public event search across all 50 states, one key, no per-organizer consent, and a documented OpenAPI 3.1 spec. It will not carry every Eventbrite listing — nothing third-party can — but it searches, which the Eventbrite API no longer does.
Public event search by city and date, no per-organizer consent
curl -H "Authorization: Bearer vn_live_..." \
"https://venunite.com/v1/events?city=Denver&starts_after=2026-09-01T00:00:00Z&limit=50"Not across the catalogue. Public search was removed on 12 December 2019 and the endpoint returns 404. You can read events for organizations that have individually authorized your app via OAuth2, and you can read a specific event by ID.
Some, where they surface publicly. But the point of this feed is the inventory that is not on Eventbrite or any other ticketing platform, and exclude_aggregators=true filters to exactly that.
No. One API key covers the whole feed. There is no per-organizer OAuth step, because these are public listings aggregated from thousands of sources rather than one platform's private data.
60 requests/minute, up to 100 events per page, keyset pagination, OpenAPI 3.1 spec. Your key also works as an MCP connector.