---
title: "List Related Bills"
method: GET
path: "/api/v1/bills/{bill_id}/related"
tags: ["bills"]
---

# List Related Bills

`GET /api/v1/bills/{bill_id}/related`

## Request

- Base URL: `https://api.billcommons.org`
- URL: `https://api.billcommons.org/api/v1/bills/{bill_id}/related`
- Auth: none declared

Companion, prior-session and superseded-bill cross-references.

These have been collected all along (~100k rows, of which ~47k are
`prior-session`) and were never exposed -- the single most-requested thing
for multi-year policy tracking, because a bill that dies and returns next
session under a new number is otherwise untrackable.

Upstream gives us only the related bill's IDENTIFIER, so the target is
resolved here, scoped to the same jurisdiction. Same-session companions
usually resolve; prior-session links usually do not, because that session
is outside this corpus. Unresolved links still return their identifier
rather than being dropped.

## Path parameters

- `bill_id` string, uuid, required

## Response `200`

Successful Response

- RelatedBillOut[]
  - `id` string, uuid, required
  - `relation_type` string, nullable
  - `related_identifier` string, nullable
  - `related_bill_id` string, uuid, nullable

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/billcommons/apis/bill-commons-api.md) · [All operations](https://skmtc.dev/billcommons/apis/bill-commons-api/llms.txt) · [OpenAPI document](https://skmtc.dev/billcommons/apis/bill-commons-api/revisions/bfb8cd50a317?raw)