GLS ShipIT REST API

Group-wide shipping integration web service (version 3.4.19) exposed by the GLS ShipIT backend, documented publicly as Doxygen reference pages. Resource groups cover shipment processing (POST /backend/rs/shipments, /shipments/cancel/{trackID}, /shipments/allowedservices, /shipments/endofday, /shipments/updateparcelweight), ParcelShop search (getParcelShopById, getParcelShopsByCountryCode, findNearestParcelShopForAddress, getParcelShopinDistance), parcel tracking (POST /parcels, /parceldetails, /parcelpod), delivery time-frame estimation (POST /backend/rs/timeframe/deliverydays) and sporadic collection scheduling (/backend/rs/sporadiccollection). Authentication is HTTP Basic over TLS 1.2 with an optional Requester header for data-protection logging; media types are application/glsVersion1+json and application/json. No baseURL is published — GLS states the endpoints for the centrally hosted service are obtained from the customer's primary GLS contact along with credentials, or point at a locally installed ShipIT backend. No OpenAPI, Swagger or WADL file is offered.

API entry from apis.yml

apis.yml Raw ↑
aid: gls-group:gls-shipit-rest-api
name: GLS ShipIT REST API
description: Group-wide shipping integration web service (version 3.4.19) exposed by the GLS ShipIT backend,
  documented publicly as Doxygen reference pages. Resource groups cover shipment processing (POST /backend/rs/shipments,
  /shipments/cancel/{trackID}, /shipments/allowedservices, /shipments/endofday, /shipments/updateparcelweight),
  ParcelShop search (getParcelShopById, getParcelShopsByCountryCode, findNearestParcelShopForAddress,
  getParcelShopinDistance), parcel tracking (POST /parcels, /parceldetails, /parcelpod), delivery time-frame
  estimation (POST /backend/rs/timeframe/deliverydays) and sporadic collection scheduling (/backend/rs/sporadiccollection).
  Authentication is HTTP Basic over TLS 1.2 with an optional Requester header for data-protection logging;
  media types are application/glsVersion1+json and application/json. No baseURL is published — GLS states
  the endpoints for the centrally hosted service are obtained from the customer's primary GLS contact
  along with credentials, or point at a locally installed ShipIT backend. No OpenAPI, Swagger or WADL
  file is offered.
humanURL: https://shipit.gls-group.eu/webservices/3_4_19/doxygen/WS-REST-API/index.html
tags:
- Shipping
- Parcel
- Track and Trace
- ParcelShop
- Pickup
- Freight
properties:
- type: APIReference
  url: https://shipit.gls-group.eu/webservices/3_4_19/doxygen/WS-REST-API/index.html
- type: Documentation
  url: https://shipit.gls-group.eu/webservices/3_4_19/doxygen/WS-REST-API/rest_shipment_processing.html
- type: Documentation
  url: https://shipit.gls-group.eu/webservices/3_4_19/doxygen/WS-REST-API/rest_parcel_shop.html
- type: Documentation
  url: https://shipit.gls-group.eu/webservices/3_4_19/doxygen/WS-REST-API/rest_tracking.html
- type: Documentation
  url: https://shipit.gls-group.eu/webservices/3_4_19/doxygen/WS-REST-API/rest_timeframe.html
- type: Documentation
  url: https://shipit.gls-group.eu/webservices/3_4_19/doxygen/WS-REST-API/rest_sporadic_collection.html