Provider transparency
Three public providers. 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 ↗Federal 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; 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. House roll-call data is explicitly limited to the House and is not described as Senate voting.
Read Congress.gov API documentation ↗Provider responses 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. A failed Congress.gov detail refresh retains the previous complete detail record. The last successful cached records remain available and are visibly labeled stale when their freshness threshold is exceeded.
