Tracking
Get Tracking Summary – REST
Summary
Name: | Get Tracking Summary |
---|---|
Reason to Call: | To get the most recent/significant tracking event for a parcel |
Input: | Parcel Identification Parameter(s) (e.g PIN Number / DNC Number or Reference parameters) |
Output: | Date, location and event type for the most recent/significant event |
Error Examples: | PIN not found, duplicate PIN |
Possible Next Calls: | Get Tracking Details, Get Signature Image, Get Delivery Confirmation Certificate |
Version history: | Release notes |
Request Details
Request – Structure for Get Tracking Summary
Endpoint
GET https://XX/vis/track/pin/{pin number}/summary |
|
---|---|
Replace... | With... |
XX (Development) |
ct.soa-gw.canadapost.ca |
XX (Production) |
soa-gw.canadapost.ca |
{pin number} |
the parcel PIN |
{dnc number} |
the delivery notice card number |
YYYY-MM-DD |
the mailing from and to dates |
{reference number} |
the value you specified in either customer-ref-1 or customer-ref-2 fields when you created the shipment. |
{customer number} |
your customer number |
{destination postal code} |
the destination Postal Code of the parcel |
HTTP Headers
HTTP Header Variable |
Value |
---|---|
Accept |
application/vnd.cpc.track-v2+xml (Note: */* in place of the header value will return an error) |
Authorization |
Basic {Base64 encoding of userid:password} |
Accept-language |
en-CA or fr-CA |
Body
None
Request – Parameters
The following table describes the different parameters used to identify the parcel(s) for which information is being requested. These include parameters:
- That are embedded directly into the URI endpoint address. e.g.
{pin number}
and{dnc number}
. - That are provided as URI query parameters at the end of the URI endpoint address (e.g. reference parameters)
Get Tracking Summary – REST – Request Parameters | ||
---|---|---|
Parameter Name | Type of Parameter | Description/Size/Format |
Access by PIN |
||
{pin number} |
Directly embedded |
The PIN (Parcel Identification Number) assigned by Canada Post on creation of the shipping label and used for tracking purposes. (12, 13 or 16 characters) When executing a request by PIN, this is mandatory and is the only parameter necessary. The
|
Access by DNC Number |
||
{dnc number} |
Directly embedded |
The Delivery Notice Card (DNC) number – The number on the card left by delivery personnel when no one is home to receive the delivery. (15 numeric characters) When executing a request by DNC number, this is mandatory and is the only parameter necessary. The
|
Access by Reference Parameters |
||
customerNumber=XXXX |
Query |
The customerNumber query parameter value can be either:
(10 digit numeric) This is an optional query parameter. If the customerNumber query parameter is not specified, the customer-number of the user that was used to authenticate this request will be used. If you ship parcels on behalf of other customers and you specify their customer number in the request, only tracking results of parcels which were mailed "on behalf of" that customer (and that match the other query parameter criteria) are returned. If you ship parcels on behalf of other customers and you specify your own customer number, you will receive tracking results for any parcels you shipped for yourself, including all parcels you shipped for any other customers (providing it also matches the other query parameter criteria). |
referenceNumber=XXXX |
Query parameter |
The value assigned to a parcel by the shipper at the time the shipment was created. This value may have been specified in either "customer-ref1" or "customer-ref2" fields of the submitted parcel. (up to 35 characters) When executing a request by reference parameter, the referenceNumber query parameter is mandatory and must be included. The Get Tracking Summary service only returns tracking results for parcels that match the referenceNumber query parameter value. |
destinationPostalCode=XXXX |
Query |
The destination Postal Code, zip code or postal identifier for the parcel in its destination country. This is the value that would be supplied in the element "postal-zip-code" in a create shipment request. Format is any of the following:
The destinationPostalCode query parameter is optional. When present, the Get Tracking Summary service only returns tracking results for parcels that match the destinationPostalCode query parameter value. Note: For zip codes in the form 99999-9999, only the first 5 digits are used in the matching. |
mailingDateFrom= |
Query |
The combination of mailingDateFrom and mailingDateTo query parameters defines a range of dates for when the parcel(s) in question were shipped. Format is: yyyy-mm-dd The mailingDateFrom value cannot be earlier than two calendar months from the current date. When executing a request by reference parameter, both the mailingDateFrom and mailingDateTo query parameters are mandatory and must be included. The Get Tracking Summary service only returns tracking results for parcels that were shipped within the range of dates specified by the mailingDateFrom and mailingDateTo query parameters. |
mailingDateTo= |
Query |
Response Details
Response – Elements
Get Tracking Summary – REST – Detailed View of Response Elements | |
---|---|
Field Name | Description |
tracking-summary |
The top level of the XML structure. |
pin-summary |
Contains the response for the specified PIN. Contained within <tracking-summary> element. |
pin |
(Numeric 15 digits) The Parcel Identification Number (PIN) that can be used by the client for calling tracking services. |
origin-postal-id |
The first 3 digits of the origin Postal Code for Canadian destinations.
For an inbound international parcel, this field is blank or contains the postal identifier of the country of origin. |
destination-postal-id |
The first 3 digits of the destination Postal Code for parcels to be delivered in Canada.
For international parcels this is the postal identifier of the destination country (e.g. ZIP code for parcels with a U.S. destination) or an identifier of the destination country. |
destination-province |
The 2-digit province code for the destination. "postal designators" - abbreviations used by Canada Post ISO 3166-2 for Canadian bound parcels. Parcels bound for international destinations have the postal identifier of the destination country (e.g. ZIP code for parcels with a U.S. destination). |
service-name |
Canada Post service name in the language specified. The service-name will default to English if language is not specified. For inbound international parcels, service name is empty or contains the service name from its shipper of origin if available. |
mailed-on-date |
yyyy-mm-dd The date of the first event for the item. If the item has been mailed from an international location this date may be blank. |
expected-delivery-date |
yyyy-mm-dd The date the item is expected to reach the destination address for addresses in Canada. If the item has been mailed from or to an international location this date may be blank. |
actual-delivery-date |
yyyy-mm-dd The date the item was delivered. Blank if not delivered or if delivery information from an international organization for an international shipment has not been provided. |
delivery-option-completed-ind |
0 – at least one option was not satisfied 1 – all options were satisfied 2 – no options were found |
event-date-time |
yyyymmdd:hhmmss The time stamp of the most recent significant event. |
event-description |
A brief description of the event |
attempted-date |
yyyy-mm-dd - The date that a delivery was attempted. For shipments into or within Canada this will indicate that an unsuccessful attempt to deliver the parcel was made on the specified date. |
customer-ref-1 |
(Character string up to 35 characters) The value supplied by the shipper as customer-ref-1when the shipment was first created with Canada Post. French character set is supported through this interface. |
customer-ref-2 |
(Character string up to 35 characters) The value supplied by the shipper as customer-ref-2 when the shipment was first created with Canada Post. French character set is supported through this interface. |
return-pin |
If a return label (PIN) was printed at the same time the shipment was created and the shipment is being returned, the return PIN is displayed. |
event-type |
The value in this field will indicate what type of event is represented for this item. |
event-location |
For an event representing a scan or delivery, this value will indicate the location where the event took place. |
signatory-name |
If the event presented as the last most significant event is a signature, the text of this field contains the signatory name. Note: For enhanced privacy and security, the signatory name will now always be empty. It may be removed in a future release. |
code |
ID associated with the failure of a query. |
description |
Text message associated with an id. |
Response – Possible Error Responses
A correctly structured request may receive one of the following application error responses:
Code | Description | Notes |
---|---|---|
002 |
Duplicate Pin |
Received on PIN or DNC searches where duplicate PINs have been encountered. |
004 |
No Pin History |
No tracking results were found based on the parameters provided. Check your parameters and the order of the from and to dates. |
006 |
Reference number, mailed from date, mailed to date and destination Postal Code are required fields for a reference number search. |
Received only on reference number searches. |
008 |
Invalid Date |
For summary reference searches, dates greater than 2 months old will result in a return of this error. |
Response – XML Diagram
PIN and DNC queries return a single "pin-summary" result. A reference search may return multiple "pin-summary" instances if more than one item matches the search criteria.
Examples
Sample REST XML – PIN Request
GET https://XX/vis/track/pin/7023210039414604/summary
Sample REST XML – PIN Response
<tracking-summary>
<pin-summary>
<pin>7023210039414604</pin>
<origin-postal-id>K1G</origin-postal-id>
<destination-postal-id>K0J</destination-postal-id>
<destination-province>ON</destination-province>
<service-name>Expedited Parcels</service-name>
<mailed-on-date>2011-04-04</mailed-on-date>
<expected-delivery-date>2011-04-05</expected-delivery-date>
<actual-delivery-date/>
<delivery-option-completed-ind>2</delivery-option-completed-ind>
<event-date-time>20110404:133457</event-date-time>
<event-description>Order information received by Canada Post</event-description>
<attempted-date/>
<customer-ref-1>APRIL1REF1A</customer-ref-1>
<customer-ref-2>APRIL1REF1C</customer-ref-2>
<return-pin/>
<event-type>INDUCTION</event-type>
<event-location/>
<signatory-name/>
</pin-summary>
</tracking-summary>
Sample REST XML – DNC Request
GET https://XX/vis/track/dnc/315052413796541/summary
Sample REST XML – DNC Response
<tracking-summary>
<pin-summary>
<pin>1680678172650919</pin>
<origin-postal-id/>
<destination-postal-id>K0B</destination-postal-id>
<destination-province>ON</destination-province>
<service-name>Xpresspost</service-name>
<mailed-on-date>2011-01-10</mailed-on-date>
<expected-delivery-date>2011-01-12</expected-delivery-date>
<actual-delivery-date>2011-01-27</actual-delivery-date>
<delivery-option-completed-ind>2</delivery-option-completed-ind>
<event-date-time>20110127:140229</event-date-time>
<event-description>Item successfully delivered</event-description>
<attempted-date>2011-01-11</attempted-date>
<customer-ref-1/>
<customer-ref-2/>
<return-pin/>
<event-type>DELIVERED</event-type>
<event-location/>
<signatory-name/>
</pin-summary>
</tracking-summary>
Sample REST XML – Reference Request
GET https://XX/vis/track/ref/summary?mailingDateTo=2011-04-05&destinationPostalCode=K0J1T0&customerNumber=1111111&mailingDateFrom=2011-03-01&referenceNumber=APRIL1REF1A
Sample REST XML – Reference Search Result
<tracking-summary>
<pin-summary>
<pin>1681334332936901</pin>
<origin-postal-id>S6V</origin-postal-id>
<destination-postal-id></destination-postal-id>
<destination-province></destination-province>
<service-name></service-name>
<mailed-on-date>2010-01-05</mailed-on-date>
<expected-delivery-date></expected-delivery-date>
<actual-delivery-date>2010-01-06</actual-delivery-date>
<delivery-option-completed-ind>2</delivery-option-completed-ind>
<event-date-time>20100106:084923</event-date-time>
<event-description>Paiement CR - SPL</event-description>
<attempted-date>2010-01-06</attempted-date>
<customer-ref-1></customer-ref-1>
<customer-ref-2></customer-ref-2>
<return-pin></return-pin>
<event-type>OUT</event-type>
<event-location></event-location>
<signatory-name></signatory-name>
</pin-summary>
</tracking-summary>