Submits a request for Quotes from different couriers on Shippit.

At minimum, a Quote requires a delivery location and information on the parcels being delivered. However, different couriers and delivery methods can require additional fields to satisfy their requirements. There is a maximum of 1000 parcels per quote request.

Listing all quotes vs listing a single quote

By default, Shippit will return a quote from the fastest / cheapest courier. However, for the purposes of showing different options, such as in a courier selection page, you may want to have Shippit display all quotes. To do this, pass the return_all_quotes field as true.

Note that the quotes returned are filtered based on the requirements given by different couriers. Depending on the info submitted in the order and the carrier settings in the Shippit admin page, you may not see quotes from all configured carriers.

Submits an Order to be created on Shippit.

At minimum, an Order requires a delivery location, user details, and parcel details. Shippit will then generate the order, allocate the courier, and fill in the origin location based on the provided info and merchant configuration on Shippit.

Note that the required fields for an Order can vary depending on the type of order, the requested courier, whether it is local or international, etcetera.

There is a maximum of 1000 parcels per quote request.

---

Order Lifecycle

Standard and Express Lifecycle

Web UI action	API call	State on completion	Where seen in UI
Add order	POST order	New Order	New Orders page
Confirm order	GET label	Ready to Ship	Ready to Ship page
Cancel order	DELETE order	Cancelled	not visible
Book order	POST book	Booked	Track page

Click and Collect Lifecycle

Web UI action	API call	State on completion	Where seen in UI
N/A	POST order	Packing order	New Orders page
Label	GET label	Packing order	New Orders page
Cancel order	DELETE order	Cancelled	not visible
Book order	POST book	Booked	Track page

Unlike standard / express orders, click and collect orders do not proceed to the Ready to Ship page. They remain in the New Orders page until you call either the Book API or click the Label button.

Priority and Ondemand Order Lifecycle

Web UI action	API call	State on completion	Where seen in UI
N/A	POST order	Packing order	New Orders page
Label	GET label	Booked	Track page
Cancel order	DELETE order	Cancelled	not visible

Unlike standard / express orders, priority and ondemand orders do not need the book call. They are automatically booked by Shippit on the delivery date.

Ondemand orders are automatically booked by Shippit for an ASAP pickup, respecting store pick-and-pack time. Priority and Ondemand orders will remain on the New Orders page until dismissed by clicking the Label button or the GET label API call is made.

Order validation

If the validate field is passed and set to true, then the order is not saved unless Shippit can validate the destination suburb and postcode to be a valid combination. If a valid combination is not found, Shippit will return a suggested address.

Manual or Automatic Courier selection

You can allocate a courier to an order in one of two ways: you can manually specify the courier as part of the order, or you can allow Shippit to automatically allocate a courier for you.

To manually specify a courier, pass the courier_allocation field with the identifier of the courier (see below).

To have Shippit allocate the courier for you, pass the courier_type field to specify the type of couriers that Shippit can choose from to allocate for you. This is used to stand for a service level such as standard, express, priority, click_and_collect.

Specifying Parcels and Products

Shippit needs to know the specifications of the products you want shipped and what parcels to use in shipping them. There is a maximum of 1000 parcels per quote request.

In the simplest case, this can be specified by a parcel_attributes field, which contains a list of Parcel specifications. Each item specifies the number, dimensions, and other information about the products being shipped, and the associated parcel. In this case, each parcel contains one type of product.

For more complex shipping arrangements, you can additionally specify a product_attributes field, which contains a list of Product specifications. In this case, the parcel_attributes will no longer contain product information such as qty. Each item under product_attributes would specify the number, dimensions, and other information about the products; while each item under parcel_attributes would separately specify the dimensions of the parcels. By mixing parcel and product specifications, you can define arbitrary groupings of products into parcels.

The number of parcels is further determined by the Allocate each item in an order to a separate carton setting in the Shippit administration page. If this is enabled, then each item will be assigned a separate parcel according to its dimensions. If this is disabled, then Shippit may combine multiple product or parcel specifications into one.

Standard orders vs tracking orders

In a standard order, Shippit will book the courier given the provided information and provide tracking information and notifications for the merchant and recipient on the status of the order.

