Where our listings come from
We publish facts — what is on, where, when, how much, and where to buy a ticket. Facts are not copyrightable, and we do not republish promoters’ descriptions or photography. Anything you read on this site that is not a bare fact was written by us.
The calendar currently carries 469 events from the sources below. Where a source is not connected yet, this page says so rather than implying coverage the calendar does not have.
VisitReno editorial
Live. Reno's signature annual events and anything a person has verified by hand.
Written by VisitReno. Ours to publish.
University of Nevada, Reno
Live. The university runs Localist, which publishes an open JSON API expressly for calendar syndication — no key, no scraping. Around 119 events in a 30-day window: lectures, exhibitions, recitals, public programming. University-internal entries (defences, staff meetings, deadlines) and virtual-only events are filtered out.
Public university calendar published through Localist's open syndication API. Facts only (Feist v. Rural): title, dates, times, venue, price posture and links. Descriptions are read to categorise and never stored.
- Live. Localist public API, 119 events in the next 30 days at last check.
MLB Stats API (Reno Aces)
Live. The authoritative Triple-A schedule, free and unauthenticated. Roughly 75 home dates a year at Greater Nevada Field — by volume the largest single block of things to do on a Reno evening. Home games only; away games are not things a visitor can attend.
Public schedule data from MLB's Stats API. Pure fact — fixture, date, time, venue. No description or imagery is taken.
- Live. MLB Stats API, Pacific Coast League. Home games only.
Venue and district calendars
Live. Reno organisations that publish their own calendar through The Events Calendar, a WordPress plugin whose REST API is public and unauthenticated by design. Currently the Downtown Reno Partnership and the Holland Project; the list is in `lib/events/feeds.ts` and is the one most likely to grow, because switching a newly-found calendar on is a data change.
Public calendars published by each organisation through an open REST API, for their own programming. Facts only (Feist v. Rural): title, dates, times, venue, price posture and links. Descriptions are read to categorise and never stored.
- Live. The downtown business improvement district's own calendar — 66 upcoming events at last check, including the Wingfield Park and Arch District programming no ticketing API carries. robots.txt permits everything.
- Live. Reno's independent all-ages music and arts venue — 35 upcoming shows at last check. Exactly the programming that ticketing APIs miss, because most of it never goes on sale through one.
- REJECTED, not merely unconfigured. The feed works and returns 5,229 entries, but roughly 94% are standing commercial promotions — daily drink specials and happy hours at every bar in the district, republished as one 'event' per day. Sampling 250 upcoming entries found 16 genuine events. Ingesting it would bury Reno's real calendar under 'Burger, Beer, & Shot $20 Any Day'. Worth revisiting only if the district ever separates its events from its specials.
- Verified and used as a research source rather than ingested. The rodeo is a curated signature event with its own evergreen page, so nine feed rows for its sub-events would compete with it in listings. Its 2027 dates were read from here and written into `curated.ts`. Note their robots.txt bars any URL with a query string — the wildcard-aware parser in `adapters/robots.ts` enforces that.
Ticketmaster Discovery API
Live. Searched by map point and by city, then filtered through the same definition of the region every other source uses, so nothing from Sacramento or southern Nevada reaches the calendar. Covers the casino showrooms, the Reno Events Center, the Grand Sierra and most touring acts routed through northern Nevada.
Ticketmaster Developer Terms of Use. Attribution and a link to the Ticketmaster event page are required; the API is for displaying event information and driving ticket sales.
SeatGeek Platform API
Not configured. SeatGeek's partner programme is the more accessible of the two major ticketing APIs and pays affiliate commission, which makes it the better second source. Needs SEATGEEK_CLIENT_ID.
SeatGeek Platform terms. Attribution and link-back required.
Venue iCalendar feeds
Adapter written, including the all-day DTEND off-by-one that makes every festival a day too long if taken literally. No Reno venue has yet been confirmed to publish an .ics endpoint — the candidates are listed in `lib/events/feeds.ts` and switch on individually once a URL is verified.
Feeds published by venues for calendar syndication. Facts only (Feist v. Rural): dates, times, venue and ticket links. Descriptions are never stored.
- Candidate. The Pioneer Center publishes a season calendar but no .ics endpoint was found at the obvious paths; needs a look at what their ticketing platform exposes.
- Candidate. Programming is largely visible through Ticketmaster; the Discovery API is the better route to it than a venue feed.
Venue schema.org Event data
Adapter written, with its own robots.txt check before any fetch. Reads `Event` JSON-LD that venues publish on their own pages for search engines, from an explicit page allowlist in `lib/events/feeds.ts` — never a crawl. The Nevada Museum of Art permits fetching but currently publishes no Event markup on its events index; Artown is the highest-value candidate and is a conversation rather than an endpoint.
Structured data a publisher embeds expressly so machines can read and act on it. Facts only — name, date, time, location, offers, URL. Descriptions and images are not stored.
- Reachable and robots.txt permits it, but the events index carries only WebPage and Organization JSON-LD — no Event objects. Individual exhibition pages need checking before this can be switched on.
- Candidate, and the highest-value one on this list: around 350 events across July at about 100 venues. No WordPress events API at the standard paths. Worth a direct approach to the organisers — Artown is exactly the kind of programming a data-sharing agreement should cover.
Destination marketing partner feed
Not configured. The regional tourism authority and the Downtown Reno Partnership both maintain event calendars. A direct data-sharing arrangement is the right long-term answer for breadth of coverage, and is a business conversation rather than an engineering one.
To be governed by a written agreement before any ingestion.