Pull your records, receipts, and status on your own terms.
A REST API for teams that build their own integration. Every consented visitor arrives as one record, with its receipt.
The scan shows whether your site already runs API.
How it works
Inside API, where you already work.
Your engineers query your tenant directly: list consented records, fetch a single record with its receipt, check consent status, and page through changes since a timestamp. Nothing is pushed unless you also turn on the webhook.
REST over HTTPS with per-tenant API keys, documented endpoints, and rate limits set on the install call.
- 1A visitor says yes on your site.
- 2ReachTheVote.com verifies the record and writes the receipt.
- 3The record lands in your tenant, pulled on request by your own systems.
What we send, and how.
Consent receipts travel as a tag, source code, or field. No destination has a receipt object of its own, and every field is one the visitor agreed to.
- What it is
- A REST API for teams that build their own integration.
- How it connects
- API · Your tenant, pulled on request by your own systems
- What we send
- Enriched Voter Contact, with its consent receipt
Late bulletin
Every day you wait, visitors leave as strangers. Scan your site today.
Ten seconds. Your Supporter Reach Score, what fires before anyone says yes, and what your privacy policy leaves out. Nothing installed, nobody contacted.
- A real browser load of your homepage, screenshot included
- Every tag that fires before a visitor can answer
- Your privacy policy, lined up against what the site does
- Modeled traffic and what an ask-first step would return