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 crsreport API
  version: '3'
servers:
- url: /v3
security:
- ApiKeyAuth: []
tags:
- name: crsreport
  description: Returns Congressional Research Service (CRS) report data from the API
paths:
  /crsreport:
    get:
      tags:
      - crsreport
      summary: Returns Congressional Research Service (CRS) report data from the API
      description: Returns Congressional Research Service (CRS) report data from the API
      parameters:
      - $ref: '#/components/parameters/format'
      - $ref: '#/components/parameters/offset'
      - $ref: '#/components/parameters/limit'
      - $ref: '#/components/parameters/fromDateTime'
      - $ref: '#/components/parameters/toDateTime'
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CrsReport'
            application/xml:
              schema:
                $ref: '#/components/schemas/CrsReport'
        '400':
          description: Invalid status value
  /crsreport/{reportNumber}:
    get:
      tags:
      - crsreport
      summary: Returns Congressional Research Service (CRS) report data from the API
      description: Returns Congressional Research Service (CRS) report data from the API
      parameters:
      - $ref: '#/components/parameters/crsReportNumber'
      - $ref: '#/components/parameters/format'
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CrsReportDetail'
            application/xml:
              schema:
                $ref: '#/components/schemas/CrsReportDetail'
        '400':
          description: Invalid status value
components:
  schemas:
    format:
      type: object
      properties:
        format:
          type: string
          example: PDF
      url:
        type: string
        format: url
        example: https://www.congress.gov/crs_external_products/R/PDF/R47175/R47175.1.pdf
    CrsReport:
      type: object
      properties:
        CRSReports:
          type: array
          items:
            $ref: '#/components/schemas/crsreport'
    crsreport:
      type: object
      properties:
        contentType:
          type: string
          example: Reports
        id:
          type: string
          example: R43083
        publishDate:
          type: string
          format: date-time
          example: '2025-02-05T11:34:25Z'
        status:
          type: string
          example: Active
        title:
          type: string
          example: 'SBA Assistance to Small Business Startups: Client Experiences and Program Impact'
        updateDate:
          type: string
          format: date-time
          example: '2025-02-07T01:36:49Z'
        url:
          type: string
          format: url
          example: https://api.congress.gov/v3/crsreport/R43083
        version:
          type: integer
          example: 145
    author:
      type: object
      properties:
        author:
          type: string
          example: Megan S. Lynch
    relatedMaterial:
      type: object
      properties:
        URL:
          type: string
          example: https://api.congress.gov/v3/law/93/pub/344
        congress:
          type: integer
          example: 93
        number:
          type: string
          example: 93-344
        title:
          type: string
          example: Providing for budget allocations, and for other purposes.
        type:
          type: string
          example: PUB
    CrsReportDetail:
      type: object
      properties:
        authors:
          type: array
          items:
            $ref: '#/components/schemas/author'
        contentType:
          type: string
          example: Reports
        formats:
          type: array
          items:
            $ref: '#/components/schemas/format'
        id:
          type: string
          example: R47175
        publishDate:
          type: string
          format: date-time
          example: '2022-07-11T04:00:00Z'
        relatedMaterials:
          type: array
          items:
            $ref: '#/components/schemas/relatedMaterial'
        status:
          type: string
          example: Active
        summary:
          type: string
          example: "The Congressional Budget Act of 1974 directs Congress to adopt a budget resolution each spring, providing an agreement between the House and Senate on a budget plan for the upcoming fiscal year (and at least four additional years). The annual budget resolution includes certain spending and revenue levels that become enforceable through points of order once both chambers have adopted the resolution.\nCongress does not always adopt a budget resolution, however, and this may complicate the development and consideration of budgetary legislation. Congress has, therefore, developed an alternative legislative tool, typically referred to as a “deeming resolution” because it is deemed to serve in place of an annual budget resolution for the purposes of establishing enforceable budgetary levels. \nOn June 8, 2022, the House of Representatives adopted H.Res. 1151, a deeming resolution for FY2023. H.Res. 1151 provided a committee spending allocation (302(a) allocation) to the House Appropriations Committee ($1.603 trillion). It also directed the chair of the House Budget Committee to subsequently file a statement in the Congressional Record that includes committee spending allocations for all other committees, as well as aggregate spending and revenue levels. (Those levels were filed on June 21, 2022.) H.Res. 1151 specified that the levels filed in the Congressional Record be consistent with the “most recent baseline of the Congressional Budget Office,” meaning that the committee spending allocations (other than for the Appropriations Committee) and the aggregate spending and revenue levels have been set at the levels currently projected under current law. \nIn addition to providing enforceable budgetary levels within the House, H.Res. 1151 grants authority to the chair of the House Budget Committee to “adjust” the budgetary levels provided under the deeming resolution in the future under specified circumstances. In addition, the resolution states that provisions designated as “emergency” shall be effectively exempt from House budgetary rules and specifies that certain accounts may receive advance appropriations for FY2024 and FY2025. \n"
        title:
          type: string
          example: 'Settings Budgetary Levels: The House''s FY2023 Deeming Resolution'
        topics:
          type: array
          items:
            $ref: '#/components/schemas/topic'
        updateDate:
          type: string
          format: date-time
          example: '2025-06-20T23:46:23Z'
        url:
          type: string
          format: url
          example: www.congress.gov/crs-report/R47175
        version:
          type: integer
          example: 1
    topic:
      type: object
      properties:
        topic:
          type: string
          example: Budget & Appropriations Procedure
  parameters:
    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
    toDateTime:
      name: toDateTime
      in: query
      description: 'The ending timestamp to filter by update date. Use format: YYYY-MM-DDT00:00:00Z.'
      required: false
      schema:
        type: string
    fromDateTime:
      name: fromDateTime
      in: query
      description: 'The starting timestamp to filter by update date. Use format: YYYY-MM-DDT00:00:00Z.'
      required: false
      schema:
        type: string
    crsReportNumber:
      name: reportNumber
      in: path
      description: The number or ID of the report. For example, R47175.
      required: true
      schema:
        type: string
    limit:
      name: limit
      in: query
      description: The number of records returned. The maximum limit is 250.
      required: false
      schema:
        type: integer
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: query
      name: api_key