Object describes the tracking information.
Object describes the tracking information.
Tracking ID.
The length of the tracking ID has been increased from 24 characters to 32 characters. We will use the legacy_id field to store the original 24-character tracking ID to maintain compatibility with existing data. Therefore, all tracking endpoints will continue to work with the legacy_id field as before.
The date and time the shipment was imported or added to AfterShip. It uses the format YYYY-MM-DDTHH:mm:ssZ
for the timezone GMT +0.
The date and time the shipment was updated. It uses the format YYYY-MM-DDTHH:mm:ssZ
for the timezone GMT +0.
(Legacy) The date and time the shipment was updated. It uses the format YYYY-MM-DDTHH:mm:ssZ
for the timezone GMT +0.
Tracking number.
Unique courier code. When importing a shipment with no courier slug and the tracking number can’t be recognized, the courier will be marked as unrecognized
. Get courier codes here.
Whether or not AfterShip will continue tracking the shipments. Value is false
when tag (status) is Delivered
, Expired
, or further updates for 30 days since last update.
Custom fields that accept an object with string field. In order to protect the privacy of your customers, do not include any personal data in custom fields.
Customer name of the tracking.
The ISO Alpha-3 code (3 letters) for the origin country/region. E.g. USA for the United States.
The state of the sender’s address.
The city of the sender’s address.
The postal code of the sender’s address.
The sender address that the shipment is shipping from.
The ISO Alpha-3 code (3 letters) for the destination country/region. E.g. USA for the United States.
The state of the recipient’s address.
The city of the recipient’s address.
The postal code of the recipient’s address.
The shipping address that the shipment is shipping to.
Destination country/region of the tracking detected from the courier. ISO Alpha-3 (three letters). Value will be null
if the courier doesn't provide the destination country.
The estimated delivery date provided by the carrier. It uses the shipment recipient’s timezone and the format may differ depending on how the carrier provides it:
Text field for the note.
A globally-unique identifier for the order.
The URL for the order in your system or store.
The date and time the order was created in your system or store. It uses the format: YYYY-MM-DDTHH:mm:ssZ
based on whichever timezone you provide.
Number of packages under the tracking.
The date and time the shipment was picked up by the carrier. It uses the timezone where the pickup occured. The format may differ depending on how the carrier provides it:
The date and time the shipment was delivered. It uses the shipment recipient’s timezone. The format may differ depending on how the carrier provides it:
The carrier service type for the shipment.
The shipment_weight field represents the total weight of the shipment. In scenarios where the carrier does not provide this information, you can provide the weight to AfterShip. We will prioritize the data provided by the carrier, if available. The shipment weight will be included in the Response and accessed through the GET API, Webhook, and CSV export. It will also be displayed on the AfterShip Tracking admin. Additionally, it plays a significant role in error-free shipment handling and carbon emission calculations, ensuring accurate and informed decision-making
The unit in which the value field is expressed.
The total amount of shipment weight.
Signed by information for delivered shipment.
The phone number(s) to receive sms notifications. Phone number should begin with +
and Area Code
before phone number.
Source of how this tracking is added.
Current status of tracking. (See tag definition)
Normalized tracking message. (See subtag definition)
By default this field shows the tracking_number
, but you can customize it as you wish with any info (e.g. the order number).
Number of attempts AfterShip tracks at courier's system.
Indicates if the shipment is trackable till the final destination. Three possible values:
The recipient’s language. If you set up AfterShip notifications in different languages, we use this to send the recipient tracking updates in their preferred language.
Deprecated
Array of checkpoint object describes the checkpoint information.
The date and time of the checkpoint event was added to AfterShip. It uses the format YYYY-MM-DDTHH:mm:ssZ
for the timezone GMT +0.
The unique code of courier for this checkpoint. Get courier slug here
The date and time of the checkpoint event, provided by the carrier. It uses the timezone of the checkpoint. The format may differ depending on how the carrier provides it:
Location info provided by carrier
City info provided by carrier
State info provided by carrier
Postal code info provided by carrier
The latitude and longitude coordinates indicate the precise location of the shipments that are currently in transit.
Country/Region ISO Alpha-3 (three letters) of the checkpoint
Country/Region name of the checkpoint, may also contain other location info.
Checkpoint message
Current status of tracking. (See tag definition)
Current subtag of checkpoint. (See subtag definition)
Normalized checkpoint message. (See subtag message definition)
Checkpoint raw status provided by courier
The array provides details about specific event(s) that occurred to a shipment, such as "returned_to_sender". You can find the full list of events and reasons here (Beta Feature)
Phone number(s) subscribed to receive sms notifications.
Email address(es) subscribed to receive email notifications.
Whether or not the shipment is returned to sender. Value is true
when any of its checkpoints has subtag Exception_010
(returning to sender) or Exception_011
(returned to sender). Otherwise value is false
.
The promised delivery date of the order. It uses the formats:
Shipment delivery type
Shipment pickup location for receiver
Shipment pickup note for receiver
Official tracking URL of the courier (if any). The language parameter of this link relies on the destination country/region and the language associated with the shipment, if the data regarding the destination country/region and language of the shipment is not available, AfterShip will set the language parameter of the link to "US" by default.
The date and time of the carrier’s first attempt to deliver the package to the recipient. It uses the shipment recipient’s timezone. The format may differ depending on how the carrier provides it:
Delivery instructions (delivery date or address) can be modified by visiting the link if supported by a carrier. The language parameter of this link relies on the destination country/region and the language associated with the shipment, if the data regarding the destination country/region and language of the shipment is not available, AfterShip will set the language parameter of the link to "US" by default.
Additional field required by some carriers to retrieve the tracking info. The shipper’s carrier account number. Refer to our article on additional tracking fields for more details.
Additional field required by some carriers to retrieve the tracking info. A type of tracking credential required by some carriers. Refer to our article on additional tracking fields for more details.
Additional field required by some carriers to retrieve the tracking info. The date the shipment was sent, using the format YYYYMMDD. Refer to our article on additional tracking fields for more details.
Whether the tracking is delivered on time or not.
The difference days of the on time.
The tags of the order.
The estimated delivery date of the shipment provided by AfterShip’s AI and shown to the recipients. It uses the format YYYY-MM-DD
based on the shipment recipient’s timezone.
The estimated arrival date of the shipment.
Indicates the confidence level and associated reason for an AI EDD prediction request. For a comprehensive list of confidence codes, refer to this document.
Earliest estimated delivery date of the shipment.
Latest estimated delivery date of the shipment.
Estimated delivery time of the shipment based on your custom EDD settings. It uses the format YYYY-MM-DD
based on the shipment recipient’s timezone.
The format of the EDD. Either a single date or a date range.
The specific EDD date.
For a date range EDD format, the date for the lower end of the range.
For a date range EDD format, the date for the upper end of the range.
A unique, human-readable identifier for the order.
The shipment’s original estimated delivery date. It could be provided by the carrier, AfterShip AI, or based on your custom settings. The format of carrier EDDs may differ depending on how the carrier provides it:
AfterShip AI and custom EDDs always use the format YYYY-MM-DD
. All EDDs use the shipment recipient’s timezone.
The format of the EDD. Either a single date or a date range.
The source of the EDD. Either the carrier, AfterShip AI, or based on your custom EDD settings.
The latest EDD time.
For a date range EDD format, the date and time for the lower end of the range.
For a date range EDD format, the date and time for the upper end of the range.
The most recently calculated estimated delivery date. It could be provided by the carrier, AfterShip AI, or based on your custom settings. The format of carrier EDDs may differ depending on how the carrier provides it:
AfterShip AI and custom EDDs always use the format YYYY-MM-DD
. All EDDs use the shipment recipient’s timezone.
The format of the EDD. Either a single date or a date range.
The source of the EDD. Either the carrier, AfterShip AI, or based on your custom EDD settings.
The latest EDD time.
For a date range EDD format, the date and time for the lower end of the range.
For a date range EDD format, the date and time for the upper end of the range.
Used to add tags to your shipments to help categorize and filter them easily.
If you have multiple accounts connected for a single carrier on AfterShip, we have introduced the courier_connection_id field to allow you to specify the carrier account associated with each shipment. By providing this information, you enable us to accurately track and monitor your shipments based on the correct carrier account.(Get your courier connection id)
In the event that you do not specify the courier_connection_id, we will handle your shipment using the connection that was created earliest among your connected accounts.
The next couriers get the second carrier information from user or AfterShip.
Tracking number.
Source of next couriers.
(Legacy) Replaced by origin_country_iso3
. Additional field required by some carriers to retrieve the tracking info. The origin country/region of the shipment. Refer to our article on additional tracking fields for more details.
(Legacy) Replaced by destination_country_iso3
. Additional field required by some carriers to retrieve the tracking info. The destination country/region of the shipment. Refer to our article on additional tracking fields for more details.
(Legacy) Replaced by destination_postal_code
. Additional field required by some carriers to retrieve the tracking info. The postal code of the recipient’s address. Refer to our article on additional tracking fields for more details.
(Legacy) Replaced by destination_state
. Additional field required by some carriers to retrieve the tracking info. The state/province of the recipient’s address. Refer to our article on additional tracking fields for more details.
The model contains the total amount of carbon emissions generated by the shipment.
The unit in which the value field is expressed. Allowed values: kg
The total amount of carbon emissions
The location_id refers to the place where you fulfilled the items.
The shipping_method string refers to the chosen method for delivering the package. Merchants typically offer various shipping methods to consumers during the checkout process, such as, Local Delivery, Free Express Worldwide Shipping, etc.
By dynamically tracking failed delivery attempts during shipment, this field allows you to pinpoint carriers accountable for the most failures. Analyzing the root cause of these failures enables you to improve carriers' delivery standard operating procedures (SOP), leading to an overall enhancement in delivery service quality.
The signature_requirement field serves the purpose of validating the service option type, specifically proof of delivery. By collecting the recipient's signature upon delivery, it ensures the package reaches the intended recipient and prevents disputes related to non-delivery or lost packages.
The delivery location type represents the secure area where the carrier leaves the package, such as a safe place, locker, mailbox, front porch, etc. This information helps ensure the shipment reaches the intended recipient efficiently, minimizing the risk of theft or damage.
preparing...