How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Library of Congress

Library of Congress committee API

Returns committee data from the API

Documentation Provider Profile APIs.io OpenAPI GitHub

Library of Congress committee API is one of 25 APIs that Library of Congress publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include committee. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 11 operations across 11 paths, and defines 16 schemas. It is described by OpenAPI 3.0.3, at version 3.

Requests are made against a single base URL, /v3.

11 operations 11 paths 16 schemas 11 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
3
Base URL
https://www.loc.gov
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Library of Congress committee API declares 1 security scheme for authenticating requests. An API key is passed in the query as api_key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 11 GET. Each is listed below with its method, path, parameters, and response codes.

committee 11

Returns committee data from the API

GET
/committee
Returns a list of congressional committees.
5 params → 200400
GET
/committee/{chamber}
Returns a list of congressional committees filtered by the specified chamber.
6 params → 200400
GET
/committee/{congress}
Returns a list of congressional committees filtered by the specified congress.
6 params → 200400
GET
/committee/{congress}/{chamber}
Returns a list of congressional committees filtered by the specified congress and chamber.
7 params → 200400
GET
/committee/{chamber}/{committeeCode}
Returns detailed information for a specified congressional committee.
3 params → 200400
GET
/committee/{congress}/{chamber}/{committeeCode}
Returns detailed information for a specified congressional committee filtered by the specified Congress.
4 params → 200400
GET
/committee/{chamber}/{committeeCode}/bills
Returns the list of legislation associated with the specified congressional committee.
7 params → 200400
GET
/committee/{chamber}/{committeeCode}/reports
Returns the list of committee reports associated with a specified congressional committee.
7 params → 200400
GET
/committee/{chamber}/{committeeCode}/nominations
Returns the list of nominations associated with a specified congressional committee.
5 params → 200400
GET
/committee/{chamber}/{committeeCode}/house-communication
Returns the list of House communications associated with a specified congressional committee.
5 params → 200400
GET
/committee/{chamber}/{committeeCode}/senate-communication
Returns the list of Senate communications associated with a specified congressional committee.
5 params → 200400

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are committeeNominations (10 properties), CommitteeDetail (9 properties), committeeReports (8 properties), Committees (8 properties). Each schema is shown below with its type and property counts.

nominationType
object
2 properties
CommitteeDetail
object
9 properties
latestAction
object
2 properties
parentcommittee
object
3 properties
committeeBill
object
7 properties
CommitteeHouseCommunication
CommitteeSenateCommunication
committeeReports
object
8 properties
committeeNominations
object
10 properties
CommitteeReports
array
committeeHistory
object
5 properties
CommitteeBills
object
3 properties
CommitteeCommunication
object
5 properties
subcommittees
object
3 properties
CommitteeNominations
array
Committees
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

loc-committee-api-openapi.yml Raw ↑

Other APIs Library of Congress publishes across the network.

Chronicling America API
AE Profile APIs.io
Library of Congress amendments API
AE Profile APIs.io
Library of Congress bill API
AE Profile APIs.io
Library of Congress bound-congressional-record API
AE Profile APIs.io
Library of Congress collections API
AE Profile APIs.io
Library of Congress committee-meeting API
AE Profile APIs.io
Library of Congress committee-print API
AE Profile APIs.io
Library of Congress committee-report API
AE Profile APIs.io
Library of Congress congress API
AE Profile APIs.io
Library of Congress congressional-record API
AE Profile APIs.io
Library of Congress crsreport API
AE Profile APIs.io
Library of Congress daily-congressional-record API
AE Profile APIs.io
#committee
← Back to L APIs
API Details
ID
loc:loc-committee-api
Base URL
https://www.loc.gov
Docs
https://www.loc.gov/apis/json-and-yaml/
Provider
Library of Congress
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=loc-committee-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/loc-committee-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Library of Congress committee API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.