This project is under early active development. The API and schema may have breaking changes several times without prior notice before the first official public release. Read changelog
Changelog
View this page as MarkdownThis page lists every change that affects how a client uses the API: the GraphQL schema, query limits, endpoints, visibility rules, and MCP tools.
When a client-visible field is renamed or removed, the old field is kept for a while with the GraphQL @deprecated directive wherever possible, and its removal appears as a later entry on this page. Relationship fields are the exception: they cannot coexist with their replacement, so renaming one is listed under Breaking right away.
2026-11-09
Section titled “2026-11-09”Breaking
BillMergeEvent.main_bill_idcan no longer be set bycreateBillMergeEventsorupdateBillMergeEvents. Link the main bill withBill.main_bill_merge_eventsincreateBillsorupdateBillsinstead
Added
Vote.voter_affiliations: [Organization!]!andOrganization.member_votes: [Vote!]!, linking a vote to the party or Senate term the voter belonged to at the time.Vote.voter_affiliation_raw, replacingVote.voter_partyBillMergeEvent.main_bill: BillandBill.main_bill_merge_events: [BillMergeEvent!]!, linking a merge event to its main bill, replacingBillMergeEvent.main_bill_id
Deprecated
Vote.voter_party, useVote.voter_affiliation_rawinsteadBillMergeEvent.main_bill_id, useBillMergeEvent.main_bill { id }instead
Fixed
- Selecting
idorcreated_atfromedges.propertiesno longer fails withCannot return null for non-nullable field Relation.id. Relationships missing these values now have them, withcreated_atapproximated from the source node, and new relationships get them automatically
2026-10-29
Section titled “2026-10-29”Added
created_atandupdated_atare marked as internal fields, not dates of real-world events, in the schema, MCP server instructions and llms.txt, so AI agents don’t use them in place of a node’s own date fields such asBill.proposal_date- Thai support for llms.txt (
/llms-th.txtand/llms-full-th.txt), the MCPget-docstool and thepolitigraph://docs/thresource, with instructions for AI agents to read the Thai documentation when the user asks in Thai Person.id,Bill.id,VoteEvent.idandOrganization.iddescriptions give the matching Parliament Watch page URL, and the MCP server instructions and llms.txt tell AI agents to citelinksand those pages as references
2026-10-21
Section titled “2026-10-21”Breaking
Bill.lis_idis replaced byBill.lis_ids, and thecreateBillsmutation now requireslis_idsinstead oflis_id
Added
Bill.lis_ids, because one bill can have several IDs on the lis.parliament website, for example when it spans several parliamentary terms
2026-09-29
Section titled “2026-09-29”Added
timestampsquery, returning UTC timestamps of data freshness:lastNodeUpdatedAt, the most recent data changelastVoteEventScrapedAt, the last successful automated scrape of votes (VoteEventandVote)lastBillScrapedAt, the last successful automated scrape of bills and their events
- MCP server instructions point agents to the
timestampsquery to check how current the data is
Deprecated
lastUpdatedAt, usetimestamps { lastNodeUpdatedAt }instead
2026-09-24
Section titled “2026-09-24”Breaking
Organization.motionsrenamed toOrganization.considered_motions. Its description wrongly said “proposed in the name of the organization”, while the field has always meant “considered in the organization” — useOrganization.created_motionsfor the former/graphqlnow responds with HTTP400instead of200when a variable does not match its declared type. Theerrorsbody is unchanged
Added
Organization.created_motions, motions proposed in the name of the organization (theCREATED_BYback-reference, matchingPerson.created_motions)Organization.considered_motions, motions considered in the organization/graphqlaccepts the optionalapollographql-client-nameandapollographql-client-versionheaders, so server-side clients can identify their application.get-docsMCP tool, returning the documentation index (/llms.txt) or a single documentation page as markdown, so agents can read how the data is modeled and example queries
Deprecated
VoteEvent.bills, useVoteEvent.bill_vote_events.billsinsteadBill.requirementandMotion.requirement, never populated. Will be removedBillVoteEvent.pass_condition, never populated. UseBillVoteEvent.vote_events.pass_conditioninstead. Will be removed
2026-09-04
Section titled “2026-09-04”Added
/mcpendpoint with tools to run a query, read the schema, and list types/llms.txt,/llms-full.txt, and a.mdversion of every documentation page
2026-08-05
Section titled “2026-08-05”Added
lastUpdatedAtquery, returning the UTC timestamp of the most recent data change
2026-03-11
Section titled “2026-03-11”Breaking
PersonandVotequeries now return at most 1,000 nodes per request. Uselimitandoffsetto page through larger result sets
2026-02-24
Section titled “2026-02-24”Breaking
Bill.bill_eventsrenamed toBill.eventsVote.voter_namerenamed toVote.voter_name_raw- Union
MotionProposerrenamed toMotionCreator Bill.proposersandBill.co_proposersrenamed toBill.creatorsandBill.co_creatorsPerson.proposed_motionsrenamed toPerson.created_motions, withPerson.co_created_motionsadded alongside it
Added
Bill.creator_typeand theBillCreatorTypeenum
2025-12-16
Section titled “2025-12-16”Breaking
Bill.bill_eventsnarrowed fromEventto the newBillEventunion.DraftVoteEventbecameBillVoteEventandBillEnforceEventbecameBillEnactEventBillStatus.ENFORCEDremoved, it duplicatedBillStatus.ENACTED
Added
Person.death_date

