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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpostnord.com%2Fpostnord" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpostnord.com%2Fpostnord" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with PostNord API

Explore with Jentic One

View OpenAPI Document

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?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the PostNord API by hand means appending your apikey as a query parameter on every call to api2.postnord.com and threading the right track-and-trace or service-point endpoint yourself. Through Jentic you install once, import the PostNord API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

PostNord carries the parcel identifier and address in the query rather than as a path resource, so scoping is by operation: you limit the agent to the operations it needs, such as tracking a shipment or finding the nearest service point. Transit-time lookups are included only if you add that operation.

Credential isolation

Your PostNord API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'track a parcel in Sweden' or 'find the nearest service point', and Jentic returns the matching PostNord operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the PostNord API?

Yes. Because you run Jentic One yourself, your own rules decide which PostNord operations and credentials the agent may use, and scoping here works at the operation level since the parcel identifier and address travel in the query rather than as a path resource. You can allow only the operations the agent needs, such as tracking a shipment by identifier or finding the nearest service point by address or coordinates, while withholding others. Transit-time lookups are available to the agent only if you include that operation in its allowed set. The API key stays with your instance and is injected at execution, so it never reaches the agent's prompt or logs.

PostNord API

Name: PostNord API
Brand: PostNord API
Availability: InStock

AI ReadinessFoundational (D+)49/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticE CommerceShipping LogisticsapiKey6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

50%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PostNord API to your agent

Capabilities

Start building with PostNord API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PostNord API

Jentic AI Readiness Score

PostNord API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness