PostNord API
★ Only Publicly Available OpenAPI DocumentE CommerceShipping LogisticsapiKey6 EndpointsREST
For Agents
Track shipments across Nordic countries, find nearest pickup service points by address or coordinates, and calculate transit times between postal codes in Sweden, Denmark, Norway, and Finland.
Use for: I need to track a parcel shipment in Sweden, I want to find the nearest PostNord service point to an address, Check whether a shipment has been delivered, Get the estimated transit time between two postal codes
Not supported: Does not handle shipment booking, label generation, or customs declarations — use for tracking, service point lookup, and transit time estimation only.
Jentic publishes the only available OpenAPI specification for PostNord API, keeping it validated and agent-ready. The PostNord API provides shipment tracking, service point lookup, and transit time calculation for parcels in Sweden, Denmark, Norway, and Finland. It supports tracking by identifier or customer reference, finding nearest service points by address or GPS coordinates, and calculating expected transit times between postal codes across Nordic countries.
Install Jentic One Beta
Connect the PostNord API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PostNord API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with PostNord API.
Track shipments by tracking number or customer reference with event-level detail
Find nearest service points by street address with configurable result count up to 20
Locate pickup points by GPS coordinates for map-based location services
Calculate expected transit days between origin and destination postal codes
Retrieve service point details including opening hours and route distance
Support multi-language responses in English, Swedish, Danish, Norwegian, and Finnish
Use Cases
Patterns agents use PostNord API for, with concrete tasks.
★ Parcel Tracking Integration
Integrate PostNord shipment tracking into e-commerce platforms and customer portals. The API returns detailed tracking events with timestamps, event codes, and location data for each shipment. Supports tracking by PostNord identifier or seller-assigned customer reference number, enabling both carrier-level and order-level tracking without requiring end customers to know internal shipment IDs.
Track shipment with identifier 'SE123456789' using GET /rest/shipment/v5/trackandtrace/findByIdentifier.json and return the current status and estimated delivery date
Service Point Finder for Checkout Flows
Display nearby PostNord pickup locations during e-commerce checkout so customers can choose their preferred collection point. The API returns up to 20 service points sorted by distance, including address, coordinates, opening hours, and route distance in meters. Supports lookup by street address or GPS coordinates for both desktop address entry and mobile location-based flows.
Find the 5 nearest service points to postal code '11153' in Sweden (country code SE) using GET /rest/businesslocation/v5/servicepoint/findNearestByAddress.json
Transit Time Estimation
Calculate expected delivery times between Nordic postal codes for a given PostNord service type. The API returns transit days and expected delivery date, enabling accurate delivery date displays at checkout and logistics planning. Supports routes within and between Sweden, Denmark, Norway, and Finland with service-specific transit calculations.
Calculate transit time from postal code '11153' in Sweden to '2100' in Denmark for service code '19' using GET /rest/transport/v1/transittime/getTransitTimeInformation.json
AI Agent Logistics Monitoring
Enable AI agents to monitor Nordic shipment status and locate pickup points through Jentic. Agents discover tracking and service point operations via intent search, receive the operation schemas with required parameters, and execute queries without navigating PostNord developer documentation. Jentic handles API key injection so agents focus on shipment data interpretation.
Search Jentic for 'track a parcel in Sweden', load the PostNord tracking schema, and execute with a tracking identifier to retrieve delivery status and events
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for postnord api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/rest/shipment/v5/trackandtrace/findByIdentifier.json
Track a shipment by tracking number
GET
/rest/shipment/v5/trackandtrace/findByReference.json
Track a shipment by customer reference
GET
/rest/businesslocation/v5/servicepoint/findNearestByAddress.json
Find nearest service points by address
GET
/rest/businesslocation/v5/servicepoint/findNearestByCoordinates.json
Find nearest service points by GPS coordinates
GET
/rest/businesslocation/v5/servicepoint/getByServicePointId.json
Get service point details by ID
GET
/rest/transport/v1/transittime/getTransitTimeInformation.json
Calculate transit time between postal codes
GET
/rest/shipment/v5/trackandtrace/findByIdentifier.json
Track a shipment by tracking number
GET
/rest/shipment/v5/trackandtrace/findByReference.json
Track a shipment by customer reference
GET
/rest/businesslocation/v5/servicepoint/findNearestByAddress.json
Find nearest service points by address
GET
/rest/businesslocation/v5/servicepoint/findNearestByCoordinates.json
Find nearest service points by GPS coordinates
GET
/rest/businesslocation/v5/servicepoint/getByServicePointId.json
Get service point details by ID
GET
/rest/transport/v1/transittime/getTransitTimeInformation.json
Calculate transit time between postal codes
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
PostNord API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens and the apikey query parameter is injected automatically without exposing the raw key.
Intent-based discovery
Agents search by intent (e.g., 'track a parcel in Sweden') and Jentic returns matching PostNord operations with their input schemas, so the agent can track shipments without browsing PostNord developer docs.
Time to first call
Direct PostNord integration: 1-2 days for auth setup, endpoint discovery, and response parsing. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PostNord API through Jentic.
Why is there no official OpenAPI spec for PostNord API?
PostNord does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PostNord API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the PostNord API use?
The PostNord API uses an API key passed as a query parameter named apikey. You obtain a key from the PostNord developer portal. Through Jentic, this key is stored encrypted in the credential vault and injected automatically into requests.
Which countries does the PostNord API cover for shipment tracking?
The PostNord API covers Sweden (SE), Denmark (DK), Norway (NO), and Finland (FI). All service point and tracking endpoints accept country codes from these four Nordic countries. Transit time calculations support routes within and between these countries.
What are the rate limits for the PostNord API?
The PostNord API enforces per-key rate limits that depend on your developer account tier. Service point lookups return up to 20 results per request via the numberOfServicePoints parameter. Monitor response codes for rate limit indicators and implement backoff when needed.
How do I find the nearest pickup point through the PostNord API using Jentic?
Install the SDK with pip install jentic, then search for 'find nearest PostNord service point'. Jentic returns the findNearestByAddress operation schema requiring countryCode and at least a postalCode or city. Execute to receive service points sorted by distance with addresses, coordinates, and opening hours.
Can I track a shipment by order number rather than tracking ID?
Yes. The findByReference endpoint at /rest/shipment/v5/trackandtrace/findByReference.json accepts a customer reference number along with your PostNord customer number. This enables tracking by your internal order ID without requiring the PostNord tracking identifier.
GET STARTED