Create a shipment
The access token received from the authorization server in the OAuth 2.0 flow.
Create simple shipment request
Create return shipment request
Carrier constraints to ignore when creating a shipment. If not specified, all constraints will be checked. While our service constraints are based on carrier specifications, like size, these specifications are often vague and difficult to enforce. To allow for this, we provide a way to ignore specific constraints when creating a shipment. ** Note that this is not a replacement for the service constraints, it is only a way to ignore specific constraints when creating a shipment. And the API consumer is still responsible for ensuring that the shipment is valid. **
SIZE The request has succeeded.
Shipment resource
At last shipment id
Data used to specify address and receiver/sender details to create a shipment and collection. The data send in these address details are NOT verified. It's the responsibility of the caller to ensure the address data is correct or shipment/collection requests can fail.
Data used to specify address and receiver/sender details to create a shipment and collection. The data send in these address details are NOT verified. It's the responsibility of the caller to ensure the address data is correct or shipment/collection requests can fail.
AWAITING_BOOKING, READY, ONGOING, COMPLETE, CANCELED, FAIL Shipment Reference.
1 - 20Optional shipping reference (might not be suported by all carriers)
1 - 20BOOKED, COLLECTED, AT_HUB, IN_TRANSIT, OUT_FOR_DELIVERY, FAILED_ATTEMPT, DELIVERED, ON_HOLD, ADDRESS_ISSUE, RETURNED_TO_SENDER, TRACKING_EXPIRED, CANCELLED, AWAITING_CUSTOMER_COLLECTION, PACKING, MISSING, DAMAGED AWAITING_BOOKING, READY, ONGOING, COMPLETE, CANCELED, FAIL Resovled collection time slot