History — Buildings_protected_Monuments_Historical

Open data API in a single place

Provided by Commune de Brocas

Get early access to History — Buildings_protected_Monuments_Historical API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
monument-historique, history
Quality scoring

Dataset description

List and location of buildings protected under the Historic Monuments (extract from the Mérimée base). Labels of fields: REF: reference (PAxxxx); ADRS: address (track number, track type, track name); AFFE: assignee (useful for state property, mention the name of the ministry); AUTR: architect or prime contractor; COM: municipality for the location of the building; two columns: Com for the name of the municipality with rejection of the article and WCOM for the common name of the municipality; DESC: description; DPRO: date of protection; DPT_LETTER: Department in letters; HIST: history; INSEE: INSEE code; PPRO: details of the protection (Article 1 of the Protection Decree + cadastre + nature and date of protection); REG: region; SCLX: construction period; STAT: property status (type of owner by category; no names); TICO: Current title, common name(s) of the building. The proposed geolocation is carried out via the BAN (National Address Base) from the Address, Commune and INSEE code fields. (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