The Shipment Server API is a hosted web service that can build a shipment and deliver a label ready for print. It is aimed at customers who want a standard delivery management platform, but also want full control over their integration. You can integrate nShift DeliveryHub (Shipment Server) in your own business systems, and have full control of your customized production view.
This article will explain, without any technical details, what you need to know before you begin using Consignor Shipment Server API:
If you are looking for information about the technical implementation, see these articles:
- Getting started with Shipment Server integration
- Overview of methods
- Implementation and request examples
The basic flow - how does it work?
You send a request to the Shipment Server web service with your shipment data and get back a label.
To get a successful response from the web service, your request must contain all the information necessary to create a shipment. This can vary from carrier to carrier, but the basic information is receiver name and address, carrier product and services, parcel weight, and content.
A successful request will usually result in a response from the web service with a label. The Shipment Server does not handle the printing of the labels. It is up to you to develop a solution for this that fits your environment.
Some carriers need to receive electronic data (EDI) about the shipments. Consignor automatically generates the correct data format, but you must tell the web service when you want to transmit the EDI or set up automatic transmit. Some carriers consider a booking to be final as soon as the label is printed and do not need any EDI. Once a booking is final, it can usually not be updated.
Getting the right carriers
nShift has the largest carrier library in the world, and we maintain all our carrier integrations to meet the carriers' label and data requirements. With nShift DeliveryHub (Shipment Server), you only need to use one API to have access to hundreds of carriers.
To make the right setup for you, you must tell nShift which carriers and what products and services you will be using. If in doubt about the products and services, ask your carrier contact. You will need an agreement with the carriers we activate on your setup.
When a new customer is set up, nShift will need to pass a test procedure between nShift and the carriers. This test procedure helps ensure high quality when the solution is put into production.
Customized setup and Actor ID
To get started, you need a Shipment Server license and a unique Actor ID. The Actor ID identifies you when you make requests to the web service. The Actor ID is created by nShift and contains all the information set up by us. Information like customer number at the carrier, product codes, and number ranges are examples of information hosted by nShift and stored under your Actor ID. We make a customized set-up for you with your customer-specific data.
Contact us to get your setup and Actor ID for Shipment Server.