CPu notifications overview
Introduction
This page contains the overview of all the notifications of the CPu platform. The purpose of this page is to allow you to identify a notification.
It is not an overview of all notifications your company may receive, as these are different for each CPu role. Please check the separate pages per role for this purpose.
CPu notifications can be identified by the "type"
value in the JSON body: ReleaseRight
, ReleaseLight
& TerminalEvent
. Use the table of contents to navigate to the type you need to look up.
Each type can be subdivided using different notification parameters. These are listed next to the notification scheme of the relevant type. Using the parameters you can check the matrix below the scheme to find out the meaning (and actions you might need to take) of the received 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 .
Under the Generic Services notifications you can find the notifications which are triggered by calling the generic services (Get Release Detail, Get Release Rights List, …).
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
Find your notification
“type“: “ReleaseRight”
Notification parameter matrix:
Event | ActionType | Explanation | Sent to |
---|---|---|---|
|
| The Release Right was successfully transferred to the |
|
|
| The transferred Release Right was accepted by the |
|
|
| The transferred Release Right was declined by the |
|
|
| The transferred (but not accepted by the |
|
“type“: “ReleaseRight”, “event“: “ThrownException“
Please contact NxtPort Support when this occurs.
“type“: “ReleaseRight”, “event“: “Update“
This notification provides an update, including the container number and the revised parameters.
“type“: “ReleaseRight”, “event“: “NotValidated“
This type of notification indicates an error and are sent to the sender of the original request. Check the body value for the error message and see the table below on how to mitigate the error.
Notification parameter matrix:
Category | Error messages | Explanation | How to mitigate? |
---|---|---|---|
Release Right errors |
| When there’s already an active commercial release in for the combination of | If not relevant anymore delete the commercial release for the |
Release Right errors |
| When a Transfer Release Right action is performed with | Verify that you provided the correct company details in the |
Release Right errors |
| 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 e.g. active. | Verify if the Release Right you wish to revoke has the Pending status (CPu UI or Get Release Detail call). |
Release Right errors |
| 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 ( |
Release Right errors |
| No Release Right Transfer due to: no matching NxtPort entity found for This response has a special indication showing the request has been logged but could not be completed. | Verify if the receiving company has been correctly registered for CPu (check their NxtPort ID or use the Company Registry call) |
Release Right errors |
| 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) |
Release Right errors |
| No Release Right Transfer/Accept/Decline 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. |
Release Right errors |
| No Release Right Accept/Decline due to: When a Release Right Accept/Decline action is performed with a | Verify if the transferred Release Right is Pending for your company. Provide your company details in the |
Release Right errors |
| No Release Right Transfer due to: Pick up Right already generated, no transfer possible. When the last transport company owning the Release generates a Pick up Right (i.e. assigns a driver for pick up), the Release Right cannot be transferred anymore. | If you need to transfer a Release Right after it has been assigned, un-assign the Right first before transferring. |
Release Right errors |
| No Release Right Transfer due to: Release Right expired When a Release Right has expired (60 days after creation date OR when expiration date has passed, whichever comes first), it cannot be transferred anymore. Contact the Shipping Agent to check why Right has expired. | Contact the submitting Shipping Agent to inform why the Release Right has expired. NxtPort has no influence on the expiration date whatsoever. |
Release Right errors |
| No Release Right Transfer due to: Release Right not transferrable to Terminal Operator A Release Right can only be transferred to a Release Party or a Transport Operator. Companies with strictly the Terminal Operator role cannot receive Release Rights. | Verify you have transferred the Release Right to a Release Party or a Transport Operator. |
Pick up Right errors |
| No Pickup Right Assigned due to: provided terminalCode does not match existing terminal for Release Right. When a Assign/Revoke/Update Pickup action contains a terminalCode that is mapped to a different terminal on the CPu platform then the terminal that is registered for the Release Right. | Verify if you have provided the correct terminal code in the Pickup action call. |
Pick up Right errors |
| No Pickup Right Assigned due to: Release Right not active for an owner When a Assign/Revoke/Update Pickup action is performed via API for a Release Right that is currently in state ‘pending’ (waiting for accept, decline or revoke) | Verify that the Release Right has been accepted before assigning the Pick up. |
Pick up Right errors |
| No Pickup Right Assigned due to: invalid owner When an Assign Pickup action is performed via API with an unidentified Pickup Party: company is not the current owner of the Release Right. | Verify if your company is owner of the Release Right. |
Pick up Right errors |
| No Pickup Right Revoked due to: invalid owner When a Revoke/Update Pickup action is performed via API with an unidentified Pickup Party: company is not the current owner of the Release Right. | Verify if your company is owner of the Release Right. |
Pick up Right errors |
| No Pickup Right Revoked/Updated: no matching active Pickup Right found When a Revoke/Update Pickup action is performed via API for a Release Right that is currently has no active Pickup Right assigned. | Verify if the Pickup Right is active before Revoking/Updating. |
“type”: “ReleaseLight”
Notification parameter matrix:
Event | greenLightName | originalValue | newValue | Explanation | Sent to |
---|---|---|---|---|---|
|
|
|
| A new Commercial Release was created within CPu by the Shipping Agent (via API call, COREOR message or CPu UI). The Commercial Release Light switches to GREEN. |
|
|
|
|
| A Commercial Release was blocked by the submitting Shipping Agent. The Commercial Release Light switches to RED. |
|
|
|
|
| A Commercial Release was unblocked by the submitting Shipping Agent. The Commercial Release Light switches to GREEN. |
|
|
|
|
| The container has been discharged from the vessel by the Terminal Operator (API call or COARRI DISCHARGE). The Terminal Discharge Light switches to GREEN. |
|
|
|
|
| The container has been released on the terminal by the Terminal Operator (API call or CPu UI). The Terminal Release Light switches to GREEN. |
|
|
|
|
| The container has been blocked on the terminal by the Terminal Operator (API call or CPu UI). The Terminal Release Light switches to RED. |
|
|
|
|
| The container has been marked selected for scan by the Terminal Operator (API call or CPu UI). The Terminal Release Light switches to YELLOW. |
|
|
|
|
| The container has been released by the competent customs authority (CCRM message). The Customs Light switches to GREEN. |
|
|
|
|
| The container has been selected for scanning by the competent customs authority (CCRM message). The Customs Light switches to YELLOW. |
|
|
|
|
| The container has been identified by the competent customs authority (CCRM message) as a Transhipment container. The Customs Light switches to YELLOW. |
|
|
|
|
| There’s a gate-in message for this import container. The Customs Light switches to YELLOW. |
|
|
|
|
| The container has been identified by the competent customs authority as a FAVV container. The Customs Light switches to YELLOW. This information is subject to 1 day delay. |
|
|
|
|
| The container’s documents are being investigated by the customs authority (PLDA message). The Customs Light switches to RED. This information is subject to 1 day delay. |
|
|
|
|
| The container has been reported to be empty. The Customs Light switches to ORANGE. Logic that sets the Customs light to “NOTAPPLICABLE” is deprecated in release 4.1.1 |
|
|
|
|
| The Customs light has been overruled by Ship Agent or Terminal. The Customs Light switches to GREEN. |
|
|
|
|
| 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. |
|
|
|
|
| The Customs Progress Light automatically switches to GREEN when the Customs Light switches to GREEN. |
|
|
|
|
| The container has left the terminal, this event is triggered by the Terminal Gate Out (API gate-out, CODECO OUT, CODECO STRIP) message. |
|
|
|
|
| The container has left the terminal, this event is triggered by the Terminal Gate Out (CODECO OUT) message. |
|
|
|
|
| A Pick up Right has been generated, meaning a driver, barge - or rail operator was assigned for pick up by the last Transport Operator holding the Release Right. The Pick up Light switches to GREEN. |
|
|
|
|
| A Pick up Right has been revoked, meaning the driver, barge - or rail operator was de-assigned by the last Transport Operator holding the Release Right. The Pick up Light switches to RED. |
|
|
|
|
| A Pick up Right has been updated, meaning a new driver, barge - or rail operator was assigned for pick up by the last Transport Operator holding the Release Right. The Pick up Light remains GREEN. |
|
“type“: “ReleaseLight“, “event”: “Update“ or “Delete”
When a Shipping Agent submits an update or delete to an existing Release Right, the sent notification is slightly different as per below:
Event | ActionType | Explanation | Sent to |
---|---|---|---|
|
| An update to a Release Right (combo equipment number, B/L number & Release Identification) was submitted by the Shipping Agent. Notification contains the new information for the Release Right. Example of data that could be updated is |
|
|
| The Release Right has been deleted by the Shipping Agent. Notification contains the information for the Release Right. A reason for the delete can be provided by the Shipping Agent. |
|
“type”: “ReleaseLight”, “event“: “NotValidated“
This type of notification indicates an error and are sent to the sender of the original request. Check the body value for the error message and see the table below on how to mitigate the error.
Notification parameter matrix:
Error messages | Explanation | How to mitigate? |
---|---|---|
| No Commercial Release/Terminal Release/… action processed due to: the current state of the Release Light is identical to the new provided state. When a Terminal/Commercial/… Light is received but the value is identical to the existing value for this light. | Verify the current state of the Release Light and find out which action you want/need to take. |
| No Commercial Release action (Update, Revoke etc…) (different from Release) processed due to: no matching release right found for provided identifiers. When a Release Light action (except for the Release action) fails due to no matching release right reference found based on the | Verify the identifiers of the Release Right you provided. Make sure they exist. |
| Invalid Terminal Code. When a provided | Verify the provided terminal code. Make sure it is was communicated to NxtPort during the onboarding. |
| No Commercial Release action processed due to missing parameters: When mandatory properties such as The body of the notification should contain the information you will need to know which parameters are missing. | Verify you provided all mandatory values and try again. |
| No Commercial Release action processed due to Release Right already found in CPu. | If you need to update an existing Commercial Release, use the update method. If you want to delete an existing Release and submit a new one, be sure to use a different |
“type”: “terminalEvent”
“type”: “terminalEvent”, “event“: ”GateOut”
Event | isValid | Explanation | Sent to |
---|---|---|---|
| N/A | The container has left the terminal, this event is triggered by the Terminal Gate Out message. |
|
Generic Services notifications
Get Release Rights List
You will receive this notification after calling the Generic Service - Get Release Right List API call. It contains all current information & details about the Release Rights currently owned by your company.
Get Release Right Detail
You will receive this notification after calling the Generic Service - Get Release Right Detail API call. It contains all current information & details about the Release Right.