Parcel Distribution Dates With Coverage Check API

The API provides a list of future distribution dates that have coverage for a parcel.

[ 1 Setup ] [ 2 Environments / endpoints ] [ 3 Authentication ] [ 4 Making a request ] [ 4.1 Path Parameters ] [ 4.2 Query Parameters ] [ 5 Response ] [ 6 Examples ] [ 7 Error handling ] [ 7.1 Error response ]

Setup

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

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

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 GET	https://staging-ws.di.no/ws/json/parcel/booking/v-1/distribution/{identifier}/dates
PRODUCTION GET	https://ws.di.no/ws/json/parcel/booking/v-1/distribution/{identifier}/dates

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.

Request-Headers

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

Path Parameters

Name	Example	Description

Name	Example	Description
identifier	(401)70712190172720651 / (00)370123460120012952	Identifier can be either a trackingReference or a shipmentId.

Query Parameters

Name	Example	Description

Name

Example

Description

limit

10

Optional. Number of days for distribution.

[1, 30]

14 days is the default if not provided.

Curl request example

curl --location --request GET 'https://ws.di.no/ws/json/parcel/booking/v-1/distribution/70724761617883184/dates?limit=7' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer $SECRET_WS_TOKEN'

Response

Responds with a list of future distribution dates for the freight product with the date format YYYY-MM-DD.

Examples

{
    "distributionDates": [
        "2024-03-08",
        "2024-03-09",
        "2024-03-11",
        "2024-03-12",
        "2024-03-13",
        "2024-03-14"
    ]
}

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.
404	Not found	The resource (i.e. parcel) for provided {identifier} does not exist.
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

{
    "statusCode": 401,
    "errorKey": "authentication.missing",
    "errorMap": {}
}

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.