Build on the data that runs Akashic Edge.
Ask a question. Explore the map. Analyze a place. Build on the data. Every chart, map, and dossier on the site is powered by the same API you’ll use. Same data, same schema, same 165 years — shipped to your stack in one line of code.
A REST API built for real workloads — not a weekend demo.
Versioned endpoints, an OpenAPI spec you can generate clients from, and predictable pagination.
Every response is the same data we use to render the product. If it’s on akashicedge.com, you can pull it.
Production-grade election data, shipped to your stack.
Newsrooms and publishers
Power explainers, election desk utilities, embed rollouts, and shareable county or state context without hand-building every chart.
Researchers and analysts
Move from a place question to reproducible queries, structured exports, and provenance-aware data access without rebuilding the base dataset.
Product and platform teams
Use one source of truth for applications, internal tooling, and public-facing data products instead of stitching together partial vendors.
What the API actually does
One clean schema, everywhere
{
"data": [
{ "fips": "55025", "county": "Dane County", "margin": 39.51 },
{ "fips": "55079", "county": "Milwaukee County", "margin": 30.36 },
{ "fips": "55133", "county": "Waukesha County", "margin": -18.55 }
],
"meta": { "queryTimeMs": 18, "rowCount": 72, "apiVersion": "v1" },
"rateLimit": { "limit": 60, "remaining": 59 }
}A few endpoints to get the feel
| Method | Route | What it is for |
|---|---|---|
| GET | /api/v1/elections | List election years and office availability. |
| GET | /api/v1/elections/2024/president | Return structured election results by office and cycle. |
| GET | /api/v1/elections/timeseries | Fetch time-series margin history for a place or comparison set. |
| GET | /api/v1/counties/17031 | Return county profile, demographics, and election context. |
| GET | /api/v1/compare | Compare places or elections on one shared schema. |
| POST | /api/v1/historian/query | Access the Historian programmatically on eligible tiers. |
Separate evaluation, production use, and institutional rollout.
Evaluate
Read the docs, inspect the schema, and review the developer dashboard flow before you commit.
Edge Insider
Use the paid individual build tier when you need repeatable developer access, Historian API workflows, and clean embeds.
Institutional rollout
Use the institutional path when the actual buyer is a newsroom, classroom, lab, or organization.