Provider transparency
Two 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 ↗Provider responses are schema-validated before any cache transaction begins. Timeouts, malformed responses, rate limits, and upstream errors are logged in the private sync ledger. 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. The last successful cached records remain available and are visibly labeled stale when their freshness threshold is exceeded.
