Logius standard WUS & ebMS2 PKIoverheid & OIN

Custom DigiKoppeling integration development

Appfront builds custom DigiKoppeling integrations that let your government system exchange messages securely and reliably with other government bodies and national services. We set up the interface according to the Logius standard — WUS for synchronous request-response, ebMS2 for reliable asynchronous transport — using PKIoverheid certificates and the OIN. DigiKoppeling handles the secure transport: you decide the content of the message.

What is a DigiKoppeling integration?

DigiKoppeling is the Logius standard for secure, reliable message exchange between government organisations. The standard contains the logistical agreements for electronic messaging: how a message is packaged, addressed, secured and delivered. The key point to remember: DigiKoppeling governs the transport and the interface — not the content of the message. Which data a message contains is determined by a content standard such as StUF or a ZGW API.

The standard has two interface profiles. WUS, based on SOAP and WS-Security, is used for synchronous request-response: you ask a question and get an answer straight away. ebMS2 (ebXML Messaging Service) is geared towards reliable asynchronous transport, where a message is guaranteed to be delivered exactly once — also suitable for large messages and attachments. Authentication and encryption run via PKIoverheid certificates; organisations are identified by their OIN (Organisation Identification Number).

Appfront builds according to the official Logius documentation for DigiKoppeling and the OWASP ASVS security standard. Together with you, we choose the right interface for the service you want to exchange data with, and we set up certificates, error handling and logging so that message traffic stays reliable and traceable, even at peak volumes.

Secure transport, not the content

DigiKoppeling is the digital envelope: it packages, secures and delivers the message between government bodies. What goes inside the envelope — for example a StUF or ZGW message — is determined by a separate content standard. This keeps transport separate from content.

Two profiles: WUS and ebMS2

WUS (SOAP/WS-Security) for synchronous request-response, where you get an answer immediately. ebMS2 for reliable asynchronous transport with guaranteed, exactly-once delivery — also for large messages and attachments. We choose the profile that suits your service.

€

PKIoverheid and OIN

Messages are encrypted and signed with PKIoverheid certificates, and parties authenticate each other mutually. Each organisation identifies itself with its OIN. This way you know for certain who you are exchanging data with, and traffic remains confidential and traceable.

Our development process for DigiKoppeling integrations

We follow a proven methodology that removes uncertainty early and delivers a stable interface. From an initial analysis of the service you want to exchange data with and the right interface profile, through to go-live and ongoing maintenance — every step is aimed at an integration your team can understand and trust.

1
Analysis and interface selection

We map out which service or chain you want to exchange data with, which messages are involved, and whether WUS (synchronous) or ebMS2 (asynchronous) is the right fit. We also look at which content standard and which OIN apply.

2
Architecture and certificates

We design the interface, arrange the PKIoverheid certificates and OIN configuration, choose the mutual TLS setup, and draw up an error-handling and logging strategy.

3
Development & testing

Implementation with automated tests, structured logging and monitoring, with conformance and chain tests against the service. You see working integrations along the way.

4
Connection and maintenance

A controlled connection to the production environment with validation and a safety net, followed by ongoing maintenance — including timely certificate renewal and further development.

What a DigiKoppeling integration delivers in practice

Every DigiKoppeling integration is set up specifically for the service you exchange data with, the chosen interface profile and your neighbouring systems. Below are the features we deliver most often for government organisations and suppliers who want to exchange messages securely.

WUS interface (synchronous)

A SOAP interface with WS-Security for synchronous request-response: your system puts a question to a service and gets a structured answer straight back. Suitable for retrieving data in real time from registers and national services.

ebMS2 interface (asynchronous)

An ebXML Messaging Service interface for reliable asynchronous transport, with guaranteed, exactly-once delivery — even if the recipient is temporarily unavailable. Suitable for reporting events, chain-wide data exchange and sending large messages and attachments.

Certificate and OIN management

Setting up PKIoverheid certificates for encryption and signing, two-way TLS authentication and correct registration of the OIN. Includes monitoring of validity periods, so expiring certificates are renewed in good time and traffic never grinds to a halt.

Connecting to services

