publicdata.au publicdata.au on GitHub

Historic marriage index, ACT

live
Publisher Access Canberra, City and Environment DirectorateUpdated yearlyLicence CC BY 4.0Latest 2026-09-27Rows 2,453Fields 6

The historic marriage index Access Canberra keeps for marriages registered in the ACT more than 75 years ago. Each row carries the registration number, the surname and given names of each of the two parties and the date of the marriage.

Also called: ACT marriage records index, Canberra historic marriages register, ACT BDM historic marriage index.

Before you use it
What is in each row?
One marriage registered in the ACT, with the registration number, the surname and given names of each party and the date of the marriage.
Why are recent marriages missing?
The publisher's index holds only marriages registered in the ACT more than 75 years ago. Later marriages are added as they pass that age.
Is this a marriage certificate?
No. It is an index with limited details. A certificate is ordered from the ACT Registry of Births, Deaths and Marriages.
2,453marriages
1930 to 1950years drawn
6fields
9formats
1version
0501001502002501930: 391931: 411932: 5019321933: 601934: 651935: 7719351936: 841937: 641938: 9119381939: 951940: 1271941: 12919411942: 1251943: 1021944: 12219441945: 1181946: 1651947: 20419471948: 1661949: 2151950: 2441950
Marriages per year, 1930 to 1950. 1951 is not drawn because the rows run to 26 March 1951. The figure is a count of rows from version 2026-09-27, worked out in the build. Nothing else is added.

Made for agents

Connect your AI agent

Any agent that connects to publicdata.au/mcp can find this dataset, read its 6 fields, count and filter across all 2,453 rows and diff its versions. Every answer names the version and carries Access Canberra's attribution. No key.

Then ask it: What does Historic marriage index, ACT hold, and what changed in the newest version?

claude mcp add --transport http publicdata https://publicdata.au/mcp

One command. No key, no account, no sign-up.

Download it as Excel, CSV, JSON and 6 more formats

Pick a format and a version. Excel is picked first because it opens in the tools most offices have. The URL is yours to keep. A dated version keeps its content.

Format
"Latest" redirects to the newest version and will change when the publisher releases again. A dated version keeps its content.
https://publicdata.au/d/act-historic-marriage-index/latest/data.xlsx
Download this file

One workbook with a records sheet of 2,453 typed rows, a fields sheet and a publicdata sheet with the provenance. Dates are real Excel dates. Opens in Excel, Numbers, LibreOffice and Sheets.

In your own tools

Use it in Excel, R, Python and more

Excel and Power BI read the CSV from its address and refresh from it. The R and Python packages take any dataset on this site by its slug, so a new dataset needs no new release. The DuckDB file attaches read-only over HTTPS, and a query reads only the blocks it touches.

The dated URL in the code never changes. https://publicdata.au/d/act-historic-marriage-index/latest/ redirects to the newest version.

https://publicdata.au/d/act-historic-marriage-index/latest/data.csv

In Excel choose Data, then From Web, and paste this address. Excel keeps it, so Refresh All reads the newest version. A sheet holds about a million rows; past that, load the query to the Data Model.

What is in it

Column names are made snake_case and the publisher's original header is kept beside each one. Blank cells are null. Nothing is added, removed, ranked or summarised. Cells were typed and headers were made snake_case. The publisher's header is kept beside every field in schema.json. Rows were left alone.

FieldTypePublisher's headerNote
registration_numberstringRegistration number
party_1_surnamestringParty 1 surname
party_1_given_namesstringParty 1 given names
party_2_surnamestringParty 2 surname
party_2_given_namesstringParty 2 given names
date_of_marriagedateDate of Marriage

Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is registration_number.

A sample of 10 rows

From the latest version, newest first by date of marriage, then in the publisher's order, with every field. A blank cell is shown as null.

