Sydney Event Monitor / API
Structured event feed
Use the feed instead of scraping the dashboard. It exposes the same collected events with source provenance, canonical times, freshness, attendance evidence and venue intelligence.
Endpoint
GET https://events.overengineered.au/feeds/sydney-events.json?month=2026-09Omit month for the current month in Australia/Sydney. The feed accepts the previous 12 months through the next 18 months in YYYY-MM form.
Quick start
const url = new URL(
"https://events.overengineered.au/feeds/sydney-events.json"
);
url.searchParams.set("month", "2026-09");
const feed = await fetch(url).then(r => r.json());
console.log(feed.events);Response
- schemaVersion
sydney-events-v1- sourceCatalogVersion
- The exact 36-source catalogue revision.
- eventPayloadVersion
- The normalised event payload revision.
- collection
- Live or materialized origin and source count.
- latestSourceRelease
- The latest one-time source expansion, including all nine new publishers.
- events
- Normalised event records.
- sources
- Source IDs, collection methods, publisher URLs, health and accepted counts.
- generatedAt
- Collection timestamp.
- dataQualitySummary
- Evidence and resolution totals.
Important semantics
- expectedAttendance
- An evidence-backed estimate when available. Planning upper bounds and venue capacity remain separately labelled.
- attendanceEvidence
- The supporting published observation, comparable, registration limit or venue ceiling.
- venueIntelligence
- Resolved coordinates, nearest transport, confidence and review status.
- dataFreshness
- Whether evidence is fresh, dated or needs review.
- sourceUrl
- The original publisher page. Preserve it for attribution.
Discovery and caching
Responses permit cross-origin requests and are browser-cacheable for five minutes, with a 30-minute shared-cache lifetime. Please respect those headers rather than polling continuously.