Deprecated Fields Prior to April 2023

Overview

The following are fields that have been deprecated prior to the latest April 2023 release. Please review the following details and note that these old fields do not receive updates or support. 

Deprecation Fields (prior to April 2023 release)

Under bill_of_lading object

• cbm

• kgs

• scheduled_receipt_time: no longer supported; refer to the container_event_list object for a detailed summary of the container milestones/events.

• scheduled_delivery_time: no longer supported; refer to the container_event_list object for a detailed summary of the container milestones/events.

• actual_receipt_time: no longer supported; refer to the container_event_list object for a detailed summary of the container milestones/events.

• actual_delivery_time: no longer supported; refer to the container_event_list object for a detailed summary of the container milestones/events.

• pol_predicted_loading_lt: no longer supported; refer to the container_event_list object for a detailed summary of the container milestones/events.

• pod_predicted_discharge_lt: pol_predicted_loading_lt: no longer supported; refer to the container_event_list object for a detailed summary of the container milestones/events.

sailing_info_tracking

• success: 

• cancelled

• status

• pol_predicted_loading_lt

• pod_predicted_discharge_lt: no longer supported; refer to the container_event_list object for a detailed summary of the container milestones/events.

voyage_details

• scheduled_arrival_on_time_confidence

• scheduled_departure_on_time_confidence

• prediction_confidence_level:

• original_voyage_no: no longer supported; use voyage_no_list instead to get the voyage number for a given vessel leg.

bill_of_lading_bookmark

• customer_id

• customer_no

Please note that no fields are being removed entirely. The deprecated fields will continue functioning but will not receive further updates or support. We recommend ensuring your fields are up to date, please refer to the latest release notes.