Parcel Replace Order API

This API enables replacing an order registered in DI

Content

[ 1 Purpose and use of Service ] [ 2 Setup ] [ 3 Environments / Endpoints ] [ 4 Authentication ] [ 5 Making a Request ] [ 6 Examples ] [ 7 Response ] [ 8 Error handling ]

Purpose and use of Service

Replace Order API is used to replace details for an existing order. Replacing will create a new order, cancel an old one and applies to all items in that order.

Setup

Make sure you have the following information at hand before proceeding.

	Example	Description

	Example	Description
Username (see Authentication section)	wsfoobar	A valid username.
Password (see Authentication section)	a-very-very-long-password	A password matching given username.

The user is a web service user
The user has access to the web service for editing orders
The user has access to the shop registered on the order

Environments / Endpoints

Consider using the TEST-endpoint while developing your system. By doing this you ensure that your test-data will not pollute any potential external systems.

TEST PUT	https://staging-ws.di.no/ws/json/parcel/booking/v-1/orders/{shipmentId}

TEST PUT	https://staging-ws.di.no/ws/json/parcel/booking/v-1/orders/{shipmentId}
PRODUCTION PUT	https://ws.di.no/ws/json/parcel/booking/v-1/orders/{shipmentId}

Authentication

This endpoint requires the user to be authenticated. Refer to the documentation here for more information on how to obtain a valid token to use in your request.

Making a Request

Notes

Clients using this API should not fail if new optional fields are added to the API. If a new field is added to the request or response on a later stage, existing clients should handle this in a way such as they just ignore the field.
Changes will be updated for all parcels/kolli for the shipment/order specified
You may have several patch operations in one request
If request contains remove operation it should be the last operation in the request
If one of the operations in a request is invalid the whole request will be interrupted
It is not possible to undo a replace request, but you can do several replace requests on the same shipment which will cause creating new order every time

Notes

It is neccessary to remove the servicePoint party to if it should be automatically re-assigned. This could be relevant if consignee address has been changed, and servicePoint should be re-evaluated and re-assigned.

Request-Headers

key	value example	comment

key	value example	comment
Authorization	Bearer "SECRET_WS_TOKEN"	See authentication on how to obtain a token
Content-Type	application/json

Request-Path-Parameters

Name	Example	Description

Name	Example	Description
shipmentId	70724761617883184	The message number of the order that will be replaced

Request-Body

JSON file containing an array of patch operations.. The current patch operations supported by JSON Patch are:

Name	Example	Description

Name

Example

Description

Replace

[
  { "op": "replace", "path": "/transportSolutionId", "value": 1 }
]

Replace the existing value with new value for specified path.
The old value is not stored, and can not be retrieved after replaced.

Description of each key:
“op“ → operation used
”path” → JSON Pointer used to specify which part of the model needs to be changed
”value” → The value that will be changed

Add

[
  { "op": "add", "path": "/parties", "value": 
    { "type": "servicePoint", "id": 1 }
  }
]

Add new value with the specified properties. Value object’s structure is dependant on the type of the object. Supported paths:

/parties see Parcel Booking API | Party
/items see Parcel Booking API | Item
/additionalServices see Parcel Booking API | Additional Services

Remove

[
  { "op": "remove", "path": "/parties/servicePoint" }
]

Removes an object from the order. Supported paths:

/parties/{type} see possible {type} options in Party.type section in Parcel Booking API | Party
/items/{itemNumber} Item/package number of the shipment. If there are 3 items in a shipment these items should have itemNumber 1,2 and 3.
/additionalServices/{key} The key for the service.

Edit operations available
See Parcel Booking API documentation for more details about use and definition of each path and value

Path	Operation supported	Value description	Example operation

