Custom ParnasSys integration development
Appfront builds custom ParnasSys integrations for primary education. Using the Edu-API and UWLR education chain standards, we securely retrieve pupil, class and results data from ParnasSys and synchronise it with your education app, parent communication platform, learning resource or BI dashboard. The privacy of (minor) pupils comes first, so everything is GDPR-proof and compliant with the Privacy Covenant for Education (Privacyconvenant Onderwijs).
What is a ParnasSys integration?
ParnasSys is by far the most widely used pupil administration and pupil tracking system (LAS/LVS) in Dutch primary education. Primary schools use it to record their pupil administration, class groupings, test results, notes and parent communication. For edtech builders and learning resource suppliers, ParnasSys is therefore the central source of pupil and results data in primary education.
In practice, a custom integration means reading out pupils and classes, retrieving test results, synchronising parent details and delivering that data to your own education app, parent communication platform, learning resource or BI dashboard. The traffic is generally read-heavy and runs via the education chain standards, with pupil data exchanged in pseudonymised form via the ECK iD.
Appfront builds in line with the education chain standards as described in Kennisnet's official UWLR documentation and the OWASP ASVS security standard. We align data flows, authorisation and error handling with the school's actual process, so the integration stays reliable, even at peak times such as test weeks and the start of the school year.
Pupil and class data
Retrieve up-to-date pupils, classes, class groupings and enrolments from ParnasSys. Your education app or learning resource always works with the right class structure, without schools having to enter data twice.
Results and test data
Retrieve or return test and learning results via the UWLR standard. Tracking tools and dashboards show how pupils and classes are progressing, based on the results as recorded in ParnasSys.
Privacy-first data exchange
Data on (minor) pupils deserves extra care. We exchange data via the ECK iD and the Nummervoorziening (Dutch national ID-number service for education), minimise data and set up integrations as read-only wherever possible, in line with the Privacy Covenant for Education.
Our development process for ParnasSys integrations
We follow a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your education application and the data flows it needs, through to go-live and ongoing maintenance, every step is aimed at an integration that your team and the schools involved can understand and trust.
We map out which pupil, class and results data you need from ParnasSys, which chain standard fits (Edu-API or UWLR), which privacy requirements apply and what process is needed for integration partner access.
We design the integration architecture, choose the right authentication and pseudonymisation via the ECK iD, and draw up an error-handling strategy.
Implementation with automated tests, structured logging and monitoring. You see working builds along the way.
A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development.
What a ParnasSys integration delivers in practice
Every ParnasSys integration is tailored to your education application, the data flows you need and the neighbouring systems. Below are the features we deliver most often for organisations that use ParnasSys data as part of their product or way of working.
Pupil and class sync
Synchronise pupils, classes, class allocations and enrolments between ParnasSys and your education app or learning resource. The school manages the data in one place; your application always works with the current class structure.
Results and test data
Retrieve or return test and learning results via the UWLR standard. Monitoring tools, methodology software and analytics work with the same results that are in ParnasSys, with no manual retyping or duplicate entry.
Parent communication app
Feed your parent communication platform with the right pupil, class and parent data from ParnasSys. Parents always see their child's current situation, and the school keeps a single, reliable source of truth.
Learning resources and methods
Link digital methods and learning resources to ParnasSys, so pupils automatically end up in the right class and the right learning resource. Sign-up and provisioning run via the chain standards and the ECK iD.
BI and education dashboards
Make pupil, class and results data available to a BI or education dashboard for a school or board. Insight into development and trends, with attention to aggregation and pseudonymisation so that privacy is safeguarded.
Integration via chain standards
Connect to the education chain standards Edu-API and UWLR, with authentication via certified integration partner access and tokens. This keeps the integration future-proof and familiar to schools and their IT partners.
Typical use cases in practice
A ParnasSys integration looks very different for each organisation. We see a number of patterns come up often, and for each of them we have a working setup that takes chain standards, privacy and proper authorisation into account.
Primary schools
Primary and special-education schools that want to feed an education app, monitoring tool or parent communication with current pupil and class data from ParnasSys. Enter it once, have the right data everywhere, with no duplicate work for the teacher.
School boards and umbrella organisations
Boards and umbrella organisations that want an overview of multiple schools at once. We make pupil, class and results data from ParnasSys available to a central dashboard, with attention to aggregation, per-school authorisation and pseudonymisation.
Edtech builders
Builders of educational software who want to integrate their application with the most widely used pupil administration system in primary education. We handle the connection to Edu-API and UWLR, certified integration partner access and privacy-compliant exchange of pupil data.
Learning resource and test suppliers
Publishers and suppliers of digital methods, tests and monitoring tools that need to exchange pupil and results data with ParnasSys. We set up UWLR results exchange and make sure pupils are linked securely via the ECK iD.
Technology we use
We build ParnasSys integrations on the Edu-API and UWLR education chain standards, combined with the backend stack that suits you. The exact choice depends on your target systems and privacy requirements, so that your own team can manage or further develop the integration.
If you want to send or receive transfer files from your own software, see our page on an OSO integration.
If you want to exchange pupil data via the Edustandaard standard, see our page on an EDEXML integration.
Why choose Appfront for your ParnasSys integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands, including in education. We always start with a thorough analysis of the existing systems and processes — an integration must not only be technically sound, but also add practical value for the school and the teacher.
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, 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 API integrations, middleware, custom software and web app development. Do you work in secondary education? Then see our Magister integration and Somtoday integration.
- Experience with the Edu-API and UWLR education chain standards
- Specialist in pupil, group and result data integrations
- Familiar with ECK iD, Nummervoorziening and pseudonymisation
- Secure by default — tokens in vaults, scoped permissions, read-only wherever possible
- Privacy approach in line with the Privacyconvenant Onderwijs (Dutch Education Privacy Covenant)
- 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 proactive further development
Security and privacy in ParnasSys integrations
A ParnasSys integration almost always involves pupil data, and therefore data about minors. That calls for extra care. Appfront builds in line with the principles of the Privacyconvenant Onderwijs and the OWASP ASVS. Among other things, that means: data minimisation, pseudonymisation via the ECK iD and the Nummervoorziening, tokens in secure vaults, scoped authorisation and integrations that we set up as read-only wherever possible.
We work within the certified integration partner access of the ParnasSys ecosystem and document the data flows, authorisations and retention periods so that your record of processing activities is complete and you can demonstrably comply with the GDPR. That way, both the school and the school board keep control over who may view which pupil data.
More about our approach to security: information security policy and CVD policy.
- GDPR-compliant data processing and data minimisation
- Pseudonymisation via ECK iD and Nummervoorziening
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Read-only integrations wherever possible
- Audit logs with traceable data flows
- Monitoring and alerting for anomalies
- Documentation for your record of processing activities
Frequently asked questions about ParnasSys integrations
Answers to the questions we are asked most often about ParnasSys integrations in primary education.
A ParnasSys integration is a technical connection between ParnasSys — Topicus's pupil administration and pupil tracking system for primary education — and another system, such as your own education app, parent communication platform, learning resource or BI dashboard. Pupil, group and result data are exchanged via the education chain standards Edu-API and UWLR, generally in a read-heavy way. An integration can range from simple (retrieving group allocations) to extensive (synchronising test results, notes and parent details with multiple systems).
ParnasSys is by far the most widely used pupil tracking system in Dutch primary education. If you are building an application for primary schools, school boards or learning resources for primary education, a ParnasSys integration is almost always relevant. For secondary education you would work with Magister or Somtoday instead — see our Magister integration and Somtoday integration. We help you determine which chain standard and which system best fit your target group.
A simple integration — for example, retrieving pupils and groups read-only via UWLR — can go live relatively quickly. More extensive scenarios involving test results, parent communication, multiple schools or boards and synchronisation to multiple target systems generally take more time, partly because of the application for certified integration partner access. After an intake conversation, we will give you a realistic estimate.
We work with the education chain standards Edu-API and UWLR, combined with the backend stack that suits you — Node.js, Python, .NET or PHP. Authentication runs via certified integration partner access and tokens (OAuth). To pseudonymise pupil data, we use the ECK iD and the Nummervoorziening (number provision service). We set up the integration as read-only wherever possible, with endpoints for pupils, classes and results.
The cost is determined by the complexity of the data flows, the number of systems to integrate, the required synchronisation frequency and the amount of custom business logic. The process for certified integration partner access, ongoing maintenance, monitoring and support also affect the total investment. We always provide a clear quote after a no-obligation analysis of your situation.
Yes. ParnasSys involves data on pupils, most of whom are minors, so privacy comes first. Appfront builds in line with OWASP ASVS and the principles of the Privacyconvenant Onderwijs (Education Privacy Covenant): data minimisation, pseudonymisation via the ECK iD, tokens in secure vaults and strictly separated permissions per integration. We set up integrations as read-only wherever possible and document the data flows so that your record of processing activities stays complete and you can demonstrably comply with the GDPR.
Yes. Appfront regularly takes over the maintenance of existing education integrations, even if they were originally set up by another party. We review the Edu-API and UWLR integrations, the authentication, the error handling and the privacy aspects, document the current setup and draw up improvement proposals. From that point on, we can handle changes, extensions and monitoring — including timely token rotation.
A ParnasSys integration is suitable for primary schools and special education schools, school boards and umbrella organisations that want an overview across multiple schools, and for edtech builders and suppliers of learning materials and assessments who want to feed their application with pupil and results data from primary education. For secondary education, you would connect to Magister or Somtoday instead. Together with you, we look at which chain standard and which scope fit best.
Ready to build your ParnasSys integration?
Tell us which pupil, class or results data you need from ParnasSys and which system it needs to integrate with — we are happy to advise on chain standards, privacy and the right authorisation. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour. Feel free to get in touch.