Provider transparency
Nine public-record families, plus one federal identity crosswalk. Local caches. Visible refresh state. Direct links back to original or provider records.
Public polling
Politically.com uses only VoteHub's documented polling endpoints: GET /polls, GET /polls/{poll_id}, GET /pollsters, GET /subjects, and GET /poll-types.
Polling data is provided by VoteHub under CC BY 4.0. VoteHub is the data provider; Politically.com is an independent cache and presentation layer.
Read VoteHub API documentation ↗Federal campaign finance
Politically.com uses official candidate, committee, total, report, and filing endpoints. The product displays summary totals supplied by the FEC and retains coverage dates and amendment indicators.
No Schedule A or individual-contributor endpoint is called. Donor names, addresses, and contributor-level rows are outside the Politically.com product boundary.
Read OpenFEC documentation ↗Certified federal outcomes
The FEC's biennial publication compiles official results certified by state election offices. Politically.com imports the U.S. Senate and House result worksheets from the hash-pinned 2022 workbook.
cdb258ea23803e50…Source winner markers are preserved without inference. Non-numeric cells such as Unopposed, *, and # remain source text. Shares are displayed only with the denominator printed in the same race table.
Federal lobbying disclosures
Politically.com caches 2025-forward filing records from the official authenticated REST API at lda.gov, including exact registrant and client identifiers, reporting periods, source-reported amounts, issue descriptions, and literal federal measure citations.
Every literal citation remains visible; a local bill link requires the exact derived Congress, measure type, and number. Missing amounts remain missing, and Politically.com publishes no filing rollups.
Read official API documentationFederal legislative records
Politically.com uses documented official endpoints for current Congress metadata; bills and their titles, actions, summaries, subjects, cosponsors, committees, amendments, text, and related measures; presidential nominations and dated actions; Congressional Research Service report metadata and structured related materials; laws; committee meetings; published hearings; members; committees; and House roll-call votes with member votes when supplied.
The API key remains in the off-tree server secret layer. Browser requests never call Congress.gov. CRS report pages retain metadata and official document links without mirroring report text; bill relationships require structured source identifiers. House roll-call data is explicitly limited to the House and is not described as Senate voting.
Read Congress.gov API documentation ↗Executive branch records
The public, no-key API supplies executive orders, final rules, proposed rules, structured agencies, publication and signing dates, comment deadlines, Federal Register citations, CFR references, docket identifiers, and links to the web record and official PDF.
The order series covers the API's complete executive-order result set beginning in 1994. The rule cache uses a reviewed January 1, 2025 start. The API exposes no structured statutory-authority field, so Politically.com does not create a law-to-rule join or text-mine citations into one.
FederalRegister.gov is an informational interface, not the official legal edition. Each detail page links to the GovInfo PDF supplied by the source. Public comment availability is displayed only from a structured source deadline and link.
Senate roll calls
Official roll-call list and detail XML supplies the question, result, measure, tally, and member votes for the current Senate session.
Election administration
The official 2024 EAVS Version 2.0 jurisdiction CSV supplies registration, reported voter, voting-method, precinct, and polling-place fields. Negative codebook sentinels remain missing.
The EAC publishes the archive for public access. Applicable federal copyright rules and any source-specific conditions remain authoritative; Politically.com does not apply VoteHub's CC BY license to EAVS records.
Open official EAVS archiveFederal identity links
The public unitedstates/congress-legislators dataset maps a congressional Bioguide identity to source-supplied FEC candidate IDs, a Senate LIS ID when present, dated congressional terms, and current committee assignments. Politically.com never substitutes a name match.
A valid crosswalk ID is retained even when the corresponding local record is not cached. A public cross-link appears only after both source records exist locally. Committee roster joins require both the exact committee system code and exact Bioguide ID.
Open source repositoryState legislative records
Open States normalizes legislative information across the 50 states, District of Columbia, and Puerto Rico. Politically.com uses official per-session JSON archives for the nationwide bill-and-vote foundation, current-legislator CSV files for rosters, and API v3 only as a budgeted freshness and correction layer.
The current REST contract allows 250 requests per fixed UTC day and 10 requests per fixed UTC minute. Politically.com starts no more than one request per second and enforces local ceilings of nine per minute and 225 per day, leaving capacity for retries and operator verification. No browser request calls Open States. When the budget is exhausted, queued updates wait while the last successful cache remains available.
Committees and events are explicitly presented as limited coverage because Open States marks those API surfaces as experimental and not every jurisdiction supplies the same fields. A missing vote, document, committee membership, or event is not interpreted as proof that none exists.
Data via Open States / Plural. Open States says almost all bulk data is provided under a public-domain dedication unless otherwise noted; its terms, source links, and any record-specific conditions remain authoritative. Politically.com is independent and not endorsed by Open States or Plural.
Provider responses and bulk artifacts are schema-validated before cache writes. Timeouts, malformed responses, rate limits, and upstream errors are logged in the private sync ledger with bounded request evidence. A VoteHub refresh may omit a bounded number of malformed individual records and records that count; it fails closed if more than five percent are invalid. Failed Congress.gov detail, Open States state/session, and federal identity imports retain the prior complete snapshot. A failed Lobbying Disclosure run retains already validated cache rows, records the failure, and leaves public freshness anchored to its last successful completion. The last successful cached records remain available and are visibly labeled stale when their freshness threshold is exceeded.