Haal Centraal BRP RvIG & authorisation PKIoverheid & GDPR

Custom BRP integration development

Appfront builds custom BRP integrations that let your application query personal data directly at the source: the Basic Registration of Persons (BRP), managed by the RvIG. Via the modern Haal Centraal BRP Bevragen API (REST/JSON) or legacy StUF-BG, we retrieve up-to-date name and address, marital status and residence data, with PKIoverheid, OAuth 2.0 and data minimisation within your authorisation decision. This way you work with current, reliable source data without duplicate registration.

What is a BRP integration?

The Basic Registration of Persons (BRP) is the central register of personal data on residents of the Netherlands and on non-residents (RNI), managed by the Dutch National Office for Identity Data (RvIG). The BRP is the source for up-to-date name and address details, marital status, partner, child and parent details, nationality and place of residence. By querying directly at the source, you work with current, reliable data and avoid duplicate registration.

There are two ways to query it. Modern: the Haal Centraal BRP Bevragen API, a RESTful API using JSON that deliberately uses the POST method so that no personal data ends up in URLs or server logs. Legacy: StUF-BG (based on LO GBA), the older SOAP/XML standard that still runs in many existing municipal and case-handling systems. Access is strictly reserved for organisations with a public task and a BRP authorisation decision, subject to strict GDPR and security requirements.

Appfront builds in line with the official RvIG BRP API documentation and the OWASP ASVS security standard. We tailor the queries, authorisation and error handling to your actual processes and to the principle of data minimisation, so that the integration only retrieves the data covered by your authorisation decision and stays reliable even at peak volumes.

Querying at the source

Look up current personal data directly in the BRP (Basic Registration of Persons) by BSN (citizen service number) or via search queries — name and address, marital status, partners, children and nationality. No outdated copies held in-house, but real-time source data from the RvIG (Dutch National Office for Identity Data) register.

{ } </>

Modern or legacy

Integrate via the modern Haal Centraal BRP Bevragen API (REST/JSON) or via legacy StUF-BG (SOAP/XML, LO GBA). We connect to your existing landscape or build a bridge from StUF to the new API where that makes sense.

Within your authorisation

The integration respects your BRP authorisation decision and the principle of data minimisation: only the fields needed for your statutory task. PKIoverheid, OAuth 2.0 and Diginetwerk ensure secure, traceable queries.

Our development process for BRP integrations

We follow a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your processes, authorisation decision and existing systems through to go-live and ongoing maintenance, every step is aimed at an integration your team can understand and trust.

1
Analysis & scope

We map out which BRP data you need for which processes, which route (Haal Centraal or StUF-BG) fits, and which fields fall within your authorisation decision and data minimisation.

2
Architecture

We design the integration architecture, arrange PKIoverheid certificates, OAuth 2.0 and the Diginetwerk connection, and draw up an error-handling strategy.

3
Development

Implementation of the queries with automated tests, structured logging without PII leaks, and monitoring. You see working builds along the way.

4
Go-live & maintenance

Controlled go-live with validation against the BRP and a safety net, followed by ongoing maintenance, certificate rotation and further development.

What a BRP integration delivers in practice

Every BRP integration is set up specifically for your processes, authorisation decision and adjacent systems. Below are the features we deliver most often for organisations that query personal data from the BRP for their services.

BSN

Looking up & searching persons

Look up a person by BSN or search by name, date of birth and address. The integration retrieves current name and address details, marital status, partners, children, parents and nationality, from both the BRP and the RNI (register of non-residents).

Residence history & occupancy

Query historical data: a person's residence history over a period or on a reference date, and the occupancy of an address over time. Essential for processes that need to look back at previous addresses or residents.

Information products

Besides raw data, the BRP API provides derived information products: addressing with the correct salutation and address lines, parental authority over minors, age in years, full name with titles and predicates, and initials, ready to use in your letters and applications.

Data minimisation

The integration requests only the fields that fall within your authorisation decision and statutory task. We set up the queries so that you receive no more personal data than strictly necessary, demonstrably in line with the GDPR and the RvIG's principles.

StUF-BG bridge & migration

Still using StUF-BG (SOAP/XML, LO GBA)? We can integrate with it or build a bridge that decouples your existing systems from the underlying route, so you can migrate step by step to the modern Haal Centraal API.

