Hi, We have had a Canada Post account since 1999 and we constantly ship using EST Desktop 2.0. No issues there.
However we have been playing around with the API’s to see what we can do or improve on. The shipping rates API has always worked and still working.
We were looking at using the API for GetManifests. We are using SOAPUI 5.10.0 to test it out. We have our production API Username and Password (same one that we use for ShippingRates.
The requests from SOAPUI that we send is:
Endpoint we are using is https://soa-gw.canadapost.ca/rs/soap/manifest/v8 (production)
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v8="http://www.canadapost.ca/ws/soap/manifest/v8">
soapenv:Header/
soapenv:Body
v8:get-manifests-request
(edit by admin: removed customer number)
2026-06-01
2026-07-07
</v8:get-manifests-request>
</soapenv:Body>
</soapenv:Envelope>
However, the result we get is NO Manifests.
<soapenv:Envelope xmlns:tns="http://www.canadapost.ca/ws/soap/manifest/v8" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
soapenv:Header/
soapenv:Body
tns:get-manifests-response
</tns:get-manifests-response>
</soapenv:Body>
</soapenv:Envelope>
Are we missing something here? We ship constantly and we always print our Manifests from EST 2.0 Desktop.
One last note, on the printed Manifests that we get from EST 20.0 Desktop, the Manifest number is example “D123456789”.
Can someone please tell us why no manifests come up when we try the SOAPUI?
Hi CLUBPLUG,
Please do not post your customer number publicly on the forum, as it is considered sensitive information. I have removed it from your post.
Regarding the issue with the Get Manifests API returning no results, I assume you are attempting to retrieve manifests that were created through EST 2.0.
Please note that EST 2.0 and the Developer Program API do not share shipment data. This separation is intentional and helps prevent data inconsistencies that could occur if two independent applications were able to modify the same shipments without awareness of each other.
As a result, manifests created in EST 2.0 cannot be retrieved through the Developer Program API. To retrieve manifests via the API, shipments and manifests must also be created using the API.
Many thanks,
The Developer Portal team
Hi
Thank you for the quick reply!!
I will make a note to never post the customer number… 
Quick question then, if we have been using EST 2.0 Desktop from Day 1 (circa early 2000).
If I need to get access to the following with the API:
Tracking numbers from Start date to End Date.
Example: From June 1, 2026 to June 30, 2026
Is there any other Request in the list of request samples that would have that information for our account?
At the moment, I need to go into EST 2.0 Desktop and then do a “right click” on the History (on left) and select “Export History”.
We are trying to avoid using EST 2.0 Desktop for this extraction and use the API.
We only need tracking number from a date range.
Thank you again…
Regards,
Frank Vessella
Club Plug Inc.
Tel: 1-866-772-(PLUG)7584
EMAIL: frankv@clubplug.net
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
Hi @CLUBPLUG ,
If you need access to shipments, manifests, or tracking PINs created through EST 2.0, you would need to obtain that information from EST 2.0 itself.
The Tracking APIs can provide tracking summaries and tracking details for a shipment when the tracking PIN is already known and supplied in the request. In this respect, they function similarly to the public-facing tracking tool on the Canada Post website.
However, obtaining a list of tracking PINs that were created through your EST 2.0 account would require access to shipping data in order to identify which shipments belong to you. As mentioned previously, shipment data created through EST 2.0 is not shared with other applications or with the Developer Program APIs. Therefore, tracking PINs associated with EST 2.0 shipments cannot be retrieved through the Developer Program.
Many thanks,
The Developer Portal Team