canonical: https://jentic.com/apis/parliament.uk/parliament-uk-lords-votes

# UK Parliament Lords Votes API

UK Parliament Lords Votes API provides access to House of Lords division voting records including Content/Not Content vote outcomes, member voting records, teller information, remote voting details, and party breakdowns. The API enables searching divisions by date range, member, division number, or keywords with filters for vote counts and majority size, retrieving individual division details with full member vote lists and teller counts, querying member voting history across divisions, obtaining divisions grouped by party vote counts, and counting total results for pagination. Public and unauthenticated access.

## For AI agents

Query House of Lords division votes, member voting records, and party breakdowns for legislative and political analysis.

## Scope

Does not include Commons votes (use Commons Votes API), Bill metadata (use Bills API), or member biographies - use only for Lords division voting records.

## Capabilities

- Search divisions by date range, member ID, division number, search term, total votes cast, or majority size
- Retrieve division details including title, date, Content/Not Content counts, tellers, member lists, and remote voting periods
- Query voting records for a specific member (Peer) across divisions with filters
- Get divisions grouped by party showing vote counts per party for Content and Not Content
- Count total divisions matching search criteria for pagination
- Filter by whether a member was a teller or includes remote voting sessions
- Access authoritative vote counts (teller-based when tellers present, member-based otherwise)

## Use cases

### Peer Voting Record Analysis

Political researchers and transparency organizations track how Peers vote. GET `/data/Divisions/membervoting`?MemberId={id} returns all divisions a Peer participated in with their vote (Content/Not Content) and teller status. Filter by date range or search term. Useful for accountability and understanding Lords influence on legislation.

Example prompt: GET `/data/Divisions/membervoting`?MemberId={memberId}&StartDate={YYYY-MM-DD} to retrieve a Peer's votes in a date range.

### Lords Division Outcome Tracking

News organizations and civic tech projects track Lords division outcomes. GET `/data/Divisions/search` returns divisions matching criteria including filters for TotalVotesCast and Majority thresholds. GET `/data/Divisions/{divisionId}` retrieves full details including Contents, NotContents, tellers, and whether the division was government win. Combine with /groupedbyparty for party discipline analysis.

Example prompt: GET `/data/Divisions/search`?SearchTerm={keyword}&StartDate={date} to find divisions, then GET `/data/Divisions/{divisionId}` for full vote breakdown including teller and member counts.

### Party Whip Analysis in the Lords

Analysts study party discipline and crossbench voting by comparing party-grouped votes. GET `/data/Divisions/groupedbyparty` returns divisions with contentCount and notContentCount aggregated by party. Identify rebellions and crossbench influence by comparing individual member votes against party majority positions.

Example prompt: GET `/data/Divisions/groupedbyparty`?SearchTerm={keyword} to see party-level vote counts, then cross-reference with individual member votes to spot rebels and crossbench patterns.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/data/Divisions/search` | Search divisions by filters including vote counts and majority |
| GET | `/data/Divisions/{divisionId}` | Get division details with full member votes and teller information |
| GET | `/data/Divisions/membervoting` | Get voting records for a member (Peer) |
| GET | `/data/Divisions/groupedbyparty` | Get divisions with party vote breakdowns |

## Key resources

- **Divisions** — Voting events in the House of Lords with Content/Not Content counts, member lists, tellers, and outcomes
- **Member Voting Records** — Individual Peer votes (Content/Not Content) and teller roles across divisions

## Why Jentic

- **Setup:** Wiring the UK Parliament Lords Votes API by hand means pointing a client at its public host, shaping the division search and member-voting routes, and handling pagination yourself. Through Jentic you install once, import the Lords Votes API from the API Directory, and your agent calls it with no credential to manage.
- **Permission scoping:** The Lords Votes API puts the division id in the URL path (`/data/Divisions/{divisionId}`), so a rule can pin your agent to one division or to the read-only vote lookups. Since this public API only reads Lords division records, the agent stays limited to retrieval.
- **Credential handling:** The Lords Votes API is public, so there is no credential to store; Jentic shapes the request and parses the response at execution time. No token ever enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'a peer voting record' or 'Lords division votes', and Jentic returns the matching Lords Votes operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **UK Parliament Bills API** — Bills API tracks Bill lifecycle while Lords Votes shows how Peers voted on those Bills and amendments.
- **Commons Votes API** — Commons Votes covers House of Commons divisions while Lords Votes covers House of Lords divisions.

## FAQ

### Does the Lords Votes API require authentication?

No. The API is public and open for research and civic use without authentication or API keys.

### Can I track how a specific Peer voted across all divisions?

Yes. GET `/data/Divisions/membervoting`?MemberId={id} returns all divisions the Peer participated in with their vote. Filter by date range or search term.

### What is the difference between authoritative counts and member counts?

Authoritative counts are the official counts - teller counts when tellers are present, or member counts when there are no tellers. The API returns both tellerContentCount/tellerNotContentCount and memberContentCount/memberNotContentCount for transparency.

### Can I limit what my agent is allowed to do with the Lords Votes API?

Yes. Because you self-host Jentic One, your own rules decide which Lords Votes operations the agent may call, and this API only reads House of Lords division records, so an agent stays limited to retrieval. Since the division id sits in the URL path at `/data/Divisions/{divisionId}`, you can pin the agent to a single division or to specific read routes such as `/data/Divisions/search`, `/data/Divisions/membervoting`, and `/data/Divisions/groupedbyparty.` The API is public with no credential, so the agent can never send a token or reach any write action.