Students and classes from your own system Results sent back where they're needed Via the open Woots API

Custom Woots integration development

Appfront builds integrations with Woots, the digital assessment platform that schools use to create, administer and mark tests. Woots integrates as standard with student information systems such as Magister and Somtoday, and has an open API. For schools and school boards with their own systems, such as test scheduling, a dashboard or an archive, we build the link so that data isn't transferred by hand.

What is a Woots integration?

Woots is a digital assessment platform that lets teachers create, administer and mark tests, either digitally or on paper. It is widely used in secondary education. Woots has integrations with student information systems such as Magister and Somtoday, and an open API that lets schools and suppliers connect Woots to other systems.

Besides Woots and the student information system, many schools and school boards run their own systems: a test schedule for exam weeks, a dashboard for the department or the board, their own analysis of results, or an archive for tests and exams. Data is exported and processed by hand. An exam week is scheduled in two systems. And anyone who wants to compare results across multiple schools ends up merging files.

We build custom integrations because schools differ: which systems you use alongside Woots, which data needs to flow in both directions, and who is allowed to see it. What the API makes possible is set out in the Woots documentation, and we review that in the first step. What may be done with pupil data is something you decide together with your data protection officer.

From your own system

Pupils, class groups and teachers from the source you choose, without manual work.

Results where they are needed

Results sent to dashboards, analyses or an archive, and comparable across schools.

Via the open API

An integration on the API that Woots provides for this purpose, with monitoring and a log.

How we build your Woots integration

We start with your school or trust: which systems you use alongside Woots, which data is currently handled by hand, who needs to see what, and what your privacy policy says. We first build whatever removes the most work, often sending results to a dashboard or the planning of test weeks. After that we expand, once the first integration is running well and teachers get something out of it.

1
Mapping your school

Your systems alongside Woots, data, users and policy.

2
Route via the API

What the open Woots API offers for your situation.

3
Building the integration

Pupils, tests and results in both directions, with checks.

4
Go-live and maintenance

Go-live, monitoring, and maintenance when Woots changes.

What a Woots integration actually does

The components below feature in almost every Woots integration. Which ones you need depends on your systems.

Students

Pupils, groups and teachers.

Tests

Aligned with your own planning.

Results

To dashboards and analyses.

Archive

Tests and results retained.

Leadership

Multiple schools side by side.

Log

Every message logged, including errors.

Who we build a Woots integration for

The integration is intended for schools and trusts that use Woots alongside their own systems.

Schools

Own planning and dashboards. The key is no duplicate work.

School boards

Multiple schools. Comparison matters most.

Exam secretary

Test weeks and archive. Planning is what is needed.

Suppliers

A product for schools. The API is the core.

Technology and integrations

This page is about integrations with Woots. For custom tests and exams, see our page on exam software, for school operations see our page on an education ERP, and for secure messaging in education see our page on Edukoppeling. You can read about our approach at building software.

Woots Open API Pupils and class groups Teachers Tests and planning Results Dashboards and analyses Archiving Multiple schools Log

Why Appfront for your Woots integration?

A test week planned in two systems, and results merged by hand, cost teachers time that belongs in the classroom. That is what we build on: data from your own system, results where they are needed, and an integration on the Woots API.

Less manual work

No exporting and merging.

Insight

Results where they are needed.

Agreed

Via the open Woots API.

Security and privacy in a Woots integration

The integration processes pupil data and their results. Only the data that is needed is exchanged, access credentials are stored encrypted, and every message is logged. What is permitted follows your privacy policy.

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

Frequently asked questions about a Woots integration

Questions schools ask before they get started.

Woots is a digital assessment platform that teachers use to create, administer and mark tests, either digitally or on paper. It is widely used in secondary education and also has a test library.

Yes, including with Magister and Somtoday, for pupils, groups and results. If you only need those integrations, you do not need a custom one. A custom integration is for your other systems.

Via the open Woots API. What the API makes possible for your situation, which data can flow in both directions and how access is arranged, we review in the first step. Access is managed by your school's administrator and can be revoked at any time.

Yes. Test results can feed a dashboard for the department, the school or the board, so you can see how groups and subjects are performing without exports. You decide per role who sees which results, so a department sees its own figures and the board sees the big picture.

Yes, if each school uses Woots and the board wants it. The integration brings the data together so it can be set side by side. You decide what each school and the board can see.

The integration reports it and records what went wrong. The message is retried or queued for review, so no student or result goes missing.

For schools and boards that use Woots alongside their own systems for planning, analysis or archiving, and for software vendors who want to connect their product to Woots. For a school that only uses Woots and the student information system, the standard integrations are often enough.

Woots connected to your own systems?

Tell us which systems you use alongside Woots and which data is currently transferred by hand. We'll show you what the integration via the Woots API would look like.

Edit content