The legislative cantons of the Gard

Open data API in a single place

Provided by Département du Gard

Get early access to The legislative cantons of the Gard API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Quality scoring

Dataset description

The Gard department has 23 cantons since the 2014 cantonal redivision. A redivision of the French cantons is defined by the law of 17 May 20131 and the implementing decrees published in February and March 2014. In accordance with this law, the constituencies of the cantons allow the election of departmental assemblies, renamed departmental councils by majority, binominal and parity ballot. Indeed, this redundancy is accompanied by a voting method designed to promote parity: each new canton is represented by two departmental councillors, a man and a woman, elected in pairs. The first such elections (departmental elections) took place in March 2015, the terms of office of the general councillors elected in 2008 and in 2011 expiring in 2015 by way of derogation from Article L.192 of the Electoral Code2,3, 4.5. Postponed in December 2015 in the draft law defining the new map of regions6, these departmental elections are held in March 2015, after arbitration of Prime Minister Manuel Valls. https://www.gard.fr/le-gard/le-departement/votre-canton-vos-elus.html
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