Skip to main content

DIWASS Integration Checklist

DIWASS (Digital Information System for Waste Shipments) allows commercial software systems to digitally exchange waste shipment documentation with EU competent authorities.

Before integrating with DIWASS, software vendors should ensure that their system supports the required technical and regulatory capabilities.

This checklist provides a practical overview of the steps typically required to implement DIWASS integration.

1. Obtain Access to DIWASS​

  • Register your software with the DIWASS platform operator.
  • Obtain credentials for OAuth 2.0 authentication.
  • Request access to the DIWASS SOAP API endpoints.
  • Obtain access to the official WSDL files distributed via the EU CIRCABC portal.
  • Confirm test environment availability.

2. Prepare System Architecture​

  • Implement SOAP client capability.
  • Support MTOM file transfer for attachments.
  • Implement secure HTTPS communication.
  • Support OAuth 2.0 Client Credentials authentication.
  • Design a document lifecycle tracking system.
  • Prepare data structures for notifications, movements, and Annex VII documents.

3. Implement Required Document Types​

Your system should support the following DIWASS document categories:

Notification Procedure​

  • Submit Notification
  • Submit Notification Authentication
  • Submit Request for Information Reply

Movement Documents​

  • Submit Movement Document
  • Submit Carrier Transfer
  • Submit Consignee Reception Certificate
  • Submit Facility Reception Certificate
  • Submit Facility Completion Certificate

Annex VII Procedure​

  • Submit Annex VII Document
  • Submit Annex VII Authentication
  • Submit Annex VII Carrier Transfer
  • Submit Annex VII Reception Certificate
  • Submit Annex VII Completion Certificate

4. Implement Attachment Handling​

  • Implement file upload using MTOM.
  • Store DIWASS attachment identifiers returned by the API.
  • Attach uploaded files to document submissions.
  • Support downloading attachments from DIWASS.

Typical attachments include:

  • facility permits
  • laboratory analysis reports
  • transport contracts
  • compliance documentation

5. Synchronize Reference Data​

Before submitting documents, software should retrieve reference data such as:

  • country codes
  • waste classification codes
  • transport modes
  • recovery and disposal codes
  • packaging types

Reference data should be refreshed periodically.

6. Implement Update Synchronization​

DIWASS provides updates through polling endpoints.

Your software must periodically request updates using the following endpoints:

  • GetActions
  • GetNotifications
  • GetAnnexVIIList

Each request uses a timestamp cursor to retrieve new updates.

7. Track Document Status​

Your system should track the lifecycle status of DIWASS documents.

Notification lifecycle​

  • Submitted
  • Acknowledged
  • Consented
  • Moving
  • Received
  • Completed

Movement lifecycle​

  • Submitted
  • Moving
  • Received
  • Completed

Annex VII lifecycle​

  • Announced
  • Moving
  • Received
  • Completed

8. Implement Error Handling​

Software should properly handle DIWASS SOAP fault responses.

Typical error types include:

  • validation errors
  • authentication errors
  • status conflicts
  • rate limits
  • system errors

Temporary failures should be retried.

9. Test Integration​

Before production deployment:

  • test document submissions
  • validate attachment uploads
  • verify synchronization endpoints
  • test lifecycle transitions
  • simulate error conditions

Confirm that the system behaves correctly for both notification procedures and Annex VII procedures.

10. Prepare for Production Deployment​

Final checks before going live:

  • configure production API credentials
  • enable monitoring of synchronization endpoints
  • ensure secure storage of authentication credentials
  • implement logging and auditing of document submissions
  • validate document lifecycle tracking

Related documentation: Developer Quickstart · API Overview · DIWASS Glossary