Periods of affiliation are by marriage or registered partnership of persons registered in the Municipal Basic Administration of Personal Data (GBA). (from 01-01-1995)

Open data API in a single place

Provided by Centraal_Bureau_voor_de_Statistiek

Get early access to Periods of affiliation are by marriage or registered partnership of persons registered in the Municipal Basic Administration of Personal Data (GBA). (from 01-01-1995) API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Data Governance Act, Huwelijk wettig, Huwelijksontbinding, Microdata, Geregistreerd partnerschap, DGA, ODISSEI
Quality scoring

Dataset description

The GBAVERBINTENISPARTNERBUS is a key file for linking all persons registered in the GBA who have (once) entered into a commitment with each other. This commitment shall include the type of commitment, the starting date and, where appropriate, the end date. If an end date is included, the reason for this is also included. Finally, a link number has been added. The link number gives an indication of the assurance that is linked to the right commitment partner. Partners within a commitment do not have to live at one address at the time of this commitment. Purpose of the bus: The bus is intended to identify (personal) characteristics of both commitment partners. The number of commitments made in a given period cannot be inferred from the bus. The bus appears once a year. An obligation means both a marriage and a registered partnership. Marriage: Legal commitment to the coexistence of two persons. Since April 2001, marriage has also been open to persons of the same sex. Registered partnership: A relationship similar to marriage between two persons of the same or different sex, recorded in a civil act Stand. The registered partnership was introduced in the Netherlands on 1 January 1998. If a person has made a commitment several times, this person appears on the bus as many times. Each commitment always occurs twice on the bus: — Once with a person as RINPERSOON; — Once with this same person as RINPERSONVERBINTENISP (=partner). More information on how to access the data: > https://www.cbs.nl/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### Methodology A. A person’s commitment history may not be complete. Reasons for this are: — Commitments of which the partner resides abroad are missing. After all, no identification number of the partner is known. — Commitments whose partner died or emigrated before the start of the DPA (in October 1994) are missing. After all, no identification is possible. — Document GBAVERBINTENISPARTNERBUS.DOCX contains a more extensive research description. This document is in the \\Ssb2f\Ssb22\Ssbkern\Tools\Descriptions\docum folder. B. The component was set up as a BUSCOMPONENT. This means that new information on past commitments has been incorporated into each new version of the bus. D. From 1998 onwards, it is possible to establish a commitment through a registered partnership instead of a marriage. The registered partnership is open from the outset to partners of equal sex. From April 2001, marriage is also open to same-sex partners. From 2001 onwards, a registered partnership can be converted into a marriage. From 2001 to April 2009, a marriage could be converted into a registered partnership. A small number of commitments (&500) complies with these rules but is logically explained (e.g. due to gender change). E. Partners within a commitment do not have to live at one address at the time of this commitment. ### Population Commitment(s) of persons registered in the DPA since 1 January 1995 who are (were) linked by marriage or registered partnership. Excluding commitments for which the partner’s identification number is not known.
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