registration_numberparty_1_surnameparty_1_given_namesparty_2_surnameparty_2_given_namesdate_of_marriage
80045367LISTKIEWICZKAROLINAKNAPJAN1951-03-26
30010489LOVEJacqueline MaryBURRIDGEGordon Joseph1951-03-24
80036967KEASTFRANCIS LAWRENCEHEATHCOTEIRENE DORIS1951-03-24
80041228NIELSENPETER GEORGEBIRKETTJEAN KATHLEEN1951-03-24
80041280LOVEJACQUELINE MARYBURRIDGEGORDON JOSEPH1951-03-24
80062644PECKZEN EYCK WESTBROOKEATHERELAINE MARGARET1951-03-24
80049712MURPHYJOAN MARYBROWNRONALD EDWARD1951-03-24
80058311QUIGGEDWARD JAMESKEELEYCORAL LORRAINE1951-03-24
80045422WALGREMALLEPARVEYALEXANDER1951-03-24
80054199WATSONLAURAROCHECHRISTOPHER STEPHEN1951-03-24
The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/act-historic-marriage-index/latest/data.json
{
  "registration_number": "80045367",
  "party_1_surname": "LISTKIEWICZ",
  "party_1_given_names": "KAROLINA",
  "party_2_surname": "KNAP",
  "party_2_given_names": "JAN",
  "date_of_marriage": "1951-03-26"
}

Query it without downloading

The query API returns only the rows you ask for, as JSON, NDJSON or CSV, from the same typed rows as the files. It needs no key. Build a query here and run it, then copy the URL or the code into your own work.

Try rows or aggregate for this dataset. The query builder needs JavaScript.

How filters work

Each filter is field=operator.value in the query string, and every filter must match. A number or date field compares as a number or date, and a text field compares as text. Values are case-sensitive, except that like and ilike ignore case in the ASCII letters A to Z. Prefix not. to negate a filter, as not.eq.value.

OperatorWhat it matches
eq.valueEqual to the value.
neq.valueNot equal to the value. A blank cell does not match.
gt.valueGreater than the value.
gte.valueGreater than or equal to the value.
lt.valueLess than the value.
lte.valueLess than or equal to the value.
like.*text*Matches a pattern where * stands for any run of characters, ignoring case in the ASCII letters A to Z.
ilike.*text*The same as like. Both ignore case in ASCII letters only, so É and é differ.
in.(a,b,c)Equal to any value in the list. A value cannot contain a comma.
is.nullBlank in the source, or suppressed by the publisher.
ParameterWhat it does
selectFields to return, comma-separated. Every field when absent.
orderfield.asc or field.desc, comma-separated. When absent, rows come in the order of the file they are read from. For the newest versions that is the version's own data.parquet, which keeps the publisher's order unless the dataset sorted it. Any other version is read from the Parquet file the answer names in file, and when that file is sorted the answer names its sort in order, which ties follow too.
limitRows per page, 1 to 10,000. 100 when absent.
offsetRows to skip. The next URL in each answer sets it for you.
groupOn aggregate, fields to group by, comma-separated.
metricOn aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent.
formatjson, ndjson or csv. JSON carries the provenance header, and the others carry it in response headers.

Without a version the API answers from the newest version, and that answer changes when the publisher releases again. Put versions/<date>/ before rows or aggregate for an answer from that version alone. Every version with a table can be queried, and /api/v1/datasets/<slug>/versions lists them. A query on a version the database does not hold is read from its Parquet file, and one that would read too much of it is refused with DuckDB SQL that answers it from the file. The 1 newest version is loaded; versions lists them.

The API allows 60 requests in 10 seconds from one address. Above that it answers 429 for 10 seconds with a Retry-After header, a RateLimit-Policy header and a JSON body that gives the limit. Every API answer carries the same RateLimit-Policy. A client should wait the Retry-After seconds, or read the files, which have no limit. openapi.json describes this dataset's query paths for client generators and agents.

