Custom Haal Centraal integration development
Appfront builds custom Haal Centraal integrations that let you query the basic registers in real time — from your case management system, forms module or your own application. Through the uniform REST/JSON query APIs of VNG, RvIG and the Kadaster, you retrieve up-to-date personal, address or company data straight from the source, at the moment you need it. No more maintaining your own copies, fewer typing errors and demonstrably current data in every process.
What is Haal Centraal?
Haal Centraal is the initiative by VNG, RvIG and the Kadaster to query basic registers through uniform, modern REST/JSON APIs, rather than through bulk delivery or local copies. The principle: when you need a data item, you retrieve a targeted answer from the source register, so you always work with current data. The Haal Centraal programme has since been completed; the APIs are now managed by RvIG (BRP) and the Kadaster (BAG, BRK, WOZ).
The best-known query APIs are BRP Bevragen (current persons, partners, parents and children from the Personal Records Database, including the Register of Non-Residents), BAG (addresses and buildings), BRK (cadastral data) and HR Bevragen (commercial register/company data). An important distinction: with Haal Centraal you query existing basic registers — you do not use it to keep a register yourself. In practice, a custom integration means calling the right APIs with the right authorisation, processing the JSON response in your own screens or processes, and requesting only the data you have a legal basis for.
Appfront builds to the official API specifications of VNG Haal Centraal and the applicable government API standards (REST API Design Rules, Dutch API Strategy). We tailor authorisation, error handling and logging to your actual processes, so the integration keeps pace with new API versions and stays reliable even at peak volumes. This fits in with our broader software for municipalities.
Real time from the source
No more outdated copies: you query the BRP, BAG or BRK at the moment you need the data and get the current answer back from the source register. Register once, use many times — fewer errors and less retyping.
Uniform REST/JSON APIs
All Haal Centraal APIs follow the same modern approach: REST, JSON and published OpenAPI specifications. One way of building for BRP, BAG, BRK and HR, so adding further registers to your integration later is straightforward.
Controlled authorisation
Access runs through OAuth 2.0 / OpenID Connect and usually an API gateway, with every query logged. You only request data you have a legal basis for, recorded traceably for your register of processing activities.
Our development process for Haal Centraal integrations
We work to a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your processes, required registers and authorisation through to go-live and ongoing maintenance, every step is aimed at an integration your own organisation can understand, manage and account for.
We map out which registers you want to query (BRP, BAG, BRK, HR), which data you need, which legal basis applies and which screens or processes the responses need to land in.
We design the integration architecture, set up authorisation via OAuth 2.0 / OpenID Connect and an API gateway, and draw up a strategy for error handling and logging.
Implementation against the Haal Centraal test environment, with automated tests, structured logging and monitoring. You see working versions along the way.
Controlled connection to the production environment with validation and a safety net, followed by ongoing maintenance, monitoring and keeping pace with new API versions.
What a Haal Centraal integration delivers in practice
Every Haal Centraal integration is tailored to your processes, the registers you are permitted to query and your existing applications. Below are the features we deliver most often for municipalities and public-sector organisations that want to consult the key registers in real time.
BRP queries (persons)
Up-to-date personal data (name and address, partner, parents and children) straight from the Personal Records Database (BRP), including the Register of Non-Residents (RNI). Your case management system or form fills in the data automatically based on a BSN or search query, with no retyping. See also our BRP integration.
BAG address validation
Validate and enrich addresses and buildings against the Register of Addresses and Buildings (BAG). An entered address is checked, completed and linked to the correct residential unit and building data, meaning fewer errors in applications and correspondence.
BRK and HR queries
Retrieve land registry data via BRK queries and business/trade register data via HR queries. This lets you consult ownership and company information within the same integration platform whenever your process requires it, using the same authorisation approach.
Authorisation via gateway
Central authorisation and access management through an API gateway and identity provider, using OAuth 2.0 / OpenID Connect tokens. Which queries and fields are permitted is enforced per user and per register.
Logging and traceability
Every query is logged traceably: who requested what, when and on what legal basis. This keeps your register of processing activities complete, supports audits and makes it demonstrable that only authorised data was requested.
Processing in your own screens
The JSON responses are processed cleanly in your existing case management system, forms or web application, with error handling, retries and clear messages when the source is temporarily unavailable. See also our custom software.
Typical use cases in practice
A Haal Centraal integration turns out differently for each organisation. We see a number of patterns come up often at municipalities and public-sector organisations, and for each of them we have a working setup that pays attention to the right register, authorisation and processing.
Case management and service delivery
Municipalities that retrieve current name, address and residence (NAW) data from the BRP (Personal Records Database) directly when an application or notification is submitted, so that officials don't have to retype it and applicants don't have to enter their details twice. See also our municipality website and ZGW API integration.
Online forms & e-services
Application forms for permits, benefits or subsidies that validate an address against the BAG (Addresses and Buildings Register) and pre-fill personal details from the BRP. This reduces drop-out, prevents errors and speeds up processing. See also our BAG API integration.
Implementing organisations
Implementing organisations that need up-to-date personal or company data in their processes, for example for checks, awarding decisions or correspondence. Instead of maintaining their own copy of the data, they query the source at the right moment, with logging and a legal basis recorded for each request.
Address & company checks
Processes that require cadastral or Chamber of Commerce data, such as verifying ownership via the BRK (Land Registry) or verifying a business via HR Bevragen. The integration consults the relevant register and processes the response with the same authorisation and logging as all other queries.
Technology we use
We build Haal Centraal integrations against the official REST/JSON query APIs and their OpenAPI specifications, combined with the backend stack that suits you. The exact choice depends on which registers you query and which authorisation and gateway set-up you use, so that your own team can manage and further develop the integration.
If you also want to integrate with other APIs that publish their contract as an OpenAPI specification, take a look at our OpenAPI integration.
For income data from the Basisregistratie Inkomen (Basic Income Register), see our page on a BRI integration.
Why choose Appfront for your Haal Centraal integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands, including in the public sector. We always start with a thorough analysis of your existing systems, processes and legal bases. An integration must not only be technically correct, but also fit within your legal frameworks and way of working.
For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.
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 for the public sector: software for municipalities, AI for municipalities and water authority software. Questions about your situation? Get in touch.
- Experience with the Haal Centraal query APIs (BRP, BAG, BRK, HR)
- Familiar with government API standards (REST API Design Rules, Dutch API Strategy)
- Authorisation via OAuth 2.0 / OpenID Connect and an API gateway
- Attention to legal basis, data minimisation and traceable logging
- Structured error handling and retry mechanisms
- Extensive 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 maintenance and keeping pace with new API versions
- An approach tailored to your existing IT landscape
Security and privacy in Haal Centraal integrations
Querying basic registrations almost always involves personal data, especially with the BRP (Personal Records Database). Appfront therefore builds according to data minimisation and the OWASP ASVS: only requesting the fields you have a legal basis for, authorisation via OAuth 2.0 / OpenID Connect and an API gateway, secure connections and traceable logging of every query. This way, the integration meets government information security frameworks.
We document the data flows, the authorisation set-up and the legal basis for each query, so that your processing register is complete and you demonstrably comply with the GDPR. The logging of every request (who, what, when and on what legal basis) serves as accountability towards supervisory authorities and during audits.
More about our public sector expertise: software for municipalities and custom software.
- GDPR-compliant querying with data minimisation and legal basis
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable data flows
- Automatic retry and dead-letter queues
- Monitoring and alerting for anomalies
- Secrets management following best practices
- Documentation and logging for your processing register
Frequently asked questions about Haal Centraal integrations
Answers to the questions we are asked most often about Haal Centraal integrations.
A Haal Centraal integration is a technical integration between your application, such as a case management system, forms module or custom web application, and the government's Haal Centraal query APIs. Through these standardised REST/JSON APIs you query the base registries in real time (BRP Bevragen for personal records, BAG for addresses and buildings, BRK for land registry data). This means you retrieve up-to-date data at the moment you need it, instead of maintaining your own copy. The integration handles authorisation, the API calls and the processing of the JSON response in your own screens or processes.
Haal Centraal is explicitly designed for querying existing base registries, not for maintaining one yourself. You don't build a copy of the BRP or the BAG; instead, you ask the source registry a targeted question at the right moment and get the current answer back. This reduces the risk of outdated or incorrect data and fits the principle of 'register once, use many times'. Bulk delivery or locally synchronising entire registries is a different approach; Haal Centraal deliberately opts for real-time querying via APIs.
The Haal Centraal initiative provides query APIs for several base registries. The best known are BRP Bevragen (current personal data from the Personal Records Database, including RNI), BAG (addresses and buildings) and BRK (land registry data); WOZ (property valuation) queries also fall under this. There is also HR Bevragen for business register and company data. Which APIs are relevant for you depends on your process, so together we determine which registries you need and which data you are permitted to retrieve from them.
Access to the Haal Centraal APIs runs through controlled authorisation. In practice, this means OAuth 2.0 and OpenID Connect via an identity provider, often combined with an API gateway that handles central authorisation and access management for the municipality. On top of that, government requirements for secure messaging apply, such as secure connections and logging. Each registration also has a legal basis: you may only request the data for which you have a statutory task and authorisation. We set up the integration so that only permitted fields and queries are possible.
The cost depends on the number of APIs to be integrated (BRP, BAG, BRK, HR), the complexity of your authorisation and gateway setup, the amount of custom work in your own screens or processes, and the logging and monitoring you require. Whether you connect to a test or production environment and which Identity Provider you use also play a role. We always provide a clear quote after a no-obligation analysis of your situation.
Yes, provided it is set up carefully. Personal data from the BRP is highly sensitive, so we build according to data minimisation: only requesting the fields you actually need, on the basis of a valid legal ground. We document the data flows so that your record of processing activities is complete, set up logging so that queries are traceable, and align authorisation with your statutory task. This way you demonstrably comply with the GDPR and with the government's information security frameworks.
Yes. Appfront regularly takes over the management of existing government integrations, even if they were originally set up by another party. We review the API calls, the authorisation and gateway configuration, the error handling and the logging, document the current setup and draw up improvement proposals. From that point on, we can handle changes, extensions to additional registries and monitoring, including keeping pace with new API versions.
Haal Centraal is intended for municipalities and implementing organisations that need up-to-date personal, address or company data in their processes. Think of a case management system that retrieves current name and address details from the BRP as soon as an application comes in, a form that validates an address against the BAG, or a process that consults land registry or business register data. Wherever you currently maintain your own copy or retype data by hand, a Haal Centraal integration can make it current and reliable.
Ready to build your Haal Centraal integration?
Tell us which base registers you want to query — BRP, BAG, BRK or HR — and which case management system or application the data needs to end up in. We are happy to help you think through authorisation, legal basis, logging and connecting to the test and production environments. In a no-obligation first conversation you will get a clear picture of what is possible. Schedule a call now.