The solution for Notification And Disclosure Of Information includes an API for relation notifications

Background:

The current solution requires:

• That the sender of the transport notification provides information about which master waybill(s) and waybill(s) (direct consignment) are included in the transport.
• That the sender of the consignment provides a reference to the parent master waybill number (or a parent transport for direct consigments) as well as a reference to the declaration in TVINN.

The industry has requested greater flexibility regarding which senders can take responsibility for ensuring that the necessary linking information is included in notifications submitted in the solution for notification and disclosure of information.

Norwegian Customs has therefore enabled actors to agree among themselves who is best suited to submit the necessary linking information by separating the links into dedicated relation notifications (called relation in the API).

Relation notifications are an addition to the current solution of submitting references in the respective notifications.

Relation-API:

Relation notifications follow a standard pattern:

• Create (POST) – The company creates a request ID, and the Norwegian Customs Authority creates and returns an MRN.
• Delete (DELETE) – The company submits the request ID and MRN.

The main principle is that the relation notification specifies the two MRNs (including MRN type) that identify the notifications to be linked.

If a link needs to be changed, this is done by deleting the submitted relation notification (DELETE in the API) and creating a new relation notification.

Similar to the fields for "representative" in transport, master, and house notifications, there should also be fields for representatives in the relation notification.

API documentation is included as part of the notification and disclosure of information APIs for each transport mode, under Relation for road API, similar for other transports modes. There are no explicit APIs for each relation type.

API for Lookup and Retrieval of MRN

If the sender of a relation notification does not know the MRN, Digitoll will provide a query API that allows MRN lookup for a notification if the sender has other identifying information about an object.

See API documentation for the road query API here.

Limitations:

Support is only provided for linking Digitoll notifications. Support for linking declaration IDs (from TVINN) to consignments (house) will be developed later, but is not included in the first version.

There is no support for submitting references to transit, Swedish export, mail bag (receptacle) and ATA carnet via relation notifications to link these to transports / consignments.

Relation notifications will not solve the industry’s challenges if the actors involved do not know each other or do not exchange necessary information. Relation notifications only make it more flexible who takes responsibility for collecting and submitting the information.

Case example:

• A freight forwarder submits the master consignment notification before a transport agreement is made. Digitoll issues an MRN for the notification.
• The carrier/driver submits a transport notification (unauthenticated solution or standard Digitoll) without reference to the master consignment notification. Digitoll issues an MRN for the notification.
  • The carrier/driver distributes the MRN for the transport notification to the actors they later agree to transport goods for.
• The freight forwarder submits a relation notification (MRN of master consignment notification and MRN of transport notification) to establish the necessary link when the freight is agreed upon.

Code example:

• Request:

  {
    "representative": "123456789",
    "parentObjectType": "TRANSPORT",
    "parentObjectReference": "24NO02091D3HAVFST5",
    "childObjectType": "MASTER_CONSIGNMENT",
    "childObjectReference": "24NO02091DW4BIEST4"
  }
                  

• Response: 202, 400, 401, 403, 415, 500 (like now)