Fetch latest data after receiving event notification.
After receiving a notification, you need to GET the release in order to receive the latest data.
Last updated
After receiving a notification, you need to GET the release in order to receive the latest data.
Last updated
EXAMPLE:
Please find a list below of these fields:
billOfLading
blNumber
yes
carrier
no
portOfLoading
yes
carrier
no
portOfDestination
yes
carrier
no
vessel
yes
carrier
no
agent
no
stayNumber
yes
carrier
no
lloydsNumber
yes
carrier
no
voyageNumber
yes
carrier
no
container
containerNumber
yes
carrier
no
containerStatus
yes
SCR app
Yes, when the carrier blocks or unblocks a release this field is updated.
pickupLocation
yes
carrier
Yes, when the pickup location (deep sea terminal) changes.
turnInLocation
yes
carrier
Yes, when the turn in location (depot) changes.
turnInReference
yes
carrier
Yes, when the turn in location (depot) changes.
termsAndConditions
yes
carrier
no
validFrom
yes
carrier
no
validUntil
yes
carrier
Yes, when the validity period is updated.
isoTypeCode
yes
carrier
no
address
no
deleted
yes
carrier
no
blocked
yes
carrier
Yes, this can occur when a container has to be scanned or when the carrier blocks the release temporarily.
encryptedPin
yes
SCR app
Yes, when the PIN is updated, for instance when the release is revoked while the pin was already retrieved.
gateOut
yes
terminal
Yes, when the container leaves the terminal.
createdAt
no
updatedAt
yes
SCR app
Yes, when a release is updated.
owner
yes
SCR app
Yes, when a release is transferred or revoked.
creator
no
version
no
pinRetrieved
yes
SCR app
Yes, when the pin is retrieved.
previousOwner
yes
SCR app
Yes, when a release is transferred or revoked.
nextOwner
yes
SCR app
Yes, when a release is transferred or revoked.
conditions
yes
carrier
no
greenLights
yes
Nxtport
Yes.