Buildings protected under the Historic Monuments – City of Clermont-Ferrand

Open data API in a single place

Provided by Clermont Auvergne Métropole

Get early access to Buildings protected under the Historic Monuments – City of Clermont-Ferrand API!

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

Dataset information

Country of origin
Updated
2025.08.25 10:00
Created
2022.11.22
Available languages
English
Keywords
immeubles, clermont-ferrand, merimee, culture-tourisme, monument-historique, monuments, culture
Quality scoring

Dataset description

**This list presents the buildings and buildings that have been or are protected under the Historic Monuments (classified or inscribed), from the year 1840 to the present.** The list presents all the information available on the Mérimée base, which comes from the Order and the protection file, established by the Historical Monuments Service. **Protected buildings date from Prehistory to the 20th century.** **Labelled fields**: Reference, Designation of the building, Current destination of the building, Address form index, Establishment assignee of the building, Other name of the building, Nature of protection, Author of the building, Cadastre, Commune form index, Copyright, Type of cover, Dating of the building, Place of conservation of a displaced architectural element, Description of the building, Standard dimensions of the shavings only, label date, Date of last update, Date of creation of the notice, Domain, File type, Date and typology of protection, Department digital format, Outer elevation part, Source of energy used by the building, Location shape and structure of the staircase, Description of the interior elevation, state of conservation, Framework of study, Type of recipient, History, name of the watercourse crossing or bordering the building, Aggregated Identifier, COG Insee during protection, Justification attribution, Justification for dating, External links, Location, Link to base Archiv MH, Materials of the bulk work, Observations, Affective precision, Constituent part not studied, Constituent part, Denomination precision, Persons related to the building, map typology, Precision of location, Precision of protection, Description of iconography, Typology of protection, Precision on the status of the building, Reference to a set, Link to the Jocond base, Link to the Palissy base, References of the constituent parts studied, Region, Department, Remarkable elements in the building, employment, Reference to a Merime or Palissy Base Notice, Standardised Iconographic Indexation, Secondary Construction Campaign Century, Century of the Main Construction Campaign, Short Format of the Construction Century, Typology of the Protection Area, Legal Status of the Building, Building Door Decor Technique, Editorial Title of Notice, Cover Materials, covers or discovered in the garden of the building, Vocable for cult buildings, Typology of covering, Address editorial form, Commune editorial form, code department, code Insee, coordinates in WGS84 format. This dataset is updated every Thursday at 6:00 am. N.B.: Monuments without geographical coordinates are **in the process of geolocation** by data producers. (https://www.culture.gouv.fr/var/culture/storage/images/_aliases/medium/media/thematiques/monuments-historiques-sites-patrimoniaux-remarquables/images/logotypes/logotypes-mh/logotype-mh-pour-edition-40mm-rvb-ombre/2181903-1-fre-FR/Logotype-MH-pour-edition-40mm-RVB-ombre.png)
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