Using a different carrier? See Package Tracking.

Introduction

Zembula reads PostNord tracking through PostNord's Track & Trace API, with the API key of your own PostNord developer account. Zembula uses the key only to read tracking. It never books or changes your shipments.

This guide covers getting the key on developer.postnord.com and connecting it in the Zembula platform. You enter the key in Zembula yourself.

Who can do this

You need a PostNord customer number: PostNord's Customer plan requires one. PostNord's developer services are only for companies.

PostNord's terms don't let you give your API key to a third party, such as Zembula, unless PostNord approves it. Ask your PostNord contact to approve this before you connect. If PostNord doesn't approve it, you can't use PostNord tracking in Zembula.

In Zembula, only account Admins can connect PostNord. Other users can open the Package Tracking page, but they can't change it.

Before you go live

Each time an image with PostNord tracking loads, Zembula can ask PostNord for the latest scans. So each email open can use a PostNord call.

PostNord's Customer plan includes a free usage limit, and PostNord bills usage above it. Check your plan on PostNord's plans and pricing page before you go live. When PostNord refuses a call because too many arrive, the image can't show tracking for that load.

Create your developer account

Go to developer.postnord.com and sign up for the Customer plan.
Sign up with your company's details and your PostNord customer number.
PostNord emails you the production API key.

Use the production key. A sandbox account gets a separate test key, and Zembula only calls PostNord's production API.

Copy the key

Copy the API key from PostNord's registration email. You can also find it on developer.postnord.com under My Account → Applications, where each application shows its API key.

Keep the key private. Don't send it by email or chat. You enter it yourself in the Zembula platform in the next step.

Connect PostNord in Zembula

In the Zembula platform, open Data Sync → Integrations and select the Data integrations tab.
Click Set up on the Package Tracking tile. If Package Tracking is already set up, the button reads Open instead.
If Package Tracking is off, click Turn on. The page shows Setting up the builder source… and then Use INTERFACES › Package Tracking in the builder.
Under Carriers, click Add on the PostNord row.
Click Paste a key next to API key. The Paste your PostNord key dialog opens.
Paste the key into the dialog's API key field and click Connect.

The button reads Verifying… while Zembula saves the key. The PostNord row then reads Connected — starts answering within the hour.

Zembula doesn't test the key with PostNord when you connect. A wrong key shows up later as missing tracking. Check it with Try it below.

If order data is live for Package Tracking, the PostNord row reads Connected — waiting: carriers and order data can't run together until the next release. To switch, click Use PostNord instead. This turns order data off and PostNord on. Content that sends only an order ID then shows your fallback.

Try it

Add INTERFACES › Package Tracking to a draft image in the builder, turn on Simulate, and preview it with a PostNord tracking number. If a number you know is real shows no tracking, check the key and replace it if needed.

The Status section at the bottom of the Package Tracking page also lists anything that needs attention.

Using PostNord in your content

Send each shipment's tracking number in tracking_number and the carrier in carrier. Zembula doesn't work out the carrier from the tracking number, so always send the carrier.

You can send the shipment ID or the item ID of one parcel. With a shipment ID, Zembula shows the whole shipment. With an item ID, it shows that parcel.

A carrier value that contains PostNord goes to PostNord, in any case, with or without a space or an underscore between the words. For example: PostNord, Post Nord, PostNord SE, POSTNORD_DK or Portal PostNord.

Posten Norge goes to Bring, not PostNord. Posten and Post Danmark on their own don't go to PostNord.

What shoppers see

Status: the latest scan PostNord reports when the image loads, such as In Transit, Out for Delivery, Ready for Pickup or Delivered. Each scan shows PostNord's English description. A scan Zembula can't classify reads In Transit.
Estimated delivery: PostNord's estimated time of arrival, when PostNord gives one. PostNord says it may be a statistical estimate. After delivery it reads Delivered, with the delivery time.
Ready for Pickup: the service point's name and address, when PostNord gives them.
Several parcels: when you send a shipment ID for a shipment with more than one parcel, it doesn't read Delivered until every parcel is delivered. Until then it shows the latest status of a parcel that isn't delivered yet. A parcel that's ready for pickup or has a problem, such as a delay, comes first. Otherwise it's the parcel furthest behind.
Tracking link: the shipment's page on tracking.postnord.com.
No manage delivery link: PostNord's tracking doesn't give one.

Messages PostNord sends to the recipient, such as text messages and emails, appear in the scan list. They show as the current status only when PostNord has no other scan yet. For a scan at the recipient's door, such as a delivery, the image shows only the city and country, never the recipient's address.

Where your key is kept

The key is saved as an encrypted secret. It can't be read back: the platform only shows its last four characters. It's listed under Data Sync → Secrets & Configs, and it can only be sent to PostNord's API (api2.postnord.com).

To change the key, open the Package Tracking page and click Replace key next to API key on the PostNord row. To stop using PostNord, click Disconnect. PostNord still accepts the key until you regenerate it on developer.postnord.com.

More detail: Shared Secrets and Configs.