Secure transport according to the education standard One connection for multiple chain partners Messages that arrive and are confirmed

Custom Edukoppeling development

Appfront builds integrations according to Edukoppeling, the standard for the secure transport of messages in education. Edukoppeling governs how the systems of schools, implementing organisations and suppliers exchange messages securely and predictably, and is based on the Digikoppeling government standard. We make sure your system connects in line with the standard, so that the messages themselves arrive correctly.

What is an integration according to Edukoppeling?

Edukoppeling is a standard that prescribes how educational organisations, public implementing organisations, suppliers and other chain partners set up their data exchange. It concerns the transport of messages, not their content: how a message travels securely from one system to another, how the parties identify each other, and how it is established that the message has arrived. Edukoppeling is based on Digikoppeling profiles and is maintained by Edustandaard.

Anyone who wants to exchange messages with parties in education deals with two layers: the content, such as data on pupils, enrolments or results, and the transport. Without a solid transport layer, every integration builds its own security and error handling, and every new partner has to be connected from scratch. A message that doesn't arrive is only noticed late.

We build custom because parties differ: which messages you exchange and with whom, which version of the standard your partners use, and how your own system is built. The standard is maintained by Edustandaard; we make sure your system connects in line with it. Which content agreements apply to your messages is set out in the standards for those messages.

According to the standard

Transport, security and addressing as Edukoppeling prescribes them, based on Digikoppeling.

One connection

The same transport layer for all chain partners, so a new partner is connected quickly.

Arrived and confirmed

Every message with a confirmation, and errors that are detected and handled.

How we build your Edukoppeling integration

We start with your message traffic: which messages, with which parties, which version of the standard, and how things work now. There are often existing integrations with their own transport. We map them out so they can be moved to Edukoppeling one by one, without the content of the messages having to change.

1
Mapping message traffic

Your messages, partners, versions and current integrations.

2
Building the transport

Transport, security and addressing according to Edukoppeling.

3
Testing with partners

Testing with chain partners, and message validation.

4
Go-live and maintenance

Go-live, monitoring, and maintenance when new versions arrive.

What an Edukoppeling integration actually does

The components below appear in almost every Edukoppeling integration. Which ones you need depends on your messages.

Transport

Messages in line with the transaction standard.

Security

Identification and encryption using certificates.

Addressing

Organisations addressed unambiguously.

Confirmation

Receipt confirmed, per message.

Errors

Detected, reported and resolved.

Log

Every message recorded.

Who we build an Edukoppeling integration for

The integration is intended for parties that exchange messages in education.

Software suppliers

A product for schools. The connection is the core.

School boards

Custom systems alongside packages. One transport layer matters most.

Public implementing bodies

Messaging with many schools. Confirmation is what you need.

Chain partners

Publishers and service providers. The standard is the core.

Technology and integrations

This page is about Edukoppeling integrations. For the government standard it is based on, see our page on a Digikoppeling integration, for school operations see our page on an education ERP, and for higher education see our page on a student information system. You can read about our approach at building software.

If you want to exchange enrolments, results and diplomas from your own administration system with DUO's Register Onderwijsdeelnemers (ROD, formerly BRON), take a look at our BRON and ROD integration.

Edukoppeling Transaction standard Digikoppeling profiles Certificates Organisation addressing Receipt confirmation Error handling Multiple versions Testing with chain partners Log per message

Why Appfront for your Edukoppeling integration?

A message containing pupil data that doesn't arrive, or reaches the wrong party, is more than a technical error. That's what we build around: transport in line with the standard, one connection for all partners, and messages that arrive and are confirmed.

Secure

Security as the standard requires.

Faster onboarding

A new partner on the same layer.

Reliably delivered

Every message with confirmation.

Security and privacy in an Edukoppeling integration

The integration often carries personal data of pupils and students. Messages are encrypted, parties recognise each other using certificates, and every message is logged. Only the data needed for the exchange is included.

The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.

Frequently asked questions about an Edukoppeling integration

Questions education parties ask before getting started.

A standard for the secure transport of messages between educational organisations, implementing bodies, suppliers and other chain partners. It governs how a message arrives securely and predictably, not what it contains. Edukoppeling is managed by Edustandaard.

Edukoppeling is an education variant of Digikoppeling, the government standard for messaging between organisations. It is entirely based on Digikoppeling profiles, with additional agreements needed for education.

No. The content, such as data about pupils, enrolments or results, follows its own agreements and standards. Edukoppeling is the layer underneath. An integration uses both: the content agreement for what is in the message, and Edukoppeling for the transport. We build the transport and embed the content messages you already exchange within it.

That depends on what your partners support. There are several versions of the transaction standard, and not everyone switches at the same time. In the first step we map out which versions are needed, so the integration can communicate with everyone.

The integration expects a confirmation. If none arrives, the message is retried or queued for review, and the administrator receives a notification. The log shows what happened to each message.

On the same transport layer. A new partner gets an address and certificates, testing takes place, and then the messages start flowing. Because the transport layer is already in place, this is faster than building a new integration from scratch. A new type of message with an existing partner can also use the same connection, without having to set up security again.

For education software suppliers that exchange messages with chain partners, for school boards and institutions with their own systems, and for implementing bodies and chain partners that exchange many messages with education.

Messages that arrive securely?

Tell us which messages you exchange, with which parties and how that currently works. We'll show you what the integration looks like under Edukoppeling.

Edit content