Carrier Webservice Endpoints and ETD (Electronic Trade Documents) [Information]

Modified on Mon, 18 Mar at 2:32 PM

When shipping orders with ETDs, knowing the endpoints we target can help you review what is possible and/or transparent depending on the case.

Here is a list of the endpoints and current capabilities to date of this article's last update:

CARRIER	ENDPOINT	ETD CAPABILITY
Canada Post	https://www.canadapost-postescanada.ca/info/mc/business/productsservices/developers/ services/shippingmanifest/default.jsf	Not determined in their documentation. Not certain if they use it or not, or if it's hidden from shippers. Each Canada Post international label contains a CN22 form.
DHL	<xsd:schema xmlns:dhl="http://www.dhl.com/datatypes_global" xmlns="http://www.dhl.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.dhl.com" elementFormDefault="unqualified">	ETD availability is determined by destination. We use the GetRates method to determine so.
Purolator	https://eship.purolator.com/Site/content/developmentprocess/ websservicesprogram.aspx	Not determined in their documentation. Not certain if they use it or not, or if it's hidden from shippers.
UPS	developer.ups.com	Not determined in their documentation. Nevertheless, they generate ETDs automatically if your UPS accounts are enrolled in the UPS Paperless program.

NOTE: The endpoints detailed above might change depending on Carrier updates.