If you've already booked and allocated a courier to your consignment outside of Shippit, however, you can still use Shippit to provide tracking and notifications for the order. This is called a tracking order. In this case, you're only using Shippit for the tracking and notifications, and not for carrier booking.

Creating a tracking order is the same as creating a standard order, only that you have to provide additional attributes so that Shippit can match the the courier's internal info to shippit. Note the following attributes:

• tracking_only required -- true - this makes this order a tracking order.
• courier_allocation required -- the name of the courier in charge of the item.
• courier_job_id -- the ID assigned by some carriers to the shipment / consignment.
• parcel_attributes -> label_number required -- the label assigned by the carrier system to a parcel, used by Shippit to match the parcel number against the carrier's parcel number
• tracking_histories -- one or two optional status events that will be added to the tracking page for the benefit of the recipient.

Passing tracking histories

In a tracking order, you can choose to pass tracking histories for the benefit of the recipient. These are shown to the recipient in the tracking page to inform them of the status of when the order has been processed.

These items have just two fields, a status field and a timestamp in UTC format, to indicate to the recipient events such as order_placement and ready_for_pickup. The status informs the user of the Order's state at that point in time and can be either order_placed or ready_for_pickup. The timestamp indicates when that change happened. The following tracking history entries are recommended to be placed:

• order_placed - set to the time when you received the order on your system.
• ready_for_pickup - set to the time when you book the order on Shippit.

If no tracking_histories entries are passed, Shippit will generate an initial tracking history for the order, set to ready_for_pickup at the point when Shippit received the API request.

Authority to leave

• When using 500g satchels,

  • When specifying No, you must have Satchel 500g (A5) enabled in your settings (Settings > Pick & Pack > Automatic Package Sorting > Carrier Default Presets).
  • When specifying Yes, you must have Satchel 500g ATL (A5) enabled in your settings (Settings > Pick & Pack > Automatic Package Sorting > Carrier Default Presets).
  • If nothing is specified, we assume ATL = No

• Note that the final ATL value also depends on how couriers are allocated and if users manually override the ATL option in the UI. It is important when confirming quotes that the ATL is set as desired.

---

Service Level Mappings

Standard	Express	Priority	Ondemand
AlliedExpressOvernight	CapitalTransport	AlliedExpressSameday	DoorDashOndemand
AramexAuNz	CouriersPleaseExpress	Bonds	UberOndemand
AramexExpress	DirectCouriers	DoorDash
AramexInternational	EparcelExpress	EparcelOndemand
CouriersPlease	EparcelInternationalExpress	QxpressSameday
DhlEcommerce	FedExInternationalPriority	YelloOndemand
DhlExpress	KerryExpress
DhlExpressInternational	NewZealandPostExpress
DirectFreightExpress	NinjaVanExpress
Eparcel	PbtCourierExpress
EparcelInternational	SekoExpress
Fastway	SingPostExpress
FedExInternationalEconomy	StarTrackPremium
FourPXStandard	TntOvernightExpress
HunterExpress	TollPriority
Janio
JanioInternational
KerryStandard
LyneConnect
LynePlus
Neway
NewZealandCouriers
NewZealandPost
NinjaVanStandard
PbtCourier
Qxpress
SekoStandard
SingPost
Skybox
StarTrack
Tnt
Toll

Cancels an Order in Shippit using the tracking number.

The API first checks if the Order can be cancelled, ie., if its current state allows it, then returns an immediate response. If the Order is successfully cancelled, the API will answer with the Order with its state updated as cancelled. If it cannot be cancelled, it will throw a 422 error.

Retrieves labelling information for an Order using the tracking number.

The labelling information for an Order can only be retrieved once the Order has been processed and allocated a courier, which may take some time after the Order has been placed. If the Order is yet to be processed, you will get a 422 Unprocessable response.

This sends a tracking request to the API to retrieve the status of an Order.

This uses a pull-based model of Order tracking, which sends tracking info on each request. If you would like to use a push-based model where you automatically receive messages on Order status changes, you can subscribe to the Tracking Webhook instead.

Given an object with the desired settings to update, will update the Merchant settings on Shippit