Council Elections Voters 2006

Open data API in a single place

Provided by Greater London Authority

Get early access to Council Elections Voters 2006 API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
elections, turnout, poll, party, voting
Quality scoring

Dataset description

<p>Numbers of votes by party for elections on 4 May 2006 by borough.</p> <p>Voters were able to make more than one vote. In 2006, it was discovered that Eastbury ward was inaccurate due to a clerical error. After seeking legal advice, it was decided that as the result had been declared it must stand until a petition is made to the High Court by the affected candidate. 2006: It was not possible for Hackney to provide figures for postal voters which included rejected ballot papers, all the rejected ballot papers are included with the polling station figures. 2006: Westminster would not provide figures for postal voters.</p> <p>The ward statistics from this election, can be found <a href="/dataset/council-elections-candidate-results-ward-2006" target="_blank">here</a>.</p>
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks