Search Help Contents:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Topics
|
Event Codes & ReferencesEventsThe Events request returns the same events as exp.o Visibility. An event consists of the following attributes when applicable:
The specific events that are available via our shipment tracking API depend on the underlying services that Expeditors provides on any given shipment or customs declaration. We refer to the events that occur in a typical shipment as “core events”. For example, “freight received” is a core event.
However, not every core event applies to every shipment. For example, “delivered to consignee” is a core event but would only apply if Expeditors is responsible for arranging the delivery of the shipment. We strongly recommend contacting your local Expeditors representative to discuss the events that apply to your shipments while using the below list as a starting point:
1. Like EDD further down the list, the AFD event is only provided if Expeditors is involved at the destination of the shipment. Best practice is to use the ETA event unless an EDD event is available. 2. Like EDL and RDL, the DLV and POD events are included if Expeditors is responsible for arranging the delivery of the shipment. 3. The reason for the delay is found in the "remarks" field of the Type Event. 4. The RLS event is available if Expeditors acts as the import customs broker at destination.
ReferencesThe References request returns the following information for a single Shipment ID, if the reference is present on the shipment:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
© 2024 Expeditors International of Washington, Inc. All information contained herein is business confidential and proprietary and may not be reproduced in any form without advanced written consent of an authorized officer of the copyright holder.
|