Logging and traceability

Every query is logged traceably (who, when and on what legal basis) without personal data leaking into URLs or plain logs. This keeps you in control of usage and keeps your record of processing activities complete and auditable.

Typical use cases in practice

A BRP integration works out very differently for each organisation. We see a number of patterns come up again and again, and for each of them we have a working setup that pays attention to authorisation, data minimisation and the right route (Haal Centraal or StUF-BG).

Municipalities

Municipalities that need current personal data for civil affairs, the social domain and enforcement. The BRP integration feeds case management systems and forms with verified name, address and marital status data. See also our software for municipalities and Haal Centraal integration.

Health insurers

Health insurers that base policyholder administration and policy processes on up-to-date personal data. The integration verifies name, address, date of birth and place of residence at the source, with data minimisation within the authorisation decision and strict GDPR safeguards for sensitive data.

Pension funds

Pension funds and administrators who keep member records up to date. Changes in marital status, partner relationships and address are verified at the source, so that benefit payments and correspondence are accurate. Residence history supports lawfulness checks.

Implementing organisations

National and regional implementing bodies with a public task that need personal data for allowances, permits or enforcement. The integration delivers verified source data, with traceable logging and a legal basis recorded for each BRP query.

Technology we use

We build BRP integrations with the official Haal Centraal BRP Bevragen API (REST/JSON) or legacy StUF-BG, combined with the backend stack that suits you. The exact choice depends on your route, authorisation decision and existing systems, so that your own team can manage or further develop the integration.

If your municipality works with PinkRoccade's iBurgerzaken, take a look at our iBurgerzaken integration.

Haal Centraal BRP Bevragen API REST / JSON OpenAPI 3.0 OAuth 2.0 (client credentials) PKIoverheid / mTLS Diginetwerk POST queries (no PII in logs) Persons, Occupancy & Residence history Information products (addressing, parental authority) StUF-BG (SOAP/XML) LO GBA (legacy) RNI (non-residents) Node.js / Python / PHP / .NET / Java / Go Data minimisation Audit logging GitHub Actions

Why Appfront for your BRP integration?

Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands, including the public sector. We always begin with a thorough analysis of your existing systems, processes and authorisation decision: a BRP integration must not only be technically sound, but also fit within the legal framework and the way you work.

For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage it. No black box, but transparent code and clear agreements on monitoring, certificate management and alerting.

You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also take a look at our broader services around custom software, software for municipalities and related government integrations such as the BAG API integration, StUF integration and DigiD integration.

  • Experience with the Haal Centraal BRP Bevragen API and StUF-BG
  • Familiar with PKIoverheid, OAuth 2.0 and Diginetwerk
  • Works with data minimisation within your authorisation decision
  • Secure by default: certificate rotation, scoped permissions, no PII in logs
  • Structured error handling and retry mechanisms
  • Comprehensive, traceable logging and monitoring from day one
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Ongoing management and migration from StUF-BG to Haal Centraal
  • An approach tailored to your existing IT landscape

Security and privacy in BRP integrations

Personal data from the BRP is among the most sensitive data you can process, which is why access is strictly regulated. Queries are only permitted within your BRP authorisation decision and your public task, following the principle of data minimisation: only the fields you truly need. The Haal Centraal BRP Bevragen API requires a PKIoverheid certificate (mTLS), OAuth 2.0 authentication and traffic over Diginetwerk, and uses the POST method so that no personal data ends up in URLs or server logs. On top of that, Appfront builds in line with OWASP ASVS.

The difference between the modern and the legacy route is also a security choice. The Haal Centraal BRP Bevragen API is designed around data minimisation and modern authentication; the legacy StUF-BG (LO GBA) works with SOAP/XML and has a different security model. For every query we document the legal basis, the fields requested and the data flows, and we keep traceable audit logs, so that your record of processing activities is complete and you can demonstrably comply with the GDPR. The application for the authorisation decision itself goes through the RvIG (the Dutch National Office for Identity Data); we build and maintain the integration within those frameworks.