Integration with national services and chains such as the Basic Registration of Persons (BRP), Digilevering and Suwinet. We handle the connection procedure, the conformity and chain tests, and the setup in your acceptance and production environments.

Large messages and attachments

For messages too large for regular transport, we set up the Large Messages profile: the message refers to a separate file that is retrieved securely. This lets you send bulky attachments reliably without overloading the message flow.

Logging and monitoring

Full logging of message traffic with traceable data flows, status monitoring and alerting on deviations or failed deliveries. Your operations team can see at once whether messages have been processed correctly, and every exchange remains traceable for audits.

Typical use cases in practice

A DigiKoppeling integration turns out differently for each organisation and each service. We see a number of patterns come up again and again — and for each of them we have a working set-up, with attention to the right interface profile, the certificates and the content standard carried in the message.

CRM

Interface between government systems

Municipalities, provinces and implementing bodies that want their case management system, BRP service or line-of-business application to communicate securely with other government systems. DigiKoppeling provides the secure interface; the content travels via standards such as StUF or a ZGW API. Relevant for software for municipalities.

Connecting to national services

Organisations that want to connect to national services such as the Personal Records Database (BRP), Digilevering or Suwinet. We take care of the interface, the PKIoverheid certificates, the OIN and the conformance tests, so you can retrieve or receive data reliably.

Data exchange in chains

Partnerships and chain partners — in the social domain or in permit processing, for example — that exchange messages in a structured way. ebMS2 ensures reliable, guaranteed delivery between parties, including for larger messages and attachments.

Suppliers of government software

Software suppliers who need to make their product DigiKoppeling-compliant so it can be used by government bodies. We build a reusable WUS and ebMS2 interface into your application, so your customers can connect without custom work per organisation. See also our ZGW API integration and StUF integration.

Technology we use

We build DigiKoppeling integrations according to the official Logius interface standards, combined with the backend stack that suits you. The exact implementation depends on the chosen profile and the service you exchange data with — so that your own team can manage or further develop the interface.

For messaging in education there is a dedicated variant of this standard; see our page on Edukoppeling.

DigiKoppeling WUS DigiKoppeling ebMS2 Large Messages Profile SOAP / WSDL WS-Security & WS-Addressing ebXML Messaging Service PKIoverheid certificates Two-way TLS OIN / COR XML & XSD validation StUF & ZGW message content Java / .NET / Node.js / Python DigiKoppeling adapters Logging & monitoring Conformity & chain tests Acceptance & production connection

Why Appfront for your DigiKoppeling integration?

Appfront has extensive experience building integrations for public sector organisations in the Netherlands. We always start with a thorough analysis of the existing systems, the service you want to exchange data with and the chosen interface profile — an integration must not only be technically correct according to the standard, but also work in practice within your organisation.

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.

Take a look at our wider services around software for municipalities, municipality websites and custom software. Would you like to talk through your situation? Get in touch for a no-obligation conversation.

  • Experience with the DigiKoppeling interface standards WUS and ebMS2
  • Familiar with PKIoverheid certificates, OIN and mutual TLS
  • Knowledge of content standards such as StUF and the ZGW APIs
  • Secure by default — certificates in vaults, strict permissions per integration
  • Structured error handling and reliable delivery
  • 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, including timely certificate renewal
  • An approach tailored to your existing government IT landscape

Security and privacy in DigiKoppeling integrations

Messages between government bodies almost always contain personal data or confidential information. DigiKoppeling is designed specifically for this: messages are encrypted and signed with PKIoverheid certificates, and parties authenticate each other mutually via their OIN. On top of that, Appfront builds in line with the OWASP ASVS: certificates in secure vaults, strict permissions per integration and full logging of message traffic.

Because DigiKoppeling handles the transport and not the content, we align data processing with the content standard and the purpose of the exchange. We document the data flows, certificates and OIN configuration so that your record of processing activities is complete and you can demonstrably comply with the GDPR. The logging serves as traceable evidence of every exchange.

