Government intake · partner portal
Push your ballot data to us
County registrars and state election offices can push measures, races, and official arguments directly into ThinkBallot's pipeline — authenticated, provenance-stamped, and staged. Nothing publishes without passing the same grounding checks and human review as every other source.
How a push flows
1 · Push
Your system POSTs to /intake/v1 with partner credentials.
2 · Staging
The record lands in staging — never the live dataset. Your office is recorded as its source.
3 · Pipeline
The same grounding pass and cite-or-omit checks run on your content.
4 · Review
A human reviews the generated card against your submission.
5 · Published
A new dataset version goes live, your office cited on every field.
Your submissions (mock partner: Santa Clara County ROV)
| Record | Pushed | Provenance | Status |
|---|---|---|---|
| Measure A: Transit Connectivity Sales Tax | Jun 12, 2026 | scc-rov · api-push | published |
| Measure B: Library Parcel Tax Renewal | Jun 12, 2026 | scc-rov · api-push | published |
| Measure C: Fire District Consolidation | Jun 28, 2026 | scc-rov · api-push | in review |
| Local ordinance argument texts (batch) | Jul 1, 2026 | scc-rov · api-push | staged |
| Corrected fiscal note, Measure A | Jul 2, 2026 | scc-rov · api-push | received |
Sample push payload
POST /intake/v1/measures · Authorization: Bearer <partner-token>
{
"jurisdiction": "county:06085",
"election": "2026-11-03-ca-general",
"title": "Measure C: Fire District Consolidation",
"official_text_url": "https://vote.example.gov/measures/c.pdf",
"arguments": { "for_url": "…", "against_url": "…" }
}
Interested in a partnership, or in a dedicated hosted
instance for your jurisdiction? This portal is a mock — the real intake API ships after the core
product.