Versions Compared

Old Version 18

changes.mady.by.user Tom Rune

Saved on

compared with

New Version Current

changes.mady.by.user Tom Rune

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Short Description

...

If it is needed to be stored in NotToCount the CargoPort key but the known data are the Voyage key, the port name, the reasonForCall and the terminal code, can be used the following endpoint:

/ws/rest/CargoPort?filter=cargo.voyage.portCalls.ownedByVoyage(EQ){VOYAGE_KEY}&filter=port.portName(EQ){PORT_NAME}&filter=reasonForCall.reasonForCall(EQ){REASON_FOR_CALL_CODE}&filter=terminal.terminalCode(EQ){TERMINAL_CODE}

One example of endpoint:

/ws/rest/CargoPort?filter=cargo.voyage.portCalls.ownedByVoyage(EQ)318636143&filter=port.portName(EQ)ZHUHAI&filter=reasonForCall.reasonForCall(EQ)D&filter=terminal.terminalCode(EQ)CNZUH-0008

that returns an array of just one element of CargoPort with just its key that can be used to be stored in NoToCount:

...

Property
Type
Length
Mandatory
Description
Comments
daysNotToCount
Double

Number of days to not count
isProrated
Boolean



notToCountStartDate
Date

Period start date
notToCountEndDate
Date

Period end date
percentToCount
Double

Percent to not count
reasonForDelayString64
Reason for delay description
sourceInteger
YesFrom API 3.22 it can be or a /CargoPort or a /PortCall key 
minutesNotToCountInteger



portCall/PortCall

Connected PortCall, if any


New NotToCount Example

Example how to insert a new NotToCount object

...