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.

How to use this page

Start with Event Structure to understand the shape of a shipment/item/event payload, check the Event Catalog for the meaning of a specific event code, and use Code Samples as copy-paste reference payloads pulled directly from real captures.

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

ID	GROUP	DESCRIPTION
`1`	`import`	Information on shipments received/imported
`2`	`transportation`	Information on transportation
3	`communication`	Information on communication
4	`status`	Information on status updates
5	`scanner`	Information on scanning of shipments
6	`export`	Information for shipments transported by others
7	`external`	Information from/relating to external systems
8	`internal`	Information on internal processing
9	`images`

Event catalogue

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

`eventGroup`	`apiKey`	DESCRIPTION
`import`	001	Transport of parcel has been booked
`import`	158	we have received your parcel, and are getting ready to transport it in our network

	003	your parcel is being loaded for transport to its next checkpoint
	004	your shipment is transit and should be delivered within a few days
	006	parcel has arrived at local service point and is ready for pick-up
	062	the shipment has been loaded for transport
	063	parcel has been unloaded from car
	104	parcel is delivered to service point
	148	registration of shipment with external carrier failed
	152	communication sent
	153	communication failed
	155	pick-up deadline has been extended
	013	parcel delivered
	015	your delivery can’t be completed as expected. we will notify the recipient with updated information regarding your delivery
	028	we will try to deliver your shipment again
	029	we will try to pick up your shipment again
	030	unfortunately we are having problems with the delivery, and we are working to locate the parcel.
	031	our carrier attempted to collect your shipment, but was unfortunately unable to do so
	032	parcel has been picked-up by our carrier
	034	our carrier attempted to collect your shipment, but was unfortunately unable to locate the shipment
	035	parcel will be returned to web shop/sender.
	057	unfortunately we were not able to deliver your parcel tonight
	060	pick-up of parcel has been cancelled
Status	061	parcel marked as wanted. this parcel should be return to store/sender
Status	068	shipment not delivered
Status	069	parcel not acknowledged
Status	073	order has been cancelled
Status	076	the customer has changed date for shipment
Status	077	new activation in edg has been cancelled as the parcel has received a final status
Status	093	parcel has been sorted incorrectly and will unfortunately be slightly delayed
Status	095	parcel not picked up at service point and will be returned to sender
Status	100	the order has been changed
Status	112	destination have been changed
Status	113	parcel activated
Status	117	parcel ready for pick-up sent to consignee
Status	118	reminder parcel ready for pick-up sent to consignee
Status	119	pick-up period extended sent to consignee
Status	120	reminder for parcel ready for pick-up after extended period sent to consignee
Status	121	parcel returned sent to sender
Status	122	parcel delivered for return at servicepoint
Status	125	parcel is no longer wanted. to be delivered as normal
Status	136	the shipment item has been cleared by customs
Status	151	shipment distribution date changed
Status	154	fallback shipment solution was triggered
Scanner	016	parcel has been scanned
Scanner	017	no edi-information received for this parcel
Scanner	018	parcel scanned at wrong station. please change station and scan again
Scanner	019	can not find alias for this parcel, verify correct transport setup or split load carrier
Scanner	022	parcel is in transit
Scanner	024	parcel scanned in return mode
Scanner	107	load carrier has been received and is beeing loaded for transport
Scanner	115	parcel has return status, it can not be scanned in outgoing mode
Scanner	116	parcel has arrived at end station
Scanner	149	the parcel has been added to the customs report
Scanner	150	alias retrieved from cargostream
Export	026	parcel will be delivered by a partner carrier.
Export	126	partner carrier has recieved the parcel
Export	147	code for return is received/updated
External	036	unknown status notification from external transporter
Internal	094	label has been generated
Images	124	additional information for delivery available

Generate a label

B2C Integration