How the Vizion API automatically unsubscribes a reference at end of the container's journey

The Vizion API detects the presence of a new shipment cycle and deactivates container tracking references automatically.

Auto-unsubscribe works in one of the following ways:

  1. The API detects an actual "gate in empty return" event in the current journey's milestones

  2. The API detects the start of a new container journey

An actual 'Gate in empty return'
The API will check each reference's latest update for the inclusion of a "gate in empty return" milestone at the destination port. If one is found, the reference will be automatically unsubscribed or deactivated.

The start of a new container journey
If the latest reference update contains entirely different milestones that occurred later than the last available milestone in the previous update's milestone list, the API will determine that the container has started a new journey and automatically unsubscribe.


The Vizion API also utilizes logic for its own housekeeping that identifies references that are a few months old and have completed at least one journey. If there has been no new milestone activity or we detect a new container journey, our system will automatically unsubscribe from those references.

Turn off auto-unsubscribe

If you want to continue tracking containers through multiple shipment cycles, please contact support and we can disable auto-unsubscribe for you.