https://publicdata.au/mcp is a remote MCP server over Streamable HTTP with the same tools, defined in the same place, so a tool added to the pages is added here too. It needs no key and no account. Its row tools and the query API answer every version through one query path, so a tool's answer and the query URL it cites give the same rows. A query that would read too much of a file is refused with DuckDB SQL that answers it from the file. It also has search and fetch, the two tools ChatGPT's deep research and company knowledge call by name, which run search_datasets and read a dataset's record in the shapes those features expect. The row tools are held to the query API's limit of 60 queries in 10 seconds from one address, and each call is two queries because it also counts the matching rows. Add it to Claude Code with claude mcp add --transport http publicdata https://publicdata.au/mcp, add the URL in Claude as a custom connector, connect the publicdata.au plugin in ChatGPT, or give it to any client that connects to remote MCP servers. Each dataset with a table is also a resource at https://publicdata.au/d/<slug>/fields.json, which lists its fields with their types, the publisher's descriptions, their ranges and the values they hold, so an agent can read a dataset's shape before it writes a query.

What changed

One version for every release the publisher has made since this site started following the dataset. The date is the day the file changed on the portal.

  • 2026-09-27
    2,453 rows6 fieldsutf-8-sig339cc6869fdf

versions.json · changes.json · history.tar.zst (80 KB, every version's Parquet and manifest)

Questions

How do I download Historic marriage index as a CSV file?

Open https://publicdata.au/d/act-historic-marriage-index/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/act-historic-marriage-index/v/2026-09-27/data.csv today. The same path serves Excel, JSON, Parquet, SQLite, DuckDB, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.

Can I open Historic marriage index in Excel?

Yes. https://publicdata.au/d/act-historic-marriage-index/v/2026-09-27/data.xlsx is a workbook with the 2,453 rows on a records sheet, the field list on a second sheet and the provenance on a third. The CSV also opens in Excel. https://publicdata.au/d/act-historic-marriage-index/v/2026-09-27/data.csv.gz is the CSV at about a tenth of the size.

What years does Historic marriage index cover?

The current version covers 1930 to 1950. Each release from Access Canberra becomes a new dated version here, and earlier versions stay online.

How often is Historic marriage index updated?

Access Canberra releases it yearly. This site checks the portal every week and adds a dated version when the file changes.

Can I use Historic marriage index commercially?

Yes. CC BY 4.0 allows commercial use, redistribution and derived works as long as the attribution is kept. The attribution string is in this page's side column and inside every file.

Is this the official source for Historic marriage index?

No. The publisher is Access Canberra, City and Environment Directorate, and its page is https://www.data.act.gov.au/d/uzaz-dbkr. National Digital converted the publisher's file to other formats. It renamed and typed the columns and kept only those the schema lists. National Digital made these changes, and the publisher is not responsible for them. The original sits beside every version as source.csv with its SHA-256, so the two can be compared.

What this site did to the data. Cells were typed, headers were renamed and the encoding was made UTF-8. Rows were left alone. The publisher's file sits beside every version as source.csv so the change can be checked.

Attribution and citation

The licence requires the publisher's attribution. We ask that you also name publicdata.au and link to the version you used.

Access Canberra, ACT Government, Historic marriage index, https://www.data.act.gov.au/d/uzaz-dbkr, accessed 3 October 2026, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/act-historic-marriage-index/v/2026-09-27/

The attribution alone is inside every file. Harvard is the author-date form a report or a brief asks for. Paste the HTML on a web page so the links carry.

Licence record

Access Canberra, City and Environment Directorate states the licence, CC BY 4.0, on its own page, which was read and recorded here on 1 October 2026.

Every fetch reads the licence again and stops when it has changed. The fetch that made version 2026-09-27 read it from www.data.act.gov.au on 3 October 2026.

Also published on
  • Hugging Faceload_dataset("National-Digital/act-historic-marriage-index")
  • Kagglewith a starter notebook
  • ZenodoDOI 10.5281/zenodo.23123450

Each copy carries the same attribution and links back to this page.

For agents and tools

This page carries a schema.org Dataset record and is listed in /.well-known/ard.json and /catalog.json.

Source

Access Canberra, City and Environment Directorate publishes this table on www.data.act.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.

Fetched 3 October 2026. Source SHA-256 339cc6869fdf9e16…

Improve this dataset

This page is built from register/act-historic-marriage-index.yaml on GitHub. Anyone can propose a fix to it, such as a clearer description or a field the publisher renamed, as a pull request.

Report a file that differs from the publisher's · How to contribute