The container represents a single tracking number with one or more deliveries nested in it.
The description of the model.
The latitude and longitude of the current location
Time in epoch seconds when this resource was created.
All of the deliveries that are nested in this container.
The estimated container for this container in epoch seconds.
Unique identifier for the container.
The hub location to which this container is assigned.
The ID of the layout where this container is being stored.
The amount of lead time needed to come get the parcel from the sender. This is set up in the dashboard.
Key value pairs of data that you can set for this container.
Unique identifier for the organization that owns this container. This will always be your organization ID.
Current status for this container. See Statuses.
Provider-specific string used to track this container.
An array of waypoints this container had in order from oldest to newest.
The address of the package at this waypoint. Address details are often limited to use the city and state when in transit.
A comment left by the provider about this update.
The ID of the container that this delivery was on during this update
Time in epoch seconds when this update occurred.
The latest event that occurred at this waypoint. See Shipment Events
A unique hash for this update to make it easier to identify duplicates in webhooks.
An array of URLs to images about this update. Commonly used by on-demand couriers for picture proof of containers.
The ID of the layout that this item is on, if it matches one of your locations.
The ID of the location of this update, if it is one of your locations.
User-friendly message generated by PackageX to let a customer know about their shipment status.
The status code for this update See Statuses
The time in epoch seconds when this status was last updated.
The ID of the vehicle that this container was on during this tracking update
URL where a user can go to track their packages.
Time in epoch seconds when this container was last updated.