More on related government integrations: DigiKoppeling and AI for municipalities and government. Questions about your specific situation? Get in touch.

  • Querying within your BRP authorisation decision and public task
  • Data minimisation: only the fields that are necessary
  • PKIoverheid certificate (mTLS) and OAuth 2.0
  • Traffic over Diginetwerk, no PII in URLs or logs
  • Traceable audit logs with the legal basis per query
  • Encryption in transit (TLS 1.2+) and at rest
  • Secrets and certificate management following best practices
  • Documentation for your record of processing activities

Frequently asked questions about BRP integrations

Answers to the questions we get asked most often about BRP integrations.

A BRP integration is a technical link between your application and the Basisregistratie Personen (the Dutch personal records database), managed by the RvIG. Through the modern Haal Centraal BRP Bevragen API (REST/JSON) or the legacy StUF-BG / LO GBA, your system queries current personal data at the source, such as name and address details, marital status, partners, children, parents and nationality. The BRP API deliberately uses the POST method instead of GET, so that no personal data ends up in the request URL and server logs. An integration can be limited (looking up one person by BSN) or broader (searching, residence history and occupancy).

The Haal Centraal BRP Bevragen API is the modern route: a RESTful API with JSON, an OpenAPI specification and data minimisation, so you only request the fields you need. StUF-BG (based on LO GBA) is the legacy standard with SOAP/XML messages that is still used in many existing municipal and public-sector systems. If you are building something new, we almost always recommend the Haal Centraal route. If you have existing StUF components, we either integrate with them or build a bridge to the modern API. In an intake session we work out together which route suits your landscape and authorisation decision.

Via the BRP API you can retrieve, among other things, name and address details, date of birth, BSN (citizen service number), marital status, partner, child and parent details, nationality and place of residence, plus historical data via residence history and occupancy. The API also provides derived information products such as addressing (salutation and address lines), parental authority, age, full name and initials. Which fields you are actually allowed to request is limited by your BRP authorisation decision and the principle of data minimisation: you only get access to the data needed for your statutory task.

For the modern route, we work with the Haal Centraal BRP Bevragen API: REST, JSON and an OpenAPI 3.0 specification, with OAuth 2.0 (client credentials), a PKIoverheid certificate (mTLS) and a connection via Diginetwerk. For legacy, we integrate via StUF-BG (SOAP/XML, LO GBA). We build the backend in the stack that suits you: Node.js, Python, PHP, .NET, Java or Go. We set up structured logging, retry mechanisms and monitoring so that queries run reliably even at peak volumes.

The cost depends on the chosen route (Haal Centraal or StUF-BG), the number of systems to integrate, the queries and information products required, and the amount of custom work in the business logic and error handling. Setting up PKIoverheid certificates, the Diginetwerk connection and ongoing maintenance also play a part. We always provide a clear quote after a no-obligation analysis of your situation and authorisation decision.

Personal data from the BRP is highly sensitive, so security and privacy are central. The BRP API requires a PKIoverheid certificate (mTLS), OAuth 2.0 authentication and traffic over Diginetwerk; because of the POST method, no personal data ends up in URLs or logs. Appfront builds according to the principle of data minimisation — only the fields that fall within your authorisation decision and public task — and in line with OWASP ASVS. We record audit logs and data flows so that your record of processing activities is complete and you can demonstrably comply with the GDPR.

Yes. Appfront regularly takes over the management of existing BRP and StUF-BG integrations, even if they were originally set up by another party. We review the queries, certificate configuration, error handling and authorisation settings, document the current setup and draw up improvement proposals. From that point on we handle changes, extensions and monitoring — including timely rotation of PKIoverheid certificates and migration from StUF-BG to the modern Haal Centraal route where that makes sense.

A BRP integration is only permitted for organisations with a public task and a BRP authorisation decision from the RvIG (the Dutch National Office for Identity Data). Think of municipalities, health insurers, pension funds and implementing bodies that need up-to-date name, address and civil status data for their processes and services. If you do not yet have an authorisation decision, we can help with the technical preparation, but the application and granting go through the RvIG. We build and manage the integration within the limits set by your decision.

Ready to build your BRP integration?

Tell us which personal data you want to query, which route suits you (Haal Centraal or StUF-BG) and which authorisation decision you hold. We are happy to advise on architecture, PKIoverheid, data minimisation and maintenance. A no-obligation first conversation will give you a clear picture of the options within half an hour.

Edit content