Election result of the Styria state election in 2010 after Graz districts

Open data API in a single place

Provided by http://www.graz.at/buergerinnenamt

Get early access to Election result of the Styria state election in 2010 after Graz districts API!

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

Dataset information

Catalog

http://www.graz.at/buergerinnenamt catalog

Country of origin

Austria

Updated

Created

Available languages

English

Keywords

wahlen, landtagswahlen, politik

Datasource

Official portal for European data link

Quality scoring

Dataset description

Election result of the Styria state election on 29.09.2010 in the city of Graz. Voting results according to Graz districts including election card polling stations but without postal voting votes short, short name of the election beznr, Graz district number (100 = 1. District, 200 = 2. District, etc.) bezname, Graz district name ptname, party name short ptlang, party name long list Place total, total votes cast unguel, invalid votes gueltig, valid votes votes, votes per party number of blasts, number of district’s summed up explosives

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

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

About api.storePrivacy Terms of Service