Congress.gov API

Congress.gov API house-communication API

Returns House communication data from the API

GitHub OpenAPI

Documentation

📖
Documentation
https://github.com/LibraryOfCongress/api.congress.gov
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/congress-gov/refs/heads/main/rate-limits/congress-gov-rate-limits.yml

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/congress-gov/refs/heads/main/openapi/congress-gov-house-communication-api-openapi.yml

SDKs

📦
GitHubRepository
https://github.com/LibraryOfCongress/api.congress.gov

Other Resources

🔗
PostmanCollection
https://documenter.getpostman.com/view/6803158/VV56LCkZ
🔗
Signup
https://api.congress.gov/sign-up/
🔗
ChangeLog
https://github.com/LibraryOfCongress/api.congress.gov/blob/main/ChangeLog.md
🔗
CoverageDates
https://www.congress.gov/help/coverage-dates
🔗
DataOffsite
https://www.congress.gov/help/using-data-offsite
🔗
ApiKeyInfo
https://api.data.gov/docs/api-key/
🔗
Issues
https://github.com/LibraryOfCongress/api.congress.gov/issues
🔗
Plans
https://raw.githubusercontent.com/api-evangelist/congress-gov/refs/heads/main/plans/congress-gov-plans-pricing.yml
🔗
FinOps
https://raw.githubusercontent.com/api-evangelist/congress-gov/refs/heads/main/finops/congress-gov-finops.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/congress-gov-house-communication-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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

OpenAPI Specification

congress-gov-house-communication-api-openapi.yml Raw ↑ 
openapi: 3.0.3
info:
  description: 'Congress.gov shares its application programming interface (API) with the public to ingest the Congressional data. <a href="sign-up/" target="_blank">Sign up for an API key</a> from api.data.gov that you can use to access web services provided by Congress.gov. To learn more, view our <a href="https://github.com/LibraryOfCongress/api.congress.gov/" target="_blank">GitHub repository</a>.

    '
  title: Congress.gov amendments house-communication API
  version: '3'
servers:
- url: /v3
security:
- ApiKeyAuth: []
tags:
- name: house-communication
  description: Returns House communication data from the API
paths:
  /house-communication:
    get:
      tags:
      - house-communication
      summary: Returns a list of House communications.
      description: Returns a list of House communications.
      parameters:
      - $ref: '#/components/parameters/format'
      - $ref: '#/components/parameters/offset'
      - $ref: '#/components/parameters/limit'
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HouseCommunications'
            application/xml:
              schema:
                $ref: '#/components/schemas/HouseCommunications'
        '400':
          description: Invalid status value
  /house-communication/{congress}:
    get:
      tags:
      - house-communication
      summary: Returns a list of House communications filtered by the specified congress.
      description: Returns a list of House communications filtered by the specified congress.
      parameters:
      - $ref: '#/components/parameters/congress'
      - $ref: '#/components/parameters/format'
      - $ref: '#/components/parameters/offset'
      - $ref: '#/components/parameters/limit'
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HouseCommunications'
            application/xml:
              schema:
                $ref: '#/components/schemas/HouseCommunications'
        '400':
          description: Invalid status value
  /house-communication/{congress}/{communicationType}:
    get:
      tags:
      - house-communication
      summary: Returns a list of House communications filtered by the specified congress and communication type..
      description: Returns a list of House communications filtered by the specified congress and communication type.
      parameters:
      - $ref: '#/components/parameters/congress'
      - $ref: '#/components/parameters/communicationType'
      - $ref: '#/components/parameters/format'
      - $ref: '#/components/parameters/offset'
      - $ref: '#/components/parameters/limit'
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HouseCommunications'
            application/xml:
              schema:
                $ref: '#/components/schemas/HouseCommunications'
        '400':
          description: Invalid status value
  /house-communication/{congress}/{communicationType}/{communicationNumber}:
    get:
      tags:
      - house-communication
      summary: Returns a list of House communications filtered by the specified congress and communication type..
      description: Returns a list of House communications filtered by the specified congress and communication type.
      parameters:
      - $ref: '#/components/parameters/congress'
      - $ref: '#/components/parameters/communicationType'
      - $ref: '#/components/parameters/communicationNumber'
      - $ref: '#/components/parameters/format'
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HouseCommunicationTypeNumber'
            application/xml:
              schema:
                $ref: '#/components/schemas/HouseCommunicationTypeNumber'
        '400':
          description: Invalid status value
components:
  parameters:
    limit:
      name: limit
      in: query
      description: The number of records returned. The maximum limit is 250.
      required: false
      schema:
        type: integer
    congress:
      name: congress
      in: path
      description: The congress number. For example, can be 117.
      required: true
      schema:
        type: integer
        format: int32
    offset:
      name: offset
      in: query
      description: The starting record returned. 0 is the first record.
      required: false
      schema:
        type: integer
    format:
      name: format
      in: query
      description: The data format. Value can be xml or json.
      required: false
      schema:
        type: string
        default: xml
        enum:
        - xml
        - json
    communicationNumber:
      name: communicationNumber
      in: path
      description: The communication’s assigned number. For example, the value can be 3324.
      required: true
      schema:
        type: integer
    communicationType:
      name: communicationType
      in: path
      description: The type of communication. Value can be ec, ml, pm, or pt.
      required: true
      schema:
        type: string
        enum:
        - ec
        - ml
        - pm
        - pt
  schemas:
    HouseCommunications:
      type: object
      properties:
        houseCoummunications:
          type: array
          items:
            $ref: '#/components/schemas/houseCommunication'
    subcommittees:
      type: object
      properties:
        name:
          type: string
          example: Investigations and Oversight Subcommittee
        systemCode:
          type: string
          example: hspw01
        url:
          type: string
          format: url
          example: https://api.congress.gov/v3/committee/house/hspw01?format=json
    houseCommunication:
      type: object
      properties:
        chamber:
          type: string
          example: House
        communicationType:
          $ref: '#/components/schemas/communicationType'
        congressNumber:
          type: integer
          example: 117
        number:
          type: string
          example: '2057'
        updateDate:
          type: string
          format: date
          example: '2021-09-01'
        url:
          type: string
          format: url
          example: https://api.congress.gov/v3/house-communication/117/ec/2057?format=json
    HouseCommunicationTypeNumber:
      type: object
      properties:
        abstract:
          type: string
          example: A letter from the Director, Regulatory Management Division, Environmental Protection Agency, transmitting the Agency's request for applications - Technical Assistance to Brownfields Communities [EPA-I-OLEM-OBLR-22-12] received February 9, 2024, pursuant to 5 U.S.C. 801(a)(1)(A); Public Law 104–121, section 251; (110 Stat. 868); to the Committee on Energy and Commerce.
        chamber:
          type: string
          example: House
        committees:
          type: array
          items:
            allOf:
            - $ref: '#/components/schemas/subcommittees'
            - type: object
              properties:
                referralDate:
                  type: string
                  format: date
                  example: '2024-03-07'
        communicationType:
          $ref: '#/components/schemas/communicationType'
        congress:
          type: integer
          example: 118
        congressionalRecordDate:
          type: string
          format: date
          example: '2024-03-07'
        isRulemaking:
          type: string
          example: 'True'
        legalAuthority:
          type: string
          format: url
          example: 5 U.S.C. 801(a)(1)(A); Public Law 104–121, section 251; (110 Stat. 868)
        matchingRequirements:
          type: array
          items:
            type: object
            properties:
              number:
                type: integer
                example: 8070
              url:
                type: string
                format: url
                example: https://api.congress.gov/v3/house-requirement/8070
        number:
          type: integer
          example: 3324
        reportNature:
          type: string
          example: The Agency's request for applications - Technical Assistance to Brownfields Communities [EPA-I-OLEM-OBLR-22-12] received February 9, 2024.
        sessionNumber:
          type: integer
          example: 2
        submittingAgency:
          type: string
          example: Environmental Protection Agency
        submittingOfficial:
          type: string
          example: Director, Regulatory Management Division
        updateDate:
          type: string
          format: date
          example: '2024-09-03'
    communicationType:
      type: object
      properties:
        code:
          type: string
          example: EC
        name:
          type: string
          example: Executive Communication
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: query
      name: api_key