CPu variables overview
Request body fields
Below you can find the overview of all the request body field keys which are used in the API calls.
This overview acts like a reference guide, not all fields are to be included in each call. The request bodies are always marked with the calls.
Field name | Type | Allowed values | Field description | |
|---|---|---|---|---|
| 1 |
| string | Free text | Unique release identification (per carrier). |
| 2 |
| string | Free text | Optional reference for you to identify the release internally. |
| 3 |
| string | Free text | Self-explanatory |
| 4 |
| string | Free text | Self-explanatory |
| 5 |
| Enum | “Import” / “Export” / “Transhipment” | Self-explanatory |
| 6 |
| Enum | “Full” / “Empty“ | Self-explanatory |
| 7 |
| string | Free text | Self-explanatory |
| 8 |
| string | Free text | Self-explanatory |
| 9 |
| string | Free text | Self-explanatory |
| 10 |
| string | Free text | Self-explanatory |
| 11 |
| string | ISO container type (e.g. “20GP“, “40HC“) or “Container” | Self-explanatory |
| 12 |
| boolean | true, false | A boolean value indicating if the release is carrier haulage (true) or merchant haulage (false). For invoicing purposes. |
| 13 |
| Array of strings | Free text | Bill of Lading number(s) of the container. The unique combination of container/BL will be used for the identification of the container release. |
| 14 |
| string | The indicative terminal where the container will be available for pickup. Can be updated at any time using the Update Commercial Release. | |
| 15 |
| Enum | Different per action you need to perform. Check the specific action. | Action which is sent to the CPu platform, e.g. “Release”, “Block“, “Update“ |
| 16 |
| Enum | “TIN” / “NxtEntityId” / “Eori” / “Duns” / “APCS” | Enter the type of identification of the carrier. Remark: TIN should be used for the VAT number of a company. |
| 17 |
| string | Free text | The value that belongs to the selected identification. Note: a carrier is not mandatory, but if filled, a check will occur if the identificationCode is known |
| 18 |
| Enum | “TIN” / “NxtEntityId” / “Eori” / “Duns” / “APCS” | Enter the type of identification of the party that will receive the Release Right. If the releaseTo party is not yet known at the moment of the commercial release, this information can be left out and updated later on in the process by using the Transfer Release Right method. Remark: TIN should be used for the VAT number of a company. |
| 19 |
| string | Free text | The value that belongs to the selected identification. Note: When carrier and releaseTo are not provided, the Release Right will automatically be assigned to the submitting Shipping Agent. |
| 20 |
| Enum | “TIN” / “NxtEntityId” / “Eori” / “Duns” / “APCS” | Enter the type of identification of the party transfers the Release Right. Remark: TIN should be used for the VAT number of a company. |
| 21 |
| string | Free text | The value that belongs to the selected identification. |
| 22 |
| string | ISO 8601 timestamp format in UTC time. E.g. | Date/time (UTC) from which the Commercial Release will be active. |
| 23 |
| string | ISO 8601 timestamp format in UTC time. E.g. | Date/time (UTC) until the Commercial Release is active. If not entered, a default of 60 calendar days will be applied. |
| 24 |
| string | Free text with maximum 50 characters, uppercase | The container number. This number will be used onwards in the process. |
| 25 |
| string | UN/LoCode | The UN/Locode of the operational port. For Antwerp this is “BEANR”, for Bruges this is “BEZEE”. |
| 26 |
| string | Free text | Free text to provide, is displayed in the audit trail of the Release Right |
| 27 |
| Enum | “Truck“ / “Barge“ / “Rail“ / “Unknown“ | Reported means of transport for post-carriage of the container |
| 28 |
| string | IMO number of vessel | Self-explanatory |
| 29 |
| string | Stay number assigned by port authority | e.g. V234555 |
Notification variables
In this table you can find all CPu variables used in the notifications and their explanation.
Variable in notification | Explanation | Can be NULL if no information was provided | |
|---|---|---|---|
| 1 |
| APCS code (unique identifier on C-point) of the relevant party indicated by the […]. This can be:
|
|
| 2 |
| DUNS number (https://www.dnb.com/duns-number.html ) of the relevant party indicated by the […]. This can be:
| X |
| 3 |
| EORI number of the relevant party indicated by the […]. This can be:
| X |
| 4 |
| NxtEntityId (or NxtPort ID) of the relevant party indicated by the […]. This can be:
|
|
| 5 |
| TIN (Tax Identification Number) number of the relevant party indicated by the […]. This can be:
For EU countries this is the VAT number as validated through the EU VIES https://ec.europa.eu/taxation_customs/vies/ . |
|
| 6 |
| ExternalId (external identifier from C-point) which is shared between C-point, NxtPort and T-MINING. This can be:
|
|
| 7 |
| Registered company name of the relevant party indicated by the […]. This can be:
|
|
| 8 |
| Masked (for privacy & security reasons) Alfapass number of the driver assigned for pick up. e.g. | X |
| 9 |
| Transport document (B/L or SWB) number of the shipment(s) inside the container. |
|
| 10 |
| Alias of the driver assigned for pick up. | X |
| 11 |
| Empty return reference of the container. Not fully implemented in CPu yet. Be sure to ask Shipping Agent if they provide this info. | X |
| 12 |
| Container number. |
|
| 13 |
| Container operator. | X |
| 14 |
|
|
|
| 15 |
| Container owner. | X |
| 16 |
| ISO type of container (e.g. or |
|
| 17 |
|
|
|
| 18 |
| Value & color of the Green Light. See the Green Light table below for all possible combinations and their meaning. | |
| 19 |
| ||
| 20 |
|
|
|
| 21 |
| ISO 8601 timestamp (in UTC) e.g. |
|
| 22 |
| GUID generated by the NxtPort platform to identify the notification. Is equal to the |
|
| 23 |
| UN/Locode of the operational port. This is “BEANR” for Antwerp and “BEZEE” for Bruges. |
|
| 24 |
| Identification code you provided in the original request. |
|
| 25 |
| NxtEntityId (or NxtPort ID) you provided in the original request. |
|
| 26 |
| Reference provided by the Shipping Agent to identify the Commercial Release | X |
| 27 |
| NxtPort standard terminal code (“0” + quay number e.g. Overview: Terminalcodes.pdf |
|
| 28 |
| Identifier provided by the submitting Shipping Agent. Is used together with the equipment number and bl number(s) to uniquely identify a Release Right. |
|
| 29 |
| Self-explanatory. | X |
| 30 |
| Self-explanatory. | X |
| 31 |
| Self-explanatory. | X |
| 32 |
| The External Reference Id submitted as request header in the original request. | X |
| 33 |
| NxtEntityId (or NxtPort ID) of your company, i.e. the company which has received the notification. |
|
| 34 |
| Free text provided by the party which triggered the event. | X |
Green Light table
In this table you can find all combinations of the Green Light name, value & color and their meaning.
Green Light | “greenLightName” | “greenLightValue” | “greenLightColor” | Explanation | |
|---|---|---|---|---|---|
| 1 | Commercial Release |
|
|
| Container has been commercially released. |
| 2 | Commercial Release |
|
|
| No commercial release information received yet (initial value) |
| 3 | Commercial Release |
|
|
| Container has been commercially blocked. |
| 4 | Commercial Release |
|
|
| Commercial release has expired:
|
| 5 | Terminal Discharge |
|
|
| No information on discharge status yet received (initial value) |
| 6 | Terminal Discharge |
|
|
| Container is still on board of vessel. |
| 7 | Terminal Discharge |
|
|
| Container has been discharged from vessel (import). |
| 8 | Terminal Discharge |
|
|
| Container has arrived on terminal via land side. |
| 9 | Terminal Release |
|
|
| No information on release status yet received (initial value) |
| 10 | Terminal Release |
|
|
| Container has been selected for scan by Terminal Operator. Scanning procedure must be followed. |
| 11 | Terminal Release |
|
|
| Container has been blocked on terminal by Terminal Operator. |
| 12 | Terminal Release |
|
|
| Container has been released on terminal by Terminal Operator. |
| 13 | Terminal Release |
|
|
| Container has been released on terminal by Terminal Operator by default (initial value). Might be turned on red later. |
| 14 | Terminal Release |
|
|
| Release Right has been archived, meaning:
|
| 15 | Customs Light |
|
|
| No release information received yet. (initial value) |
| 16 | Customs Light |
|
|
| Container has been selected for scanning by competent customs authority. Scanning procedure must be followed. |
| 17 | Customs Light |
|
|
| Customs authority has sent a CCRM “release” for this container. OR Customs authority has sent a CSR with color “green” for this container (release 4.1.0 - IRP). |
| 18 | Customs Light |
|
|
| Container can be released under transhipment |
| 19 | Customs Light |
|
|
| Container can be released under port equalisation |
| 20 | Customs Light |
|
|
| Container can be released under FAVV |
| 21 | Customs Light |
|
|
| Container is subject to documentary control |
| 22 | Customs Light |
|
|
| Container manually released by Ship Agent or Terminal Operator. |
| 23 | Customs Light |
|
|
| Container can be released for transfer. |
| 24 | Customs Progress |
|
|
| No information received from customs (initial value). This information is received with delay. |
| 25 | Customs Progress |
|
|
| Indicative light: at least 1 item of at least 1 BL is fully cleared. This information is received with delay and Customs light is always leading over CustomsProgress. |
| 26 | Customs Progress |
|
|
| Light defaulted on green as Customs Light is turned on Green. |
| 27 | Gate Operation |
|
|
| Container has not left the terminal yet according to Terminal Operator. (initial value) |
| 28 | Gate Operation |
|
|
| Container has left the terminal according to Terminal Operator. |
| 29 | Pick up |
|
|
| No Pick up Right has been generated yet for the container. (initial value) |
| 30 | Pick up |
|
|
| Pick up Right has been generated, i.e. a driver has been assigned. |
| 31 | Pick up |
|
|
| The assignment of a driver has been revoked, awaiting new assignment. |
Related pages
Need any further assistance?