Cite this page

Granite Record indexes the General Court’s record; it is not that record. Where a citation allows only one source, cite the General Court — every page here links to what it is drawn from. The date below is the day this page’s record last changed.

MLA
“The data API.” Granite Record, https://graniterecord.org/api. Accessed 20 Nov. 2026.
APA
Granite Record. (n.d.). The data API. Retrieved November 20, 2026, from https://graniterecord.org/api
Chicago
Granite Record. “The data API.” Accessed November 20, 2026. https://graniterecord.org/api.
BibTeX
@misc{api, title = {The data API}, howpublished = {Granite Record}, url = {https://graniterecord.org/api}, note = {Accessed 20 Nov. 2026} }

The Data API

The whole record behind this site, as files a program can read: every bill of every term with its full history, every roll call and every member’s vote, the committee reports and their reasoning, and one list joining every number the General Court uses for a person. No key, no account and no limit to ask about: they are plain files, rebuilt every night.

A beta until February 1, 2027. Until then a file or a field may still change, and every change is announced in manifest.json a week before it is made. From then on, changes only add things.

On this page

The Files

Everything is under /data/, beside the spreadsheets on the data page, and data/manifest.json lists every file with its address, size and checksum. Start there: one request says what is here and how much. The bill files are compressed with gzip and the database with xz. Python opens and reads both with nothing to install; R unpacks both, and reads the database with its RSQLite package. On the command line, gzip and xz are on most Linux systems; a Mac has gzip and needs xz installed.

FileWhat it holdsCountSizeDownload
manifest.json

Every file here, with its address, rows, size, checksum and the night it was built.

62 files—Open manifest.json
schema.json

What every column and field of every file means, its type, and what it joins to.

More about schema.json

A Frictionless Data Package, a published standard that pandas, R and the frictionless tools read directly. Each field says whether it is stable, beta, or drawn for the page and promised nothing.

—0.5 MBOpen schema.json
granite-record.sqlite.xz

Every table on the data page in one SQLite database, with the committee reports and their reasoning, interim study statements, testimony counts and every noticed meeting.

More about granite-record.sqlite.xz

138.2 MB once opened. Tables: bills (33,717), rollcalls (9,565), votes (2,303,047), vote_values (7), sponsors (129,486), legislators (406), proceedings (105,476), people (2,187), person_numbers (5,761), committee_reports (33,097), docket_reports (31,538), interim_study (1,601), testimony (3,054), meetings (166,539). Testimony is counts only, never a name. A vote is its roll call, its member, their person and a value, so each roll call and each member is stored once.

votes.rollcall joins rollcalls.id; votes.person and person_numbers.person join people.person; term + bill joins bills.

14 tables15.0 MBDownload granite-record.sqlite.xz
people.json

One entry for each of the 2,157 people with a recorded vote since 1999, with every number the General Court has used for them, and 30 for a number that proved to be one of theirs (replaced_by).

More about people.json

The General Court gives a member a new employee number and a new person id when they move between the House and the Senate. This file joins every one of those, and the ids this site’s other files use, to one person. people.csv is the same, one row a number.

2,157 people0.8 MBDownload people.json
Bills by Termbills-<term>.jsonl.gz

Every bill’s full record, one line a bill: its docket, hearings, votes, sponsors, committee reports, and the text of its latest printing where the record has it. One file a term, 19 in all, from 1989–1990 to 2025–2026.

More about bills-<term>.jsonl.gz

Each line is one JSON object, keyed "key": "2025-2026/HB1442": the record the bill’s own page is drawn from. It leaves out the Senate’s hearing reports, which name members of the public, and YouTube’s own titles and links.

33,717 bills143.5 MBEach term below
Bill Texts by Termbill-texts-<term>.jsonl.gz

The text of every bill, one line a bill: each version its Bill Text tab shows, with its name and the day the General Court dated it. One file a term, 19 in all.

More about bill-texts-<term>.jsonl.gz

Each line is keyed as the bill files are, "key": "2025-2026/HB1442". A bill this site holds no text for says so, "text_on_file": false; no text is made up.

33,717 bills47.8 MBEach term below
bills.csv and the rest

The spreadsheets, as on the data page, with every date written YYYY-MM-DD and a person column in the sponsor and legislator tables.

2,581,697 rows241.4 MBSee them bills.csv and the rest

One Record at a Time

Each bill and roll call of the current term, each member, each bill request and each chapter of the laws also has a small file of its own under /api/, for a program that wants one record rather than a whole term. api/index.json lists them, with every field each file holds. They hold only the fields schema.json marks stable, so a change to how a page is drawn does not change them. 7,930 files, 182.7 MB in all.

/api/bills/<term>/index.json
Every bill of one term, a row each: its number, title, prime sponsor, committees, topic, status and how far it got. One file for each of the 19 terms.
/api/bills/2025-2026/<bill>.json
A bill of the current term with its whole record: its docket, sponsors, roll calls, committee reports and amendments, and the text of every version its Bill Text tab shows, each with its name and date. 2,243 files. One is HB1.json. A bill of an earlier term is a row in its term’s file, its whole record is in bills-<term>.jsonl.gz, and its text in bill-texts-<term>.jsonl.gz.
/api/rollcalls/<term>.json
Every roll call of one term: the question, the tally and whether it carried. Roll calls begin in 1999, so there are 14 files.
/api/rollcalls/2025-2026/<roll call>.json
A roll call of the current term, with how each member voted. 799 files. One is 2025-H-1.json.
/api/members/<person>.json
Each of the 2,187 people with a recorded vote since 1999, by their person number: the General Court’s numbers for them, their terms and chambers, their seat if they sit now, and every bill they sponsored. One is 27.json. /api/members/index.json lists them.
/api/requests/2027/<number>.json
Each of the 856 bill requests for 2027: its title, sponsors and where it stands, and the bill it became once it is one. One is 0001.json. /api/requests/2027/index.json lists them.
/api/laws/<chapter>.json
Each of the 1,800 chapters of the laws: each section’s heading and text as its page here shows them, the session laws that changed it, the bill each law was, and the day it took effect. The file says the day the text was taken from the General Court’s database, and links the official text. One is 1.json. /api/laws/index.json lists the chapters.

Getting Started

Every bill of the current term: download its file, then read it a line at a time, here in Python with nothing to install.

curl -O https://graniterecord.org/data/bills-2025-2026.jsonl.gz
import gzip, json
with gzip.open("bills-2025-2026.jsonl.gz") as lines:
    for line in lines:
        bill = json.loads(line)
        print(bill["key"], bill["title"])

Or the whole database, in the sqlite3 program:

curl -O https://graniterecord.org/data/granite-record.sqlite.xz
xz -d granite-record.sqlite.xz
sqlite3 granite-record.sqlite "SELECT term, COUNT(*) FROM bills GROUP BY term"

A page on another site may read every file the manifest lists from a reader’s browser too: each is served to any origin.

Keys and Joins

A bill is its term and its number. HB 100 names a different bill in every term, so every file writes a bill as 2025-2026/HB1442, or as a term and a bill side by side.

A person is a person. The General Court numbers a member in two ways, an employee number and a person id, and this site’s files use both; one person can carry several of each. people.json joins them to one person, which does not change when a member moves between the House and the Senate. It is one of the General Court’s own numbers for them: their earliest person id, or their earliest employee number where the record gives no person id.

When two entries prove to be one person, or one is two

A person is never given to anyone else. If two entries prove to be one person, the one that goes stays in the file with a replaced_by line, so a program that stored it can still find them. If one proves to be two people, it keeps its number and the other gets a new one, marked split_from. A number not yet issued is marked provisional and may still change.

A blank field is usually an answer

The record leaves it empty, the document that would fill it has not been collected, or this site does not read it yet. The data page’s coverage table counts how far each column reaches in each term.

What Changed Tonight

/changes/<date>.json is what each night’s build found new, kept for the last eight nights: the hearings, votes and actions each bill, member, committee and topic gained. With the checksums in manifest.json, another site can fetch only the files that moved.

/api/changes/<date>.json says, for the same eight nights, which records under /api/ changed: each bill, of any term, roll call, member, chapter of the laws and bill request whose fields marked stable or whose text changed that night, and any that are gone, so a program fetches only those. A change to how a page is drawn is not listed.

Today’s Votes

On a day the House or the Senate sits, /api/live/votes/<date> holds the roll calls recorded so far that day. They are provisional: the nightly files above take the day in the next morning, from the General Court’s own record.

What is live on the General Court’s video streams is not part of the API. Each bill’s page links its recording.

What It Covers

The General Court publishes its record as a database. Every table of it this site reads, and where each lands here, is in manifest.json under sources, and below.

Docket
each bill's events, stages and chapter; proceedings; docket_reports; bills.csv status and chapter
Legislation
bills.csv; each bill's title, committees and subject
Sponsors
sponsors.csv; each bill's sponsors
Legislators
legislators.csv; people.json; the names in the vote files
RollCallSummary
rollcalls.csv; each bill's rollcalls
RollCallHistory
votes-<term>.csv; the database's votes
CandH_Reports
the Senate's committee reports in committee_reports and each bill's reports
LegislationText
each bill's billtext, the current printing
NH_RSA
each bill's rsa; the /laws pages, not a /data file
houseRemoteTestify
testimony: counts only. Names, towns and written testimony are never collected
Committees, CommitteeMembers
legislators.csv committees; the committee pages, not a /data file
StatStudDetails, StatStudMembers, StatStudMeetings
the statutory and study committee pages, not a /data file
HouseDistricts, senateDistricts, County, Towns
legislators.csv district and county; the town pages, not a /data file
Subject, GeneralStatusCodes, BodyStatusCodes
as words in bills.csv topic and status, not as code tables
PastLegislation, PastSponsors, PastDocket, PastLegislationText
the same places as their current-term tables, for 1989 to 2024
PastCommitteeReports
not published itself: it corrects misprinted House reports in committee_reports
PastAmendments
each bill's related
DocumentVersion
not published: it only orders and names the printings
VHearings
not published: read by nothing; hearings come from the Docket and the calendars
hearingType, committeeType, DistrictPast
not published: dumped and read by nothing
The House and Senate calendars (not the database)
the House committee reports and their reasoning, interim study statements, and meetings

Versions and Stability

The format is numbered: 1 now, in manifest.json under api, in schema.json and in people.json. Until February 1, 2027 the API is a beta, and a field may be renamed or removed; each such change is listed here and in manifest.json a week before it is made. From February 1, changes only add: a new file, a new field, a new column at the end. A change that cannot be made by adding becomes a new file beside the old one, and both are published for a year. schema.json marks what the promise covers.

No change is announced now.

Using It

The record is the State of New Hampshire’s and is public, and so are the numbers it gives people and bills. What this site adds — the keys and joins it makes and the corrections made here by hand — is dedicated to the public domain under CC0: use it for anything, with no need to ask. The plain-English histories are this site’s writing, offered under the MIT License like the code that builds all of it. A link back to graniterecord.org helps somebody check your working.

Found something that looks wrong, or a shape that is awkward to use? Each bill’s page has a Report a problem button, or write to [email protected].