Skip to main content

DIWASS Integration Examples

DIWASS integration uses SOAP web services to exchange waste shipment documentation with competent authorities.

This page provides simplified examples of common DIWASS operations to help developers understand how requests and responses are structured.

The examples illustrate typical payloads used when submitting notifications, movement documents, and Annex VII documents.

Example: Submit Notification​

This example shows a simplified notification submission request.

Notifications are used for notified waste shipments under the EU Waste Shipment Regulation.

SOAP Request Example​

<SubmitNotificationRequest>
  <userCADomainId>EXAMPLE-SOFTWARE-001</userCADomainId>

  <notification>

    <destinedForRecoveryDisposal>RECOVERY</destinedForRecoveryDisposal>

    <totalQuantity>
      <massTonnes>10</massTonnes>
    </totalQuantity>

    <shipmentQuantity>3</shipmentQuantity>

    <exportCountryId>HR</exportCountryId>
    <importCountryId>DE</importCountryId>

    <wasteClassifications>
      <entry>
        <wasteTypeCode>160213*</wasteTypeCode>
        <wasteList>AnnexIV</wasteList>
      </entry>
    </wasteClassifications>

    <recoveryDisposalTypeCodes>
      <code>R3</code>
    </recoveryDisposalTypeCodes>

  </notification>
</SubmitNotificationRequest>

SOAP Response Example​

<SubmitNotificationResponse>

  <notificationId>
    DIWASS-NOT-2026-HR-000123
  </notificationId>

  <status>SUBMITTED</status>

</SubmitNotificationResponse>

Example: Upload Attachment​

Attachments must be uploaded before submitting documents that reference them.

SOAP Request​

<UploadAttachmentRequest>

  <attachmentType>FacilityPermit</attachmentType>

  <originalFilename>
    facility_permit.pdf
  </originalFilename>

  <mimeCode>
    application/pdf
  </mimeCode>

  <containsPersonalData>false</containsPersonalData>

  <fileData>
    <!-- binary data transmitted using MTOM -->
  </fileData>

</UploadAttachmentRequest>

SOAP Response​

<UploadAttachmentResponse>

  <diwasskAttachmentId>
    ATT-DIWASS-001
  </diwasskAttachmentId>

</UploadAttachmentResponse>

Example: Submit Movement Document​

Movement documents are created for each shipment performed under an approved notification.

SOAP Request​

<SubmitMovementDocumentRequest>

  <notificationId>
    DIWASS-NOT-2026-HR-000123
  </notificationId>

  <movementDocument>

    <sequenceNumber>1</sequenceNumber>

    <actualDateOfShipment>
      2026-06-01
    </actualDateOfShipment>

    <actualQuantity>
      <massTonnes>3.5</massTonnes>
    </actualQuantity>

    <carrierMeansOfTransportCode>
      T1
    </carrierMeansOfTransportCode>

  </movementDocument>

</SubmitMovementDocumentRequest>

SOAP Response​

<SubmitMovementDocumentResponse>

  <movementId>
    MOV-DIWASS-2026-001
  </movementId>

  <status>
    SUBMITTED
  </status>

</SubmitMovementDocumentResponse>

Example: Submit Annex VII Document​

Annex VII documents are used for green-listed waste shipments and follow a simplified procedure.

SOAP Request​

<SubmitAnnexVIIRequest>

  <userCADomainId>EXAMPLE-SOFTWARE-001</userCADomainId>

  <annexVIIDocument>

    <actualDateOfShipment>
      2026-06-10
    </actualDateOfShipment>

    <exportCountryId>HR</exportCountryId>
    <importCountryId>AT</importCountryId>

    <actualQuantity>
      <massTonnes>5</massTonnes>
    </actualQuantity>

    <wasteClassifications>

      <entry>
        <wasteTypeCode>200101</wasteTypeCode>
        <wasteList>AnnexIII</wasteList>
      </entry>

    </wasteClassifications>

  </annexVIIDocument>

</SubmitAnnexVIIRequest>

SOAP Response​

<SubmitAnnexVIIResponse>

  <annexVIIDocumentNo>
    AVII-DIWASS-2026-HR-000456
  </annexVIIDocumentNo>

  <status>
    ANNOUNCED
  </status>

</SubmitAnnexVIIResponse>

Example: Retrieve Updates​

Client software must periodically request updates from DIWASS using synchronization endpoints.

SOAP Request​

<GetActionsRequest>

  <userCADomainId>
    EXAMPLE-SOFTWARE-001
  </userCADomainId>

  <lastSyncAt>
    2026-05-21T08:00:00Z
  </lastSyncAt>

</GetActionsRequest>

SOAP Response​

<GetActionsResponse>

  <actions>

    <action>

      <actionType>
        DECISION_ISSUED
      </actionType>

      <relatedDocumentType>
        NOTIFICATION
      </relatedDocumentType>

      <relatedDocumentId>
        DIWASS-NOT-2026-HR-000123
      </relatedDocumentId>

    </action>

  </actions>

</GetActionsResponse>

Implementation Tips​

  • Cache reference data such as country codes and waste classifications.
  • Upload attachments before submitting documents that reference them.
  • Track document lifecycle states.
  • Implement retry logic for temporary API failures.
  • Store synchronization timestamps when polling updates.

Related documentation: Notifications API · Movement Documents API · Annex VII API · Synchronization API