House numbers

Open data API in a single place

Provided by Regione Emilia Romagna

Get early access to House numbers API!

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

Dataset information

Country of origin
Updated
2025.09.30 22:00
Created
2024.07.11
Available languages
English
Keywords
numeri-civici, toponomastica
Quality scoring

Dataset description

Civic numbers of the Municipality of Castel Bolognese. Description fields: ‘Stadio_civico’: Unique identifier, ‘Institution’: Code belfiore of the Municipality, "Codice_via": Unique street code, ‘Name’: Official street name, "Number": House number, ‘Exponent’: Specify numerically or literally the house number, "Exponent-number": Unine of the Number and Exponent fields, "Data_ Beginning": Date of digitization on the map, "Municipality": Cadastral code of the Municipality, "Foglio": Cadastral sheet number, ‘Mappale’: Cadastral parcel number, ‘Partkey’: Land registry key, "Civkey": Toponymy key. - Data managed through the Municipal Register of Real Estate (ACI) following the establishment, modification or termination of a Civic. The function is in charge of the Multifunctional Service, which coordinates and manages the toponymy service and external civic numbering. The first plant in ACI was made in 2016 with data extracted from the Regional Territorial Data Base (DBTR).
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