Want to talk through a secure connection? Get in touch — we are happy to think along about your specific situation.

  • Encryption and signing with PKIoverheid certificates
  • Mutual authentication via OIN and mutual TLS
  • GDPR-compliant data processing and minimisation
  • Role-based access and least-privilege principles
  • Full logging with traceable data flows
  • Reliable delivery with monitoring and alerting
  • Certificate and secrets management following best practices
  • Documentation for your record of processing activities

Frequently asked questions about DigiKoppeling integrations

Answers to the questions we are asked most often about DigiKoppeling connections.

A DigiKoppeling integration is the technical interface that allows your system to exchange messages securely and reliably with other government systems. DigiKoppeling is the Logius standard that governs the logistical arrangements: how a message is packaged, addressed, secured and delivered. It therefore covers the transport, not the content of the message. There are two interface standards: WUS for synchronous request-response and ebMS2 for reliable asynchronous transport of, among other things, large messages and attachments. Authentication and encryption run via PKIoverheid certificates, and organisations are identified by their OIN.

WUS and ebMS2 are the two interface profiles of DigiKoppeling. WUS is based on SOAP and WS-Security and is used for synchronous request-response: you send a request and get an immediate reply, for example when retrieving data. ebMS2 (ebXML Messaging Service) focuses on reliable asynchronous transport, where the message is guaranteed to be delivered exactly once, even if the recipient is unavailable at that moment. ebMS2 is often used for reporting events, sending large messages and attachments, and chain-wide data exchange. Which profile is suitable depends on the service you are connecting to.

DigiKoppeling has been on Forum Standaardisatie's 'comply or explain' list since 2009. This means government organisations must apply the standard for digital data exchange that forms part of the Generieke Digitale Infrastructuur (the Dutch national digital infrastructure) — including basic registers — or that spans multiple sectors, whenever two-way authentication between systems is required. If you deviate, the 'explain' principle applies and you must justify your choice. We help you choose the right interface that fits the service you want to exchange data with.

We build to the official Logius interface standards: WUS, based on SOAP, WSDL and WS-Security, for synchronous traffic, and ebMS2 (ebXML Messaging Service) for reliable asynchronous transport. For large messages and attachments we use the Large Messages profile (Grote Berichten). Authentication and encryption run via PKIoverheid certificates and two-way TLS; we identify organisations using the OIN from the COR. We implement the integration in the backend stack that suits you — Java, .NET, Node.js or Python — optionally using an existing DigiKoppeling adapter.

The cost is determined by the number and type of interfaces (WUS, ebMS2 or both), the services you connect to, the complexity of message processing on your side, and the set-up of certificates and monitoring. Ongoing maintenance, timely renewal of PKIoverheid certificates and support also affect the total investment. We always provide a clear quote after a no-obligation analysis of your situation.

Yes. DigiKoppeling was designed specifically for secure exchange between government bodies: messages are encrypted and signed with PKIoverheid certificates, and parties authenticate each other two-way via their OIN. Appfront builds on top of this in line with OWASP ASVS and applicable government standards: certificates in secure vaults, strict permissions per integration and full logging of message traffic. We document the data flows so your record of processing activities stays complete and you can demonstrably comply with the GDPR.

Yes. Appfront regularly takes over the maintenance of existing integrations, even when they were originally set up by another party. We review the WUS and ebMS2 interfaces, the certificate and OIN configuration, error handling and logging, document the current set-up and draw up improvement proposals. From that point on, we can handle changes, extensions and monitoring — including timely renewal of expiring PKIoverheid certificates.

DigiKoppeling is the transport mechanism underlying many national services and chains. Among other things, you can use it to connect to the Basisregistratie Personen (BRP, the Dutch personal records database) and Digilevering, and it is used for data exchange in chains such as Suwinet. The message content you send — for example StUF or ZGW messages — is separate from DigiKoppeling: DigiKoppeling handles secure transport, while the content standard determines what is in the message. We help you set up both the right interface and the corresponding content standard correctly.

Ready to build your DigiKoppeling integration?

Tell us which service or chain you want to exchange data with and which messages are involved. We're happy to help you think through the right interface (WUS or ebMS2), the certificates and the connection procedure. A no-obligation first conversation will give you a clear picture of the options within half an hour. Also see our DigiD integration and Suwinet integration.

Edit content