🔑 GLS Tracking API Automation
The action is used to get the tracking information from GLS. It does not require any credentials from the client.
The GLS API Documentation can be found here: https://dev-portal.gls-group.net/apis (credentials in 1Pass)
The action uses the following endpoints:
- POST Authentication - to generate the access token
- GET Tracking - to retrieve the tracking information for a specified tracking number
Inputs
Name | Type | Description |
---|---|---|
Tracking Number | String | GLS tracking number |
Outputs
Name | Type | Description |
---|---|---|
Found Tracking? | Boolean | Whether the tracking information was found True / False |
Status | String | Tracking status: Ready for Shipment, Delivered, In Transit, Problem with Delivery, Returning to Sender, Ready for Pickup, Label Created |
Status Description | String | Detailed description of the tracking status |
Last Event Date | String | The date of the last tracking event. Format: YYYY-MM-DDThh:mm:ss |
Raw Data | Object | Raw Data |
Statuses mapping
{
"Label Created": [
"EPSEND",
"INFO.SIGSER-PILOT",
"INTIAL.PREADVICE"
],
"Ready for Shipment": [
],
"Delivered": [
"DELIVD",
"INFO.SIGWSUR",
"INFO.GREENDELIVER",
"PICKOK.NORMAL"
],
"In Transit": [
"CHANGD",
"CHECK",
"CLEAR",
"CONCON",
"CUDACA",
"FOWARD",
"INBOUD",
"INTIAL",
"LOADED",
"NDAYEV",
"OUTBOD",
"OUTDEL",
"RELEAS",
"UNLOCK",
"VOLPCL",
"WHOUSE.NORMAL",
"WHOUSE.AWAIT_PICKUP"
],
"Returning to Sender": [
"RETCUS",
"RETURN",
"WHOUSE.SPERETURN"
],
"Problem with Delivery": [
"CANCEL",
"CLLCAN",
"CLLCPB",
"CUSTPB",
"DORDOC",
"DSTROY",
"IDENT",
"INFO.PLOCK_RESEXC",
"INFO.INSTCAN",
"NOTDEL",
"NOUTDL",
"NTDEL2",
"PICKPB",
"PIKCAN",
"PIKPB2",
"PINOAT",
"REFUSD",
"REQRDL",
"RETDEL",
"SDAYDL",
"WHOUSE"
],
"Ready for Pickup": [
"CLLCTD",
"INFO.CONFIRMED",
"NOUTDL.AWAIT_PICKUP"
]
}
Updated 1 day ago