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 hearing API

Returns hearing data from the API

Documentation Provider Profile APIs.io OpenAPI GitHub

Library of Congress hearing 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 Hearing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

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

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

4 operations 4 paths 6 schemas 4 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 hearing 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 4

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

hearing 4

Returns hearing data from the API

GET
/hearing
Returns a list of hearings.
3 params → 200400
GET
/hearing/{congress}
Returns a list of hearings filtered by specified congress.
4 params → 200400
GET
/hearing/{congress}/{chamber}
Returns a list of hearings filtered by specified congress and chamber.
5 params → 200400
GET
/hearing/{congress}/{chamber}/{jacketNumber}
Returns detailed information for a specified hearing.
6 params → 200400

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are HearingDetail (11 properties), hearing (5 properties), subcommittees (3 properties), associatedMeeting (2 properties). Each schema is shown below with its type and property counts.

formats
object
2 properties
Hearings
array
hearing
object
5 properties
subcommittees
object
3 properties
HearingDetail
object
11 properties
associatedMeeting
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

loc-hearing-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 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
#Hearing
← Back to L APIs
API Details
ID
loc:loc-hearing-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-hearing-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/loc-hearing-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 hearing 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.