Machine-readable

Open data

Everything on this site is generated from a public Git repository, and published here as JSON and CSV. No key, no login, no rate limit. Free to reuse with attribution.

Last generated from source data verified 2 Aug 2026. Files rebuild automatically whenever the dataset changes.

Victorian state election 2026

Available data files
File Contents Records Formats
candidates Every candidacy record, with its full status history and sources. 263 JSON CSV
districts All 88 Legislative Assembly districts, their Council region and sitting member. 88 JSON CSV
council-members Sitting members of the Legislative Council, by region, as the seats are held today. 40 JSON CSV
retirements Sitting members who have confirmed they will not recontest. 22 JSON CSV
parties Parties on the VEC register, with any public commitment they have made. 18 JSON
regions The 8 Legislative Council regions. 8 JSON
representation Seats each party holds right now in each house of the current parliament. JSON
election Key dates and jurisdiction metadata, each with a source. JSON
coverage Per-party district coverage, with the counting caveat attached. JSON
summary Headline counts, regenerated on every build. JSON
polls Sourced statewide primary-vote polls (eligible and excluded). JSON CSV
poll-average Weighted primary-vote average with uncertainty bands (not a forecast). JSON
issues Policy issue taxonomy and jurisdiction notes for the comparison matrix. JSON
coalitions Reversible display relationships for combined Coalition matrix columns; registered parties remain separate. JSON
policies Sourced party policy claims by issue (sparse ledger; no ratings). JSON CSV

Using the data

Licence

Data is licensed CC BY 4.0. You may reuse and adapt it, including commercially, provided you attribute it.

Site and tooling code are MIT-licensed.

How to cite

Australian Election Tracker (OZE), Victorian state election 2026 candidate ledger, electiontracker.au, accessed 2 Aug 2026.

Read the caveats first

coverage.json carries a caveat field explaining exactly what the coverage counts do and do not include. Please carry it through into any reuse.

How coverage is counted

Source of truth

These files are build artefacts. The authoritative records are the YAML files in the public repository, where every change has a commit, an author and a date.

Schema notes