Skip to main content

Notification Service

Covers the full lifecycle of notified waste shipments (Annex IV/orange-listed waste).


Notification Lifecycle

The following state diagram illustrates the notification lifecycle and possible status transitions.


SubmitNotification

Submits a new notification to DIWASS. DIWASS assigns a notificationId and returns it synchronously. The notification enters SUBMITTED status.

Request (abbreviated)

<SubmitNotificationRequest>
<userCADomainId>YOUR-CADOMAIN-ID</userCADomainId>
<notification>
<takeBackIndication>false</takeBackIndication>
<illegalActivityIndication>false</illegalActivityIndication>
<individualShipmentIndicator>false</individualShipmentIndicator>
<destinedForRecoveryDisposal>RECOVERY</destinedForRecoveryDisposal>
<preConsentIndicator>false</preConsentIndicator>
<totalQuantity>
<massTonnes>10.5</massTonnes>
</totalQuantity>
<shipmentQuantity>3</shipmentQuantity>
<shipmentPeriodFirstStart>2026-06-01</shipmentPeriodFirstStart>
<shipmentPeriodLastStart>2026-12-31</shipmentPeriodLastStart>
<wasteClassifications>
<entry>
<wasteTypeCode>160213*</wasteTypeCode>
<wasteList>AnnexIV</wasteList>
</entry>
</wasteClassifications>
<physicalCharacteristicTypeCodes>
<code>S</code>
</physicalCharacteristicTypeCodes>
<wasteDesignationDescription>
<item><languageId>EN</languageId><description>Mixed PCBs</description></item>
</wasteDesignationDescription>
<customsCodesHS>
<code>854810</code>
</customsCodesHS>
<packageTypeCodes><code>DR</code></packageTypeCodes>
<specialHandlingRequired>true</specialHandlingRequired>
<recoveryDisposalTypeCodes><code>R3</code></recoveryDisposalTypeCodes>
<technologyDescription>
<item><languageId>EN</languageId><description>Thermal treatment</description></item>
</technologyDescription>
<reasonForExportDescription>
<item><languageId>EN</languageId><description>No licensed facility in origin country</description></item>
</reasonForExportDescription>
<exportCountryId>HR</exportCountryId>
<importCountryId>DE</importCountryId>
<transitCountryIds/>
<exportExitPointName>Rijeka Port</exportExitPointName>
<importEntryPointName>Hamburg Port</importEntryPointName>
<customsOfficeEntryName>Hamburg Main</customsOfficeEntryName>
<customsOfficeExitName>Rijeka Customs</customsOfficeExitName>
<customsOfficeExportName>Zagreb Customs</customsOfficeExportName>
<exportCAPartyUUID>xxxxxxxx-...</exportCAPartyUUID>
<exportCACode>HR-ENV-01</exportCACode>
<importCAPartyUUID>yyyyyyyy-...</importCAPartyUUID>
<importCACode>DE-ENV-NRW</importCACode>
<transitCAs/>
<parties>
<!-- See NotificationParty structure in DIWASS technical documentation -->
</parties>
<attachmentIds>
<id>ATT-001</id> <!-- pre-uploaded via UploadAttachment -->
</attachmentIds>
</notification>
</SubmitNotificationRequest>

Response

<SubmitNotificationResponse>
<notificationId>DIWASS-NOT-2026-HR-000123</notificationId>
<status>SUBMITTED</status>
<submittedAt>2026-05-21T08:30:00Z</submittedAt>
</SubmitNotificationResponse>

GetNotification

Retrieves a full notification record including all sub-documents received from DIWASS (decisions, RFIs, signals, etc.).

Request

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

Response

Full notification with nested acknowledgement, decisions, RFIs, and signals.


WithdrawNotification

Withdraws a previously submitted notification. Only possible while status is SUBMITTED or ACKNOWLEDGED (before consent decisions are issued).

Request

<WithdrawNotificationRequest>
<notificationId>DIWASS-NOT-2026-HR-000123</notificationId>
<reason>
<item><languageId>EN</languageId><description>Change of waste volume</description></item>
</reason>
<signature>
<signerName>Ivan Horvat</signerName>
<organizationRole>NOTIFIER</organizationRole>
<timestamp>2026-05-22T10:00:00Z</timestamp>
<emailURI>ivan@example.com</emailURI>
</signature>
</WithdrawNotificationRequest>

Response

<WithdrawNotificationResponse>
<notificationId>DIWASS-NOT-2026-HR-000123</notificationId>
<status>WITHDRAWN</status>
</WithdrawNotificationResponse>

SubmitNotificationAuthentication

Submits a party signature (authentication) on a notification. Multiple parties (NOTIFIER, PRODUCER) must authenticate before the notification is processed.

Request

<SubmitNotificationAuthenticationRequest>
<notificationId>DIWASS-NOT-2026-HR-000123</notificationId>
<partyRole>NOTIFIER</partyRole>
<partyUUID>xxxxxxxx-...</partyUUID>
<signature>
<signerName>Ivan Horvat</signerName>
<organizationRole>NOTIFIER</organizationRole>
<timestamp>2026-05-21T09:00:00Z</timestamp>
<emailURI>ivan@example.com</emailURI>
</signature>
</SubmitNotificationAuthenticationRequest>

Response

<SubmitNotificationAuthenticationResponse>
<notificationId>DIWASS-NOT-2026-HR-000123</notificationId>
<authenticationId>AUTH-001</authenticationId>
</SubmitNotificationAuthenticationResponse>

SubmitRFIReply

Submits a reply to a Request for Information issued by a competent authority on a notification.

Request

<SubmitRFIReplyRequest>
<requestForInformationId>RFI-DIWASS-001</requestForInformationId>
<reply>
<item><languageId>EN</languageId><description>We confirm the facility permit is enclosed.</description></item>
</reply>
<signature>...</signature>
<attachmentIds><id>ATT-002</id></attachmentIds>
</SubmitRFIReplyRequest>

Response

<SubmitRFIReplyResponse>
<replyId>REPLY-001</replyId>
</SubmitRFIReplyResponse>