Tracking events reference

Learn about interpreting Helthjem parcel tracking events — what each event means, how the event object is shaped, and how to consume it reliably in your integration.

Overview

Every scan, status change, communication, and delivery attempt for a parcel is recorded as a discrete event. A tracking lookup returns a shipment, which contains one or more items (parcels), each carrying its own ordered list of events. Events are identified by a unique apiKey, so your integration can react to specific milestones without depending on free-text descriptions.

Language

Event Log API can display events in 3 languages using the path parameter:

• English (EN),

• Norwegian (NO)

• Swedish (SE)

Response

• Response may include events for multiple parcels if:

  • The shipment contains multiple items.

  • A parcel changes delivery method (new tracking reference linked with original).

• Duplicate events can occur (margin < 0.001%).

• Clients must tolerate new event IDs or fields being added.

Event structure

A lookup returns an array of shipments. Each shipment has one or more items (parcels) — most shipments have exactly one. Each item carries its own parcelStatus and an ordered array of events. Events are returned newest first; sort explicitly by eventTime if you need chronological order.

Envelope — shipment → item → event

[
  {
    "shipmentNumber": "XXXXXXXXXXXXXXXXX",
    "shopName": "XXXX",
    "shopId": XXXX,
    "consigneeReference": null,
    "consignorReference": null,
    "properties": {},
    "items": [
      {
        "trackingNumber": "XXXXXXXXXXXXXXXXX",
        "returnCode": null,
        "freightProductId": 1,
        "freightProductName": "helthjem",
        "parcelStatus": "XXXX",
        "linkedParcelNumbers": [],
        "events": [ /* see below — newest first */ ]
      }
    ]
  }
]

Event object shape

{
  "eventTime": "2026-08-11 03:04:50",
  "eventTimeUtc": "2026-08-11T01:04:50.000904Z",
  "lat": null,
  "lon": null,
  "locationContext": "OSLO",
  "locationContextId": null,
  "eventType": {
    "apiKey": "013",
    "description": "Parcel delivered",
    "i18nKey": "event.type.distr.shipment.delivered"
  },
  "additionalInfo": {
    "apiKey": "012",
    "description": "in the mailbox",
    "i18nKey": "event.type.ai.distr.shipment.delivered.mailbox"
  },
  "eventGroup": {
    "id": 4,
    "name": "event.type.group.status"
  },
  "comChannelType": null,
  "changeUserId": null,
  "changeUsername": "flow-bud",
  "regSystem": { "id": 2, "name": "eBudbok" },
  "message": null,
  "eventData": null
}

Event groups

Event catalogue

Use this table to map codes to UI states and translations. /