Custom NLX/FSC integration development
Appfront builds custom NLX/FSC integrations for secure API traffic within Common Ground. NLX has evolved into the FSC standard (Federated Service Connectivity) for federated, logged and authorised API traffic between government organisations. We set up the inway, outway, manager and contracts in line with the NL profile, with PKIoverheid certificates, mTLS and transaction logging, so you query data at the source instead of copying it.
What is an NLX/FSC integration?
NLX originated within the VNG Common Ground programme as an open source component for handling API traffic between (government) organisations in a federated, logged and authorised way. The approach behind NLX has since been developed into a formal standard: Federated Service Connectivity (FSC), adopted in December 2024 by the Programmeringsraad GDI. NLX has not disappeared; it lives on as the reference implementation of FSC. In practice, the community speaks of NLX/FSC: NLX as the working software, FSC as the agreements an implementation must meet.
An FSC/NLX integration lets organisations find, offer and query each other's REST APIs securely without data being copied centrally. Each participant (peer) runs an outway for outgoing traffic, an inway for incoming traffic and a manager that handles contracts and authorisations; a directory registers the connected organisations and their services. Access to a service runs through a contract with a service connection grant, and all traffic is logged per transaction. This way, the integration fits the Common Ground principle: query data at the source.
Appfront builds on the official FSC/NLX documentation and the Dutch profile for government implementations. Because the standard is still evolving, with extensions for logging, policy and control under way, we follow the current publications from Logius and VNG and are honest about what is already settled and what is still being worked out. We align the setup, certificate management and error handling with your existing landscape.
Federated, not centralised
No central data store: each organisation keeps its own data and makes it available through its own inway. Other participants query that service directly at the source, within a shared trust network of peers.
Authorised through contracts
Access to a service only exists after an explicit contract with a service connection grant. Only authorised peers may query a specific API, managed through the manager, with delegation where an intermediary acts on behalf of an organisation.
Logged and traceable
Every data exchange gets a uniform log record with a unique transaction ID through the logging extension. This makes it traceable per integration who requested what and when, which is mandatory as soon as FSC is used in a Digikoppeling context.
Our development process for NLX/FSC integrations
We work with a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of the APIs to be exposed or queried and the right FSC profile through to go-live and ongoing maintenance, every step is aimed at an integration your own team can understand and trust.
We map out which APIs you want to offer or query, which peers you will connect with, which FSC profile fits, and how the integration relates to existing Digikoppeling traffic and your source registrations.
We design the setup of the inway, outway, manager and directory, arrange PKIoverheid certificates and trust anchors for mTLS, and draw up a logging and error-handling strategy.
Implementation and configuration with contracts and grants, automated tests against the FSC test suite, structured transaction logging and monitoring. You see working integrations along the way.
A controlled go-live with validation of contracts and certificates and a safety net, followed by ongoing maintenance, certificate rotation and further development.
What an NLX/FSC integration delivers in practice
Every FSC/NLX integration is set up specifically for the APIs you offer or query, your source registrations and the peers you work with. Below are the features we deliver most often for organisations putting Common Ground into practice.
Inway for your own APIs
We place an inway in front of your existing REST API or source registration, so that other authorised organisations can query that service securely. The inway validates, logs and routes incoming traffic without you having to rebuild your underlying application.
Outway for outgoing traffic
An outway lets your applications query other peers' APIs as if they were local endpoints. The outway handles mTLS, selects the right contract and logs every call, so your developers can focus on functionality instead of integration mechanics.
Managing contracts and grants
Through the manager, we set up contracts with service connection grants: who may query which service, and under what conditions. This includes delegation where an intermediary publishes or consumes an API on behalf of an organisation, so that partnerships are properly arranged.
PKIoverheid and mTLS
Setting up mutual TLS between managers, inways and outways using X.509 certificates. In a government context this is based on PKIoverheid certificates and an agreed set of certificate authorities (trust anchors), including timely rotation so that connections stay reliable.
Transaction logging
The logging extension writes a uniform log record with a unique transaction ID for each exchange, so every call is traceable. We set up logging in line with the Dutch profile and connect it to your existing logging facilities for oversight and accountability.
Connecting to Digikoppeling
FSC is included in the Digikoppeling REST API profile. We help you determine how your FSC integration relates to classic Digikoppeling messaging and, where needed, set up both so that they complement each other within your landscape.
Typical use cases in practice
An FSC/NLX integration works out differently for every organisation. There are a number of contexts we see time and again, and for each of them we have an approach that pays attention to inway/outway setup, contracts and the requirements around certificates and logging.
Municipalities with Common Ground
Municipalities putting Common Ground into practice that want to query data at the source rather than copy it. An inway exposes a source registry or API; outways let internal applications query other registries securely. A good fit with software for municipalities and a modern municipality website.
Partnerships that share APIs
Regional partnerships, chain partners and joint arrangements that want to share APIs with one another. FSC uses contracts with grants to govern, per relationship, which organisation may query which service, including delegation when an implementing organisation acts on behalf of several parties.
Suppliers of Common Ground components
Software suppliers that build Common Ground components or want to make existing products FSC-compliant. We handle the inway/outway setup, the connection to the directory and validation against the FSC test suite, so that your component demonstrably meets the standard.
Implementing organisations and chain partners
Implementing organisations, water boards and housing associations that exchange data between chain systems with traceable logging. Think of a Haal Centraal integration or a ZGW API integration that is exposed in a federated way via FSC.
Technology we use
We build FSC/NLX integrations in line with the FSC standard and the NL profile, combined with the backend stack that suits you. The exact setup depends on your source registries, the peers you connect with and your certificate and logging facilities, so that your own team can manage and further develop the integration.
Why Appfront for your NLX/FSC integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes, because an integration must not only be technically sound but also add practical value to 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 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 around custom software, housing association software, custom water board software and AI for municipalities and government.
- Familiar with the FSC standard and NLX as the reference implementation
- Experience with inway, outway, manager and directory within Common Ground
- Well versed in contracts, grants and delegation between peers
- Secure by default: mTLS, PKIoverheid certificates and certificate rotation
- Transaction logging in line with the logging extension and the NL profile
- Insight into the relationship between FSC and Digikoppeling
- Clear documentation that your team can read and maintain
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
- An approach tailored to your existing government IT landscape
Security and privacy in NLX/FSC integrations
FSC/NLX integrations often expose personal data from source registers, so security and authorisation are central. Traffic between managers, inways and outways runs over mutual TLS (mTLS) with X.509 certificates. In a government context we use PKIoverheid certificates, and the components accept only the agreed certificate authorities (trust anchors), so every party knows exactly which peer it is connecting to. Access is only granted through a contract with a service connection grant.
The logging extension records a uniform log entry with a unique transaction ID for every transaction; in the Digikoppeling context, this logging is mandatory. We build according to data minimisation and least privilege, document the data flows, contracts and authorisations, and align the setup with the NL profile so that your processing register is complete and you demonstrably comply with the GDPR.
Not sure whether FSC, classic Digikoppeling messaging or a combination suits you best? Get in touch, we'd be happy to think it through with you.
- GDPR-compliant data processing and minimisation
- mTLS with X.509 and PKIoverheid certificates
- Trust anchors and strict peer validation
- Authorisation via contracts and service connection grants
- Transaction logging with a unique transaction ID
- Monitoring and alerting for anomalies
- Certificate management and timely rotation
- Documentation for your record of processing activities
Frequently asked questions about NLX/FSC integrations
Answers to the questions we get asked most often about NLX/FSC implementations.
NLX originated within the VNG Common Ground programme as an open source component for federated, logged and authorised API traffic between organisations. The approach behind NLX has grown into a standard: Federated Service Connectivity (FSC). NLX has not disappeared; it lives on as the reference implementation of that FSC standard. In practice, the community therefore usually talks about NLX/FSC: NLX as the working software, FSC as the agreements an implementation must meet. We build integrations that align with that current standard.
NLX as a standalone brand name has largely been absorbed into the FSC standard, which was adopted by the Programmeringsraad GDI (the Dutch government's Digital Government programming board) in December 2024. NLX itself has not been deprecated: its codebase is the reference implementation of FSC and is still being developed. For new projects we therefore always position on FSC, with NLX as the implementation. Because the standard is still evolving, with extensions for logging, policy and control under way, we follow the latest publications from Logius and VNG and phrase our choices cautiously wherever something is not yet final.
Digikoppeling is the broader family of interface standards for message exchange between government organisations. FSC is the Common Ground API layer, which has since been included in the Digikoppeling REST API interface standard profile. Whereas classic Digikoppeling message exchange is mainly about the reliable transport of messages, FSC/NLX focuses on exposing, discovering and authorising REST APIs in a federated way. In an integration project, we help you determine which profile fits and how FSC and Digikoppeling relate to each other in your specific situation. See also our page on Digikoppeling integrations.
An FSC/NLX environment consists of a number of fixed roles: an outway that proxies and logs outgoing API requests, an inway that validates and logs incoming requests and forwards them to the underlying API, a manager that handles contracts and authorisation requests, and a directory in which participating organisations (peers) and their services are registered. Access to a service is arranged through a contract with a service connection grant. We set up these components, connect them to your existing API or source register, and make sure the whole setup remains manageable.
Traffic between managers, inways and outways runs over mutual TLS (mTLS) with X.509 certificates. In the government context, PKIoverheid certificates are used for this, and the components only accept certificates from the agreed certificate authorities (trust anchors). This gives every party certainty about which peer it is connecting to. The FSC logging extension writes a uniform log record for each transaction with a unique transaction ID; in the Digikoppeling context, this logging is mandatory. We set up certificate management, trust anchors and transaction logging in line with the NL profile.
The cost depends on the complexity of the data flows, the number of APIs to be exposed or queried, the setup of the inway, outway, manager and directory, and the requirements around certificates, logging and authorisation. The connection to your existing source register or Common Ground components and ongoing maintenance also play a part. We always provide a clear quote after a no-obligation analysis of your situation and the desired FSC profile.
Yes, provided it is set up properly. Because FSC/NLX often exposes personal data from source registers, we build according to data minimisation and least privilege: only authorised peers get access to a specific service via a contract with a grant. mTLS with PKIoverheid certificates secures the transport, and transaction logging makes every data exchange traceable. We document the data flows, contracts and authorisations so that your record of processing activities is complete and you can demonstrably comply with the GDPR.
FSC/NLX suits municipalities and other government organisations putting Common Ground into practice and wanting to query data at the source rather than copy it. Collaborative partnerships that share APIs with one another, and suppliers who build or connect Common Ground components, also benefit from a correct FSC implementation. Not sure whether FSC, traditional Digikoppeling messaging or a combination fits best? We'll look at it with you in a no-obligation conversation.
Ready to build your NLX/FSC integration?
Tell us which APIs you want to offer or query and which peers you want to connect with within Common Ground. We're happy to advise on setting up the inway, outway, contracts, certificates and logging in line with the NL profile. A no-obligation initial conversation gives you a clear picture of the possibilities and how they relate to Digikoppeling.