> ## Documentation Index > Fetch the complete documentation index at: https://doc.astreus.ai/llms.txt > Use this file to discover all available pages before exploring further. # Congressional calendar > US House and Senate committee meetings in a window (up to 93 days, Washington days), each chamber's session days, and how far each chamber's published calendar reaches. Cancelled and postponed meetings keep their status. `limit`/`offset` page the meetings; session days are always whole. ## OpenAPI ````yaml https://astreus.ai/openapi.json get /api/v1/congressional/calendar openapi: 3.1.0 info: title: Astreus API version: '2026-11-11' description: >- Astreus is a financial data terminal that turns the world's unstructured financial disclosure into structured, traceable data. It reads what companies, exchanges and central banks publish — annual and interim reports, SEC filings, results announcements, investor presentations, earnings calls, 8-Ks, regulator notices and policy text — across the United States, the Gulf (Tadawul, DFM, ADX, Boursa Kuwait, QSE), Japan, Taiwan, Korea, the UK and Europe, and serves it as data a program can trust: standardized financial statements (annual, quarterly, semiannual), segments and KPIs, the tables inside the notes, filing sections as text, investor decks page by page, earnings-call transcripts and audio, span-anchored observations, management guidance scored against outcomes, typed 8-K events, an attributed intraday news tape, insider and 13F ownership, a people registry, macro series (the current vintage: the latest published value for each period) and central-bank text, benchmark, commodity and compute-price series, and a source-linked claim graph with declared validation limits. Use `fact-source` and document metadata to retain available provenance. Publication and entitlement gates apply per dataset; inspect availability and tool limitations. Coverage is published live: `GET /api/v1/landing/coverage` (no key) returns every market served with company counts, history depth, completeness and periods held per data type — ask it before answering "what do you cover?". `{id}` is a ticker, a numeric SEC CIK, or a platform key for a non-SEC issuer (XSAU000001) — the `cik` field of the company payload. Human-readable guides: https://doc.astreus.ai (coverage at /coverage, data catalog at /data-catalog). Tiers: `public` endpoints need no credentials. Everything else takes an **API key** — create one on the Developers page in the terminal (https://astreus.ai/developers) and send it as `X-API-KEY: pk_live_...` (or `Authorization: Bearer pk_live_...`). Signed-in terminal sessions may use their Cognito ID token instead. Rate limits and quotas are per plan (fixed UTC windows): Free — 30 req/min, 250 req/day; Build — 300 req/min, 100,000 req/month; Scale — custom. Build, Scale and prepaid credits are set up with sales (https://astreus.ai/contact), not self-serve. Responses carry RateLimit-*, X-Quota-* and, when credits pay, X-Billing-Source/X-Credits-Remaining-USD headers; a 429 carries `Retry-After` and a machine `code` of rate_limited or quota_exceeded (with sales_email). Server-side use: `/api/v1` sends no CORS headers, so a browser page on another origin cannot call it. Call it from a server, a script or an agent, and keep the key there. Versioning: `info.version` is the UTC date the contract last changed, and every response carries it in `x-astreus-api-version`. Within `/api/v1` changes are additive; a field or parameter that will go is marked `deprecated` first and kept for at least 90 days. Policy: https://doc.astreus.ai/versioning. Not investment advice. See /terms. contact: email: saif@astreus.ai termsOfService: https://astreus.ai/terms license: name: 'Proprietary: Astreus terms of service' url: https://astreus.ai/terms servers: - url: https://astreus.ai security: [] tags: - name: Search & Meta description: Entity resolution and platform metadata. - name: Company Data description: Profiles, structure, leadership, calendars. - name: Geo & Assets description: >- Physical assets on the map — what a company owns, operates or develops, where, since when, at what location precision, and the source behind each fact. - name: Financial Statements description: >- Standardized XBRL-derived statements — every line traceable to its filing via fact provenance. - name: SEC Filings description: >- The filing index and documents (SEC and exchange-published), parsed section text, and the tables inside the notes as gated grids and series. - name: 8-K Events description: >- Material events: 8-K items and exchange disclosures by item code, filterable by family, with extracted item text. - name: News description: >- The intraday news tape: filings, releases and licensed wires with source attribution, storylines and topics. - name: Transcripts & Calls description: Earnings-call transcripts, span-anchored observations, IR decks. - name: Guidance & Scorecards description: What management promised vs. what happened. - name: Ownership & Insiders description: 13F holders, Forms 3/4/5, the people registry. - name: Macro description: >- Economic series (the current vintage: the latest published value for each period) and central-bank text. - name: Market Data description: Daily bars for stocks, benchmarks, commodities and compute. - name: Intelligence description: Narratives and source-linked claims with declared validation status. - name: Analytics description: Charting over any catalog series. paths: /api/v1/congressional/calendar: get: tags: - Macro summary: Congressional calendar description: >- US House and Senate committee meetings in a window (up to 93 days, Washington days), each chamber's session days, and how far each chamber's published calendar reaches. Cancelled and postponed meetings keep their status. `limit`/`offset` page the meetings; session days are always whole. operationId: get-congressional-calendar parameters: - name: from in: query description: First day, YYYY-MM-DD (default today). schema: type: string - name: to in: query description: Last day, YYYY-MM-DD (default `from`). schema: type: string - name: chamber in: query description: >- One chamber: house or senate (joint meetings are returned only when no chamber is given). schema: type: string enum: - house - senate - name: kinds in: query description: 'Comma-separated: hearing, markup, business.' schema: type: string - name: committee in: query description: Committee system code, e.g. ssbk00. schema: type: string - name: search in: query description: >- Meeting title or location contains (case-insensitive); max 100 characters. schema: type: string - name: limit in: query description: >- Page size, 1–500 (500 when only `offset` is given); with `offset`, pages the window (`nextOffset` names the next page). Without both, the whole window. schema: type: integer minimum: 1 maximum: 500 - name: offset in: query description: Rows to skip, default 0. schema: type: integer minimum: 0 default: 0 responses: '200': description: OK content: application/json: schema: type: object properties: events: type: array items: type: object properties: id: type: string chamber: type: string eventId: type: string congress: type: integer date: type: string format: date meetingAt: type: string format: date-time time: type: string title: type: string kind: type: string meetingType: type: string closed: type: boolean status: type: string location: type: string committees: type: array items: type: object properties: systemCode: type: string name: type: string parentSystemCode: type: string witnessCount: type: integer url: type: string days: type: array items: type: object properties: chamber: type: string date: type: string format: date status: type: string conveneAt: type: - string - 'null' format: date-time conveneText: type: - string - 'null' adjournedAt: type: - string - 'null' format: date-time adjournedText: type: - string - 'null' ranPastMidnight: type: boolean statusFrom: type: 'null' program: type: 'null' basis: type: string bases: type: array items: type: string observedOn: type: string format: date sourceRef: type: string horizon: type: object properties: house: type: object properties: publishedThrough: type: string format: date note: type: string senate: type: object properties: publishedThrough: type: string format: date note: type: string summary: type: object properties: hearing: type: integer markup: type: integer business: type: integer total: type: integer truncated: type: boolean generatedAt: type: string format: date-time offset: type: integer limit: type: integer nextOffset: type: integer description: >- Inferred from captured responses: every field shown was returned by a real call; a field may be absent or null on other calls. x-schema-source: inferred example: events: - id: house:119515 chamber: house eventId: '119515' congress: 119 date: '2026-09-01' meetingAt: '2026-09-01T14:00:00.000Z' time: 10:00 AM title: >- Countering Houthi Terrorism: Protecting U.S. Interests and Security in the Red Sea kind: hearing meetingType: Hearing closed: false status: scheduled location: Rayburn House Office Building 2172 committees: - systemCode: hsfa13 name: House Subcommittee on the Middle East and North Africa parentSystemCode: hsfa00 witnessCount: 2 url: >- https://www.congress.gov/event/119th-congress/house-event/119515 - id: house:119516 chamber: house eventId: '119516' congress: 119 date: '2026-09-01' meetingAt: '2026-09-01T14:00:00.000Z' time: 10:00 AM title: “Sanctuary Policies, Tragic Consequences” kind: hearing meetingType: Hearing closed: false status: scheduled location: Rayburn House Office Building 2141 committees: - systemCode: hsju01 name: >- House Subcommittee on Immigration Integrity, Security, and Enforcement parentSystemCode: hsju00 witnessCount: 4 url: >- https://www.congress.gov/event/119th-congress/house-event/119516 days: - chamber: house date: '2026-09-01' status: in_session conveneAt: '2026-09-01T15:00:00.000Z' conveneText: 11 a.m. adjournedAt: '2026-09-02T00:23:00.000Z' adjournedText: 8:23 p.m. ranPastMidnight: false statusFrom: null program: null basis: congressional_record bases: - annual_calendar - congressional_record observedOn: '2026-09-01' sourceRef: CREC-2026-09-01-pt1-PgD854-3 - chamber: senate date: '2026-09-02' status: not_in_session conveneAt: null conveneText: null adjournedAt: null adjournedText: null ranPastMidnight: false statusFrom: null program: null basis: congressional_record bases: - congressional_record observedOn: '2026-09-02' sourceRef: CREC-2026-09-02-pt1-PgD859 horizon: house: publishedThrough: '2026-12-31' note: >- The House publishes an annual calendar of session days and district work periods, and the Daily Digest announces each sitting the day before. senate: publishedThrough: '2026-11-02' note: >- The Senate publishes no machine-readable forward calendar — senate.gov refuses automated access — so its days come from the Congressional Record and reach only as far as the last Daily Digest's announ… summary: hearing: 82 markup: 11 business: 17 total: 110 truncated: false generatedAt: '2026-11-01T12:49:09.510Z' offset: 0 limit: 2 nextOffset: 2 '400': description: >- A query parameter the route does not take (unknown_parameter), a value outside its type, enum or range (invalid_parameter), or a required one missing (missing_parameter); `param` names it. A request refused against this spec's parameter list is not metered. content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Missing or invalid bearer token. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Unknown company, country, symbol or resource. content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: Rate limited. Honour Retry-After. content: application/json: schema: $ref: '#/components/schemas/Error' security: - apiKey: [] - cognitoIdToken: [] components: schemas: Error: type: object required: - error - code properties: error: type: string description: Human-readable message. It may change; branch on `code`. code: type: string description: >- Stable machine code; every error carries one. unknown_parameter, invalid_parameter and missing_parameter come with `param`; unknown_parameter also with `allowed`. A route may add codes of its own (e.g. key_limit); treat an unlisted code by its HTTP status. enum: - unknown_parameter - invalid_parameter - missing_parameter - invalid_request - unauthenticated - upgrade_required - forbidden - not_found - conflict - too_large - unsupported_media_type - rate_limited - quota_exceeded - auth_unavailable - upstream_unavailable - internal_error param: type: string description: The query parameter at fault, when one is. allowed: type: array items: type: string description: 'With unknown_parameter: every query parameter the route takes.' securitySchemes: apiKey: type: apiKey in: header name: X-API-KEY description: >- Astreus API key (pk_live_...), created on the Developers page in the terminal. Also accepted as `Authorization: Bearer pk_live_...`. x-default: pk_live_YOUR_KEY cognitoIdToken: type: http scheme: bearer bearerFormat: JWT description: >- Amazon Cognito ID token (token_use=id) for the Astreus user pool — the terminal's own session credential. API consumers should use an API key instead. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.