tulsacal
A trustworthy local-events data utility for Tulsa — source intelligence, freshness, dedupe, and provenance you can verify.
Not a prettier calendar grid. Every event below links back to the source that reported it, with a confidence tier and when it was last verified.
# browse events
Filter the canonical event set. Filter state lives in the URL, so any view is a shareable link.
# source registry
TulsaCal weights official venue / organizer / city sources above aggregators, and labels social posts as sightings until a stronger source confirms them. Coverage, not curation, is the moat.
# how this data is built
Observations (what a source said, when) are stored separately from canonical events (what the calendar currently believes). Duplicates merge; events never silently disappear.
# data & api
The product is the data. Reuse it.
events.json
Canonical events with full provenance per record.
{
"event_id": "…",
"title": "…",
"status": "scheduled",
"start": "2026-06-20T18:00:00-05:00",
"venue_name": "…",
"city": "Tulsa",
"categories": ["…"],
"source_confidence": "high",
"canonical_url": "https://…",
"source_urls": ["https://…"],
"first_seen": "…",
"last_verified": "…"
}
tulsa.ics
RFC 5545 calendar feed. Subscribe in Apple/Google Calendar with a
webcal:// URL, or download the file.
webcal://tulsacal.samcarlton.com/data/tulsa.ics
license & attribution
Thin factual event records. TulsaCal's compilation is published under CC BY 4.0; each record links to its primary source.
- Attribute as: “Event data compiled by TulsaCal (CC BY 4.0); source: <venue>.”
- Per-source rights are tracked in the registry.
- Aggregators are used for discovery only, then traced to a primary source.
what this is not
- Not a hand-curated “best of” calendar.
- Not a place that silently deletes events when a source drops them.
- Not scraping social without provenance — social posts are labeled sightings.
It’s the source layer the calendars are built on.