Notifications for Release Parties
This page will guide you through the notifications you - as a Release Party - might receive in Certified Pick up (CPu). We will guide you through the different types of notifications and what to do with them.
For Release Parties, there are three types of CPu notifications:
Responses: asynchronous responses sent to your notification channel after you have sent a request tot the CPu API. These notifications indicate an error and require you to take action
Release Light events: events which relate to the Release Lights of the container (Terminal release, Customs release, Commercial release - released, blocked etc.)
Release Right events: events which happen to the Release Right (transferred to next party, accepted, declined, revoked)
For each type there is an example for display purposes. Click the expand to see the full notification.
The notification schemes also contain CPu variables (between double curly braces {{}}
) which are different for each notification you will receive. An overview & explanation of these CPu variables can be found on this page CPu variables overview .
Implementation of the notifications requires you to have read Getting Started with the API integration !
Important: you need to have set up a notification channel for your company in order to receive and process these notifications. See Setting up notification channels if you have not done so already.
Notifications - generic fields
Every notification that is sent by NxtPort will be built up with a generic part, allowing integrators to identify the asset, sender, error or warning messages and a Use case or type specific body.
Field Name | Type | Allowed values | Field Description |
---|---|---|---|
assetId | string | Contains the name or ID of the asset | For CPu, the assetId (NxtPort identification number) is used and contains the value |
id | string | The unique ID linked to the notification | For CPu, the container number is included in this field. |
PublicReferenceId | guid |
| Automatically generated GUID from NxtPort. This is a unique ID throughout our platform. In case of questions, please provide this ID, allowing us to clearly retrieve the corresponding information. |
externalReferenceId | string |
| Your own reference, as provided in the request header (optional). Will be null in case the notification was triggered by another party. |
senderId | string | NxtPort ID | The NxtPort ID of the owner that generated the notification. If a 3rd party triggered the event, this information will still be the owner of the original source that will be listed here. |
receiverId | string | NxtPort ID | This should always be your NxtPort ID as you are the receiver of this message. |
type | enumeration |
| Depending on the notification, one of these values will be used. Within the NxtPort Console, you can use these type to filter out notifications to multiple channels. |
event | enumeration | Multiple values allowed | Values will define the body of the notification and is explained further on in this document. |
body | N/A | N/A | Contains the event specific body related to this notification. This body is included in the details of the notifications and described later on in this document. |
timestamp | DateTime | UTC datetime | The timestamp when the notification was created by the Certified Pick-up platform. This will always be in UTC ISO 8601 format. |
errors | Array | free text | These arrays are not used in CPu notifications. The error message can be found in the body of the notification. |
warnings | Array | free text | These arrays are not used in CPu notifications. The warning message can be found in the body of the notification. |
Notifications list
Responses
As stated previously, CPu is an asynchronous process (with some exceptions), meaning that when data is sent to an API, NxtPort will first receive and ‘store’ the data and then in a separate process will process the action in a CPu context. This means however, that not all errors or issues can be reported in a synchronous API response and that you will need to integrate the notifications you receive to make sure all data you provide is processed correctly.
Response notifications are asynchronous responses sent to your notification channel after you have sent a request tot the CPu API. These notifications indicate an error and are characterized by the "event": "NotValidated"
field in the JSON body.
There is a problem with the action you performed on the Release Right. The error message is included in the "body"
field, all possible messages are listed below, including the mitigation steps.
Example of a notification
Notification received | Explanation | How to mitigate? | Notification body |
---|---|---|---|
Mismatch in entity | No Release Right action <Transfer / Accept / Decline / Revoke> due to: mismatch in provided identity. When a Release Right action with a non-existing identification is performed or when the sender’s identity is different from the current owner (during Transfer, Revoke) or next owner (during Accept, Decline). | Verify if you are allowed to perform the required action on the Release Right. |
JSON
|
No matching entity found | No matching entity found. No Release Right Transfer / Accept / Decline due to: no matching NxtPort Entity found for provided parameters (NxtEntityId, APCS, DUNS, EORI or TIN). | Verify if the receiving company has been correctly registered for CPu (check their NxtPort ID or use the Company Registry call) |
JSON
|
No matching release right | No Release Right Transfer / Accept / Decline due to: no matching Release Right found for provided parameters. When a Release Right action with a non-existing Equipment Number / Bill of Lading Number(s) / Release Identification combination is performed. | Verify the provided identifiers ( |
JSON
|
Release Right not pending | No Release Right Revoke due to: Release Right not in state ‘Pending’. When a Release Right Revoke is performed on on a Release Right that is not ‘pending’ (awaiting accept or decline) but instead is f.e. active. | Verify if the Release Right you wish to revoke has the Pending status (CPu UI or Get Release Detail call). |
JSON
|
Release Right transferred to current owner | When a Transfer Release Right action is performed with You will only receive this if you are the current owner of the Release Right. | Make sure to provide the correct identifiers of the |
JSON
|
Release Light events
Event notifications are notifications sent to your notification channel when an event occurs on a Release Right for which you are a stakeholder.
Example of a notification
Event | Explanation | Notification Body |
---|---|---|
Commercial Release created | A new Commercial Release was created within CPu by the Shipping Agent (via API call, COREOR message or CPu UI) in which your company has been identified as First Release Party. The Commercial Release Light switches to GREEN. |
JSON
|
Commercial Release blocked | A Commercial Release was blocked by the submitting Shipping Agent. The Commercial Release Light switches to RED. |
JSON
|
Commercial Release updated | A Commercial Release was updated by the submitting Shipping Agent. This notification serves as a heads-up. You will need to perform a Get Release Detail call to retrieve the updated release information. |
JSON
|
Commercial Release deleted | A Commercial Release was deleted by the submitting Shipping Agent. The Release Right is no longer active in CPu. |
JSON
|
Customs Release submitted | The container has been Released by the competent customs authority (CCRM message). The Customs Release Light switches to GREEN. |
JSON
|
Customs Selected for Scan | The container has been selected for scanning by the competent customs authority (CCRM/NGPS message). The Customs Release Light switches to YELLOW. |
CODE
|
Customs Transhipment | The container has been identified by the competent customs authority (CCRM message) as a Transhipment container. The Customs Release Light switches to YELLOW. |
CODE
|
Customs Port Equalisation | There’s a gate-in message for this import container. The Customs Release Light switches to YELLOW. |
CODE
|
Customs FAVV | The container has been identified by the competent customs authority as a FAVV container. The Customs Release Light switches to YELLOW. This information is subject to 1 day delay. |
CODE
|
Customs Documentary Control | The container’s documents are being investigated by the customs authority (PLDA message). The Customs Release Light switches to RED. This information is subject to 1 day delay. |
CODE
|
Customs Progress Partially Cleared | The container is partially cleared by the customs authority. At least 1 item for a bill of lading has been cleared by the customs authority. The Customs Progress Light switches to YELLOW. This information is subject to 1 day delay. |
CODE
|
Customs Manual Overwrite | The container has been Released manually by the Ship Agent or Terminal Operator. The Customs Release Light switches to GREEN. |
JSON
|
Release Right events
Event notifications are notifications sent to your notification channel when an event occurs on a Release Right for which you are a stakeholder.
Example of a notification
Event | Explanation | Notification Body |
---|---|---|
Release Right Transferred | The Release Right was successfully transferred to the You will only receive this notification if you are the |
CODE
Temporary format:
JSON
|
Release Right Revoked | The transferred (but not accepted by the You will only receive this notification if you are the |
JSON
|
Release Right Accepted | The transferred Release Right was accepted by the You will only receive this notification if you are the |
JSON
|
Release Right Declined | A Decline Release Right action was successfully processed, declining the pending release right and returning the ownership to the previous party. You will only receive this notification if you are the |
JSON
|
You have reached the end of the page. Go back to the integration guidelines.