Woonbase Key file: all persons, households and living quarters and their mutual relationships in the Netherlands (01-03-2022 - 01-01-2023)

Open data API in a single place

Provided by Centraal_Bureau_voor_de_Statistiek

Get early access to Woonbase Key file: all persons, households and living quarters and their mutual relationships in the Netherlands (01-03-2022 - 01-01-2023) API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
ODISSEI, DGA, Data Governance Act, Microdata
Quality scoring

Dataset description

This Keyfile is one of the files that together form the Woonbase. This file includes all persons, households and residence objects and their mutual relationships that were registered in the Netherlands either on 1 January or on 31 December (GBA, or BAG). Also those berths (SL) that are inhabited somewhere during the year are included. More information on how to access the data: > https://www.cbs.nl/en-en/our-services/custom-and-microdata/microdata-self-research ### Methodology Woonbase is set up to ask the question "Who lives where with whom?" to answer. To this end, three types of files have been set up per year: a key file, attribute files and population files. The key file is a bus file for one year, in which the links between a person, a household and an object are recorded. Every time something changes in the link between the three entities, a new record is created. The attribute files include the attributes of an entity on both 1 January and 31 December for each record. In the population files, the characteristics of the different entities are combined on 1 January and 31 December according to the links in the key file. In this way, the question "Who lives where with whom?" be answered in a consistent manner from both individuals, households, and objects. ### Population Per record a person, with the residence object in which he lives and the household to which he belongs. Or, if an object is not inhabited, a residence object per record. When something changes in the relationship between these three populations, the record is closed and a new record is started.
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