🔑 Nacex Track and Trace
The action is used to get the tracking information from Nacex. Nacex is a carrier from Spain.
Credentials
The credentials are optained from your Nacex contact person. Please not you will need to ask for your web service credentials.
Inputs
Name | Type | Description |
---|---|---|
Tracking Number | String | Nacex tracking number |
Username | String | Nacex web service username. Please note that this is different than the username used to login into the business portal. |
Password | String | Nacex web service password. Password in MD5 format supplied by NACEX. Please note that this is different than the password used to login into the business portal. |
Outputs
Name | Type | Description |
---|---|---|
Success | Boolean | Whether the tracking information was found True / False |
Status | String | Tracking status: Delivered, In Transit, Problem with Delivery |
Tracking Link | String | Nacex tracking link |
Shipped Date | String | The date of the shipment. Format: DD/MM/YYYY |
Last Event Date | String | The date of the last tracking event. Format: DD/MM/YYYY hh:mm:ss |
Last Event | Object | A detailed description of the last tracking event |
Activity History | List | History of events for this package |
Shipment Id | String | The internal Nacex shipment Id for the package. This is needed to be able to generate return labels |
Delivery Address | String | The address where the package is/will be delivered |
Tracking Status
Nacex API returns a status code for the last tracking event. DG maps this status code to one of the predefined statuses. E.g. INCIDENCIA - Problem with Delivery.
Statuses mapping
Problem with Delivery = INCIDENCIA
In Transit = TRANSITO,REPARTO
Delivered= RECOGIDO, OK
More endpoints documentation here: https://pda.nacex.com/nacex_ws/doc/es.documentacion.html
Updated about 1 year ago