---
title: "Committee documents (reports + legislation)"
method: GET
path: "/api/v1/congress/committees/{chamber}/{system_code}/documents"
tags: ["Public Finance & Government"]
---

# Committee documents (reports + legislation)

`GET /api/v1/congress/committees/{chamber}/{system_code}/documents`

Documents produced by a committee, as a structured catalog (doc_type, citation, title, congress, chamber, doc_url). LEAN build: the committee-scoped `report` and `legislation` legs are served; the chamber-wide `hearing` / `meeting` / `publication` legs are omitted (a faithful build is a hundreds-of-calls fan-out that does not fit the single-worker model) and DISCLOSED via `partial` + `skipped` - never a silent cap (a served leg that hits a per-request row cap is named in `truncated` and forces `partial`). A SUBCOMMITTEE request is served from its parent committee's documents (the upstream endpoints are parent-scoped); the parent actually queried is returned as `served_system_code`. The `report` title is the report citation. Example: /congress/committees/senate/ssas00/documents

## Path parameters

- `chamber` string, required — Chamber: house, senate, or joint.
- `system_code` string, required — Committee system code (e.g. ssas00, hsju00).

## Query parameters

- `doc_type` string — Document type: all, report, meeting, publication, legislation. Only report/legislation are served in the lean build.
- `congress` integer — Congress number (e.g. 119). Defaults to the current Congress.
- `limit` integer — Max rows to return.
- `offset` integer — Pagination offset.

## Response `200`

Committee document catalog with partial/skipped/truncated disclosure.

- EnvelopeCongressCommitteesChamberSystemCodeDocumentsData
  - `data` CongressCommitteesChamberSystemCodeDocumentsData, required
    - `chamber` string, nullable
    - `system_code` string, nullable
    - `served_system_code` string, nullable
    - `congress` union
      - integer
      - number
    - `doc_type` string, nullable
    - `partial` boolean, nullable
    - `skipped` string[], nullable
    - `truncated` string[], nullable
    - `total` union
      - integer
      - number
    - `documents` Document[], nullable
      - `doc_type` string, nullable
      - `citation` string, nullable
      - `title` string, nullable
      - `congress` union
        - integer
        - number
      - `chamber` string, nullable
      - `doc_url` string, nullable
  - `meta` SugraMeta, required — Metadata attached to every /api/v1/* response envelope.
    - `endpoint` string, required — Requested endpoint path.
    - `data_time` string, required — ISO 8601 UTC timestamp of the source data, not of the request.
    - `response_time` string, required — ISO 8601 UTC timestamp when this response was produced.
    - `provider` string, required — API name and version.
    - `source` string, nullable — Identifier of the primary upstream source used for this response.
    - `attribution` string, nullable — Human-readable attribution mandated by an upstream source (e.g. a securities regulator or self-regulatory organization). Present only on responses whose source requires the owner and source to be clearly identified. Do not remove or alter it when using the response.
    - `fallback_used` boolean, nullable — True when the primary source failed and a fallback produced the data.
    - `fallback_chain` string[], nullable — Ordered list of sources attempted, in the order they were tried.
    - `cached` boolean, nullable — True when this response was served from the internal cache.
    - `stale` boolean, nullable — True when the cached response was returned after the upstream rate-limited or errored. Clients can use this to detect degraded data.

## Other responses

- `401` — Missing or invalid `x-api-key` header. JSON body with a stable `code` distinguishing `missing_api_key` (no header sent) from `invalid_api_key` (header sent, key not accepted); any other 401 source carries the generic `unauthorized` with its detail as `reason`. Plus `hint`. `plan` is always null on 401 - an unauthenticated request has no plan; quota exhaustion is 429, not 401.
- `422` — Validation Error
- `429` — Daily rate limit exceeded. Check `X-RateLimit-Reset` for the next window.
- `503` — Upstream source is temporarily unavailable. Retry after a short delay.

## Changes

- **2026-08-28** `560e8847c7b3` — 2 breaking
  - response property `data/skipped/anyOf[subschema #1]/items/` list-of-types was widened by adding types `null` to media type `application/json` of response `200`
  - response property `data/truncated/anyOf[subschema #1]/items/` list-of-types was widened by adding types `null` to media type `application/json` of response `200`
- **2026-08-24** `64715a22734d` — 10 info
  - added the optional property `data/chamber` to the response with the `200` status
  - added the optional property `data/congress` to the response with the `200` status
  - added the optional property `data/doc_type` to the response with the `200` status
  - added the optional property `data/documents` to the response with the `200` status
  - …6 more
- **2026-08-08** `4c4530760ba1` — 12 info
  - added the optional property `code` to the response with the `401` status
  - added the optional property `code` to the response with the `429` status
  - added the optional property `code` to the response with the `503` status
  - added the optional property `hint` to the response with the `401` status
  - …8 more

[Change history](https://skmtc.dev/sugra/apis/sugra-api/changes/api/v1/congress/committees/:chamber/:system_code/documents/get.md)

---

[API](https://skmtc.dev/sugra/apis/sugra-api.md) · [All operations](https://skmtc.dev/sugra/apis/sugra-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/sugra/sugra-api/revisions/87582f2e0110/schema)