Path	Operation supported	Value description
`/shopId`	`"op": "replace"`	Whole number, The shop this booking is made for.
`/shopDisplayName`	`"op": "replace"`	String, A user presentable name of the shopId.
`/transportSolutionId`	`"op": "replace"`	Whole number, A transport solution is a construct that contains multiple freight products
`/shipmentId`	`"op": "replace"`	String. ShipmentId is identificator for the entire order.
`/desiredDeliveryDate`	`"op": "replace"`	String, Date format yyyyMMdd. This date should be defined as distribution date.
`/desiredDeliveryTimePeriod`	`"op": "replace"`	String, Time format HHmm-HHmm (desiredDeliveryTimeStart - desiredDeliveryTimeEnd) Default value '2000-2200' will be used as delivery time interval if it is not given.
`/messageToCarrier`	`"op": "replace"`	String, Typically delivery instructions.
`/messageToConsignee`	`"op": "replace"`	String, This information can be placed on some shipping labels in the information field.
`/proofOfDelivery`	`"op": "replace"`	String, proof of delivery options. Possible values: NO_CONFIRMATION, SIMPLE_CONFIRMATION, SCAN, SCAN_AND_PICTURE, PICTURE
`/campaignMark`	`"op": "replace"`	Boolean, When set to true, an asterix (*) will be visible on some labels.
`/parties/{partyType}/type`	`"op": "replace"`	String, Type of party involved.
`/parties/{partyType}/id`	`"op": "replace"`	String, Identifier that can be used to identify the same party between different shipments.
`/parties/{partyType}/name`	`"op": "replace"`	String, Consignor/sender name
`/parties/{partyType}/countryCode`	`"op": "replace"`	String, Country code, according to ISO 3166-1
`/parties/{partyType}/postalName`	`"op": "replace"`	String, Consignor/sender city
`/parties/{partyType}/zipCode`	`"op": "replace"`	String, Consignor/sender postal code
`/parties/{partyType}/address`	`"op": "replace"`	String, Consignor/sender street address, number and household
`/parties/{partyType}/coAddress`	`"op": "replace"`	String, Consignor/sender co address
`/parties/{partyType}/phone1`	`"op": "replace"`	String, This can be used for automated SMS notification.
`/parties/{partyType}/phone2`	`"op": "replace"`	String, This can be used for automated SMS notification.
`/parties/{partyType}/email`	`"op": "replace"`	String, Consignor/sender email
`/parties/{partyType}/reference`	`"op": "replace"`	String, This can be an orderId or some other reference. consignee and consignor reference can be placed on some shipping labels.
`/parties/{partyType}/contact`	`"op": "replace"`	String, Contact information for the party. Consignee contact can be printed on some shipping labels.
`/items/{itemNumber}/itemNumber`	`"op": "replace"`	Whole Number, Item/package number of the shipment.
`/items/{itemNumber}/trackingReference`	`"op": "replace"`	String, If not specified as a part of the request this will be generated and returned in the response.
`/items/{itemNumber}/returnCode`	`"op": "replace"`	String, If specified this will be used for custom return functionality.
`/items/{itemNumber}/weight`	`"op": "replace"`	Whole Number, Measuring unit is gram.
`/items/{itemNumber}/volume`	`"op": "replace"`	Decimal Number, Measuring unit is cubic decimeter.
`/items/{itemNumber}/length`	`"op": "replace"`	Decimal Number, Measuring unit is centimeter.
`/items/{itemNumber}/height`	`"op": "replace"`	Decimal Number, Measuring unit is centimeter.
`/items/{itemNumber}/width`	`"op": "replace"`	Decimal Number, Measuring unit is centimeter.
`/items/{itemNumber}/contentValue`	`"op": "replace"`	Decimal Number, Currency is according to the location of the shopId.
`/items/{itemNumber}/externalSupplierId`	`"op": "replace"`	String, ExternalSupplierId is the id of the supplier to the shop. It can be used for access control or filtering.
`/items/{itemNumber}/contents`	`"op": "replace"`	String, Description of the contents. This can be placed on some shipping labels.
`/items/{itemNumber}/properties`	`"op": "replace"`	Map with additional properties. Various information (properties) are specified only for certain transport products.
`/additionalServices`	`"op": "add"`	Adds Additional services that should be applied to the shipment.
`/additionalServices/{key}`	`"op": "remove"`	Removes additional services that should be applied to the shipment.

Examples

Curl request replace consignee details

Curl request replace transport solution ID

Curl request remove party

Curl request add party

Response

Name	Type	Example	Mandatory	Description

Name	Type	Example	Description
shipmentId	string	(401)70712190172720651	See description with the same name in the request.
freightProductId	whole number	2	The selected freight product for this shipment. See example freight products ablow
parties	list of party objects		Note that the API could make minor changes to the returned consignee address.
items	list of item objects		See description with the same name in the request.
properties	map of properties		Map with additional properties. Various information (properties) are specified only for certain transport products.
additionalServices	list of additionalServices objects		See description with the same name in the request.

The response is the same as for Parcel booking API, see example and more details in that documentation.

Error handling

API requests that result in errors will return an appropriate HTTP status code to help you identify the type of error. You can use the table below to understand what each code means. og search online with the HTTP status code. The HTTP error keys used are based on the standard, and therefore available online (Tips to search “HTTP code XXX”)

In addition to HTTP status there may be more details in the errorKey field. Error Keys can be added at a later stage, clients should handle this as well as an empty value for errorKey.

HTTP Status code	Text	Description

HTTP Status code	Text	Description
400	Client or Validation Error	The request body/query string is not in the correct format.
401	Authentication Failure	Indicates that the Authorization header is either missing or incorrect. You can learn more about the Authorization header here.
403	Access denied	This indicates that the agent whose credentials were used in making this request was not authorized to perform this API call. It could be that you do not have access to the shop or transportsolution you provided in your request. If you believe this is a mistake, please reach out to your contact so it can be rectified.
405	Method not allowed	This API request used the wrong HTTP verb/method. For example a PUT request will result in this error.
4xx	Client error	Generally receiving an error code that starts with 4 indicates that the client needs to change something.
500	Unexpected Server Error	Oops! This may indicates an error on our side. Please try again, if the error continues notify your contact person

Error response

In addition to the HTTP status code, most errors will also return a response body that contains more information to help you debug the error. A sample error response is shown below. The format of the error response body is explained after the example.

Sample error

Field	Description

Field	Description
statusCode	The HTTP code associated with this error.
errorKey	A machine parseable error code.
errorMap	Additional details pertaining to the error.

Error keys

Error key	Status code	Action

Error key	Status code	Action
no.access.api	403	Your user does not have access to this API. Notify your carrier contact person to update your access
no.access.shop.id	403	Your user does not have access to the shop registered to the order you try to edit. Notify your carrier contact person to update your access
cannot.find.order	404	We can not recognise the shipmentID specified, please check that it is a valid and correct ID
unable.to.edit.exporter.order	400	For some carriers and freight products we do not have the possibility to edit and order after they have registered the order, therefor these orders can not be edited. See flow chart under “use of service” for details.
order.cancelled	400	It is not possible to edit cancelled ordres
no.changes.in.patch	400	The edit order request you are trying to perform does not have any changes from what information is already registered on the order.
invalid.format.desiredDeliveryDate	400	Please check your date format
order.changes.freightproduct	400	The edit order request you have will result in a different delivery method (freight product), and is not possible to perform. This can be for several reasons, maybe the date or address changes are not supported for the existing freight product
failed.to.parse.request	400	Please check your path value, we are not able to recognise the key. Remember this path value is case sensitive
JsonPatch.format.invalid	400	Please check you request format, see valid format in examples above.
failed.to.map.JsonPatch	400
distributionDate.must.be.in.future	400	Change distribution date.
error.parcel.final.status	400	Parcel has reach a final destination and can not be edited.
order.exported	400	For some carriers and freight products we do not have the possibility to edit and order after they have registered the order, therefor these orders can not be edited. See flow chart under “use of service” for details.
party.name.required	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
party.name.too.long	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
address.required	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
address.too.long	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
zipCode.required	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
email.too.long	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
phone.too.long	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
co.address.too.long	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
zipCode.too.long	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
postalName.too.long	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
countryCode.too.long	400	Required information and validation for each value is equal to the booking API, see details in Parcel Booking API documentation
error.parcel.under.distribution	409	Please see Parcel Edit Order API \| Use of Service for when parcels can be edited.
internal.error	500	If you receive this error please notify your carrier contact person, and provide the request(s) you try to perform

DI Services