Units & formats

Use these units and formats in all requests.

Measurements

Field Unit Type Example
weight Grams (g) Integer 1000 = 1 kg
length, width, height Centimetres (cm) Number 12
volume Cubic decimetres (dm³ = litres) Integer 2
contentValue Norwegian kroner (NOK) Number 499

Dates and times

Date formats differ between endpoints. Don't assume one format everywhere.

Field Format Example Where
desiredDeliveryDate YYYYMMDD 20261014 Booking request
dates[] YYYY-MM-DD 2026-10-14 Get Available Pickup Dates response
eventTime YYYY-MM-DD HH:MM:SS, Norwegian local time 2026-10-13 13:46:07 Tracking events
eventTimeUtc ISO 8601, UTC 2026-10-13T11:46:07.028470Z Tracking events
timestamp ISO 8601, UTC 2026-06-05T12:59:31.131Z Error responses
from1, to1 HH:MM 07:00 Service point opening hours
plannedDeparture HHMM 2230 Single Address Check response

Converting pickup dates

The pickup-dates endpoint returns YYYY-MM-DD, but the booking expects YYYYMMDD. Remove the dashes before you send the date: 2026-10-14 → 20261014.

Use eventTimeUtc when you sort or compare tracking events.

Addresses

Field Format Example
countryCode ISO 3166-1 alpha-2, uppercase NO
zipCode String, 4 digits. Keep leading zeros. "0468"
address Street name, number, entrance and apartment number in one string Kongsberggata 18 H0201

Always send zipCode as a string. Sent as a number, 0468 becomes 468.

Helthjem only delivers within Norway, so countryCode is NO for all parties.

Field lengths

Field Max length
Party address 105
Party phone1, phone2 100
Party email 100
Party reference, contact 35
Item trackingReference 35
Item contents 100
idempotency-key header 40

Requests with longer values are rejected with 400.

Other formats

Field Format
expires_in (token) Seconds
locale (tracking) EN, NO or SE
Request and response bodies JSON, UTF-8
Last updated