Notifications from your own system Via the DIWASS API Shipments tracked

Custom EVOA notification integration

Since 21 May 2026, notifications under the EU Waste Shipment Regulation (EVOA) for the cross-border shipment of waste are handled digitally through DIWASS, the European Union's central system. This follows from the revised EU Waste Shipment Regulation, Regulation (EU) 2024/1157. Besides the website, DIWASS offers an integration for business software. Appfront builds the integration that takes notifications and transport documents from your own system into DIWASS and reads the status back.

What is an EVOA notification integration?

An EVOA notification integration means you no longer have to enter notifications twice: once in your own system and once in DIWASS. The revised Waste Shipment Regulation was adopted on 11 April 2024 and has largely applied since 21 May 2026; most of the rules for exports outside the EU take effect on 21 May 2027. According to the European Commission, DIWASS is both a central website and a central hub for exchange with the local systems of authorities and with company software. Among other things, the system handles the notification and the decision-making on it, the transport documents and the certificates of treatment. The requirements for this integration are set out in Implementing Regulation (EU) 2025/1290, and the Commission publishes technical documentation for the API, which is updated continuously.

The ILT (the Dutch Human Environment and Transport Inspectorate) explains how a notification works in DIWASS. Every company involved in EVOA shipments registers once. As soon as you save a draft for the first time, the notification receives a unique notification number, which you put on the contract and the annexes. You upload annexes, such as the contract, the financial guarantee and the information on origin, composition, treatment and route, as labelled PDFs. The notifier and the producer both authenticate the notification in DIWASS, and carriers and third-party processors must have their own account, because you can only select parties from the list of registered ones. According to the ILT, authorising a third party to handle the administration is not an accepted way of working: only an authenticated employee of the notifying company may submit.

We build it as a custom solution because the data for a notification is already in your own systems: waste streams, contracts, carriers, processors and quantities. The integration prepares that data for DIWASS, checks that the parties involved are registered, and lets you submit the notification from your own software under your company's registration. It then reads back statuses, questions from authorities and decisions, and keeps track of how many shipments have been used on a notification. For an API integration, the Commission requires your company to be registered in DIWASS first with an authorised user, who then requests the integration credentials from the Commission's helpdesk. We take care of that together with you.

Enter once

From your system into DIWASS.

Under your name

Submitted by your own employee.

Status sent back

Questions and decisions visible.

How we build your EVOA notification integration

We start with your waste shipments: which streams you send across the border, in which role, with which carriers and processors, and where the data currently lives. Then we define which fields and annexes go from your system to DIWASS and who in your organisation submits and authenticates. After registration and the request for the integration credentials, we first build the submission of a notification with annexes and the reading back of the status, and test that with the Commission. The transport documents and the tracking of shipments follow after that. If the API documentation changes, we update the integration.

1
Shipments mapped

Streams, parties, data.

2
Fields and roles

What goes to DIWASS.

3
First notification

Submitting and reading back the status.

4
Go-live and maintenance

Transport documents, and maintenance for new API versions.

What a WSR notification integration actually does

The components below appear in almost every integration with DIWASS. Which ones you need depends on your role and on the number of notifications and shipments.

Notification

Data from your own system.

Attachments

PDFs with the right label.

Lots

Registration checked in advance.

Status

Questions and decisions fed back.

Shipments

Usage tracked per notification.

Log

Every action traceable.

Who we build a WSR notification integration for

The integration is intended for companies that regularly ship waste across borders under a notification, or that deal with large numbers of notifications and transport documents as a processor.

Manufacturers

Your own waste across borders.

Collectors

Waste streams from multiple customers.

Traders and brokers

Notifier on behalf of the producer.

Processors

Completing transport documents.

Technology and integrations

This page is about notifications for the transboundary shipment of waste. For reports of waste streams within the Netherlands, see our page on the waste stream number integration. If you are interested in digital transport information in general, read about the eFTI integration, and for waste delivered in ports, about the waste delivery system. You can read about our approach at building software.

DIWASS Regulation (EU) 2024/1157 Implementing Regulation (EU) 2025/1290 DIWASS API Notification number Transport document PDF attachments ERP and waste administration Roles and permissions Log

Why Appfront for your WSR notification integration?

A notification that is entered twice, a carrier that is not in DIWASS and blocks submission, or a notification against which too many shipments are quietly planned all cost time and can hold up a shipment. That is what we build around: data from your own system, parties checked in advance and shipments that you track per notification.

One source

No double data entry.

Checked in advance

Parties and attachments complete.

Overview

Shipments per notification.

Security and privacy in a WSR notification integration

Notifications contain commercially sensitive data, such as contracts, financial guarantees and waste compositions, as well as personal contact details. The integration uses only the data needed for the notification and leaves submission and authentication to your own staff, as DIWASS requires. The ILT (the Dutch Human Environment and Transport Inspectorate) points out that users from outside your organisation can view all data in DIWASS and perform actions on behalf of your company; the integration therefore does not add external users.

The integration runs in a European data centre or in your own environment, with encrypted connections and storage. API credentials are kept secured and are not visible to staff. Every action is recorded with the time, user and result, and we agree with you in advance who is allowed to do what.

Frequently asked questions about a WSR notification integration

Questions that producers, collectors, traders and processors ask before they get started.

The Digital Waste Shipment System is the European Union's central system for submitting and exchanging information and documents on waste shipments electronically. It works as a website and as a hub for integrations with local systems and business software.

According to the ILT, you have registered WSR notifications and reports digitally in DIWASS since 21 May 2026. This follows from the revised Waste Shipment Regulation, Regulation (EU) 2024/1157.

Yes. Alongside the website, the European Commission offers an API for business software, with requirements set out in Implementing Regulation (EU) 2025/1290. Your company must first be registered in DIWASS with an authorised user, who requests the integration credentials from the Commission's helpdesk.

According to the ILT (the Dutch Human Environment and Transport Inspectorate), authorising a third party to handle the administration is not a recognised way of working: only an authenticated employee of the notifying company can submit. A registered trader or broker can act as the notifier itself, with written authorisation from the producer or collector.

All companies involved in a shipment, such as the notifier, the producer, the carriers, the consignee and the recovery or disposal facility. You can only select parties that are registered; entering them manually is not possible.

You upload mandatory attachments, such as the contract, the financial guarantee and the information on the waste and the route, as labelled PDFs. You put the notification number that DIWASS creates when you first save on the contract and the attachments. The integration keeps track of which attachments belong to which notification.

For companies with many notifications or shipments, or with data that is already held in their own system. If you only submit the occasional notification, the DIWASS website is usually enough.

Submit your EVOA notifications from your own system?

Tell us which waste streams you ship across borders and which system holds your data. We'll show you how an integration with DIWASS takes that over.

Edit content