For developers & integrators

An API for the count.

The election-data API we wish we had had when we started. OpenAPI specs, typed SDKs, webhook events, rate-limited public endpoints, and integration recipes for INEC EFLOC/EMSC, Zoom, SignalR, and Cloudinary.

Request API access

What you're up against

The problems we built for.

  • Election data is a PDF

    You wrote a scraper once. You do not want to write another one.

  • Integrations are bespoke

    Every commission and every party does EFLOC, EMSC, and result reconciliation differently.

  • Documentation is pitched at sales

    You need OpenAPI specs, not white papers.

How iElect helps

The right products for developers & integrators.

How it works together

Apply for an API key. We issue scoped, rate-limited tokens: a read-only "press" tier that streams aggregated tallies, a "partner" tier that adds observer incidents and polling-unit metadata, and a "deployment" tier for commissions and parties. Webhooks fire on result, incident, and certification events. TypeScript + Python SDKs; reference integrations in our GitHub org.

"We replaced an eight-month scraping project with a two-day integration against the iElect feed. The API is boring — in the best possible way."
Senior engineer, civic-tech NGO — pilot partner
Request API access