Most event APIs are reselling the same headline inventory, because they are all reading from the same handful of ticketing platforms. The useful question for a local-events product is not who has the most concerts, but who has the farmers market, the county library reading group, the brewery gig and the civic meeting. Those come from thousands of individual sources rather than a few partners, and they are what this feed is built on — with a filter so you can query for exactly that slice rather than taking it on faith.
If you need major ticketed concerts and sports, the ticketing platforms' own APIs are better sources and are free to use within their terms. If you need modelled demand intelligence — predicted attendance, impact radius, spend — PredictHQ built a category around that and this API does not attempt it. This is a listings feed, not a forecasting product.
Building something local: a city guide, a neighbourhood newsletter, a weekend planner, a civic app, or grounding for an assistant that answers what is on near me. The events that make those products feel local are the ones the aggregators never carried.
Farmers markets in Iowa
curl -H "Authorization: Bearer vn_live_..." \
"https://venunite.com/v1/events?state=IA&source=usda&limit=50"Ticketmaster, Eventbrite, AXS, SeatGeek, AEG, Live Nation, DICE and TicketWeb. One list defines both the exclude_aggregators filter and the coverage figure on the API page, so what you read and what you fetch cannot drift apart.
Yes — source=usda, or the internal token form source=scraper:usda. It matches as a prefix, so a per-market feed like scraper:ticketmaster_nv is covered by scraper:ticketmaster.
The ingest pipeline runs continuously and the serving snapshot refreshes throughout the day. Every event carries its startDate and the response is generated per request — nothing is served from a shared cache.
60 requests/minute, up to 100 events per page, keyset pagination, OpenAPI 3.1 spec. Your key also works as an MCP connector.