Parcel Last Mile delivery info API (? )

Template som utgangspunkt for API dokumentasjon som lages. Kun synlig for DI brukere

Enda ikke synlig for andre en DI brukere, endre synlighet når APiet legges i produksjon eller dokumentasjonen er klar

This API will provide details from last mile delivery

Content

Setup

	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 event log
The user has access to the shop the parcel is booked for

Environments / endpoints

TEST GET	http://staging-ws.di.no/ws/json/parcel/tracking/v-2/deliveryinfo/{identifier}
PRODUCTION GET	https://ws.di.no/ws/json/parcel/tracking/v-2/deliveryinfo/{identifier}

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

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.
Only parcels marked with API Key 124 will possibly provide results. Do not use this API for parcels who do not have that mark.
Client should handle empty images URLs, the URL may point to an empty site at any point and will always be empty after 30 days

Request header

Key	Value
Authorization	Bearer $SECRET_WS_TOKEN	see Setup
Content-Type	application/json

Path parameters

parameter

Example

Description

shipmentid

70724760120000880

35

Globally unique identifier for the shipment, typically a GINC code. Typically named MessageNumber, DocumentNumber or ConsignorsReference in EDI

trackingreference

370724760120000898

35

Unique identifier for an item/kolli in the shipment. This can be a SSCC code according to gs1, or a UPU S10 identifier.

Typically named TransporterInstructionMark in EDI.

pickupcode

R-12345

10

Optional additional unique identifier, used for pick up parcels

Curl request example

curl -X GET \
  https://dev-ws.di.no/ws/json/parcel/tracking/v-2/deliveryinfo/trackingreference/370724760120000898 \
  -H 'Authorization: Bearer $SECRET_WS_TOKEN' \
  -H 'Content-Type: application/json' \

Response

Name	Type	Example	Mandatory	Description
`parcelDeliveryProof`	`TrackingReference`	`URL`

Examples

Guidelines for use of image URLs

Clients should always link to URLs provided in this API when displaying the images.
Clients should NOT store a copy of the images provided though URL on their side. It is a violation of GDPR to store the image on client side.
Do not use the image provided directly on other sites, such as e-mail and SMS communication. Always provide a link to a site where the information is loaded directly from this API. If used directly the image may not be altered or removed by owner.
Do not send the URL we provide directly to a consumer, link consumers to a site where the client use the image URLs
We do not take responsibility for image quality or content

Example 1

{
    "parcelDeliveryProof": {
        "370724761842781669": [
            {
                "distrDate": "2021-04-29",
                "images": [
                    {
                        "imageUrl": "https://dev-img-budbuddy.aws.di.no/original/b4637de2-1e9c-40d9-b86f-be3becc9da49.jpg",
                        "note": null
                    },
                    {
                        "imageUrl": "https://dev-img-budbuddy.aws.di.no/original/0966a1f4-ec11-49d2-a429-20144d6861ef.jpg",
                        "note": null
                    }
                ],
                "labelImageUrl": "https://dev-img-budbuddy.aws.di.no/original/ec3bb3c0-f208-4080-9cf0-f759ace47041.jpg",
                "scanned": false,
                "timestamp": "2021-04-29T14:14:04.067746Z"
            }
        ]
    },
    "errors": {}
}

Example 2

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.

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.
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
statusCode	The HTTP code associated with this error.
errorKey	A machine parseable error code.
errorMap	Additional details pertaining to the error.