Additional features available within the Container Tracking API are listed below. Visit the related subpages to learn more.

More features

Additional features available within the Container Tracking API are listed below. Visit the related subpages to learn more.

Auto-unsubscribe

Detects new shipment cycles and automatically deactivates container tracking references.

Configurable tracking frequency

For some use cases, customers need to check for the latest container miletones more often. Now, customers can have the frequency of checking for new data configured to be as frequent as every two hours.

Customizable Options: 6 hours, 3 hours, 2 hours.

Read more about Configurable tracking frequency.

Continuous MBL processing

This feature is an optional setting that will continue to process parent references created using Create Reference via Bill of Lading until we see a vessel departure milestone from the origin port.

Read more about Continuous MBL processing.

Customs Clearance API

Minimal tracking based on MBL (master bill of lading). Real-time access to critical customs data.

Schedule a demo here.

Duplicate prevention

Prevents the creation of duplicate references for the same container ID, bill of lading, or booking number, so repeated inputs don't create extra billable references.

DSCA event and location codes

Utilizing DCSA event and location codes can reduce developer time by providing a programmable field to key on, enhancing the ability to filter specific event types, and reducing the need to maintain a list of Vizion's standardized descriptions.

Read more about DSCA event and location codes.

Enhanced locations

Enabling this feature will include more specific facility information such as SMDG, BIC, SPLC and FIRMS codes within the reference update payload.

Exception alerts

Also referred to as webhook events, exception alerts notify your systems automatically when tracking data changes for a reference, instead of requiring you to poll for updates.

Smart Updates

Vizion adjusts how often it checks each data source (carrier, terminal, rail) based on a shipment's current status, checking more frequently when an update is likely and reducing the delay before a tracking event reaches you.