Pricing overview
PostNord's API pricing model is structured to accommodate various usage levels, from individual developers to large enterprises, primarily focusing on the Nordic logistics market. The pricing is usage-based, with different tiers offering varying numbers of API requests per month across its core products: the Delivery Tracking API, Delivery Checkout API, Service Point Finder API, and Address API. A free tier is available for initial development and low-volume applications, transitioning to paid subscription plans for higher request volumes.
The cost per request decreases at higher tiers, incentivizing larger-scale integrations. PostNord specifies distinct request limits for its Tracking API compared to other APIs within the same plan, acknowledging the potentially higher usage patterns for real-time parcel tracking. Developers can access detailed pricing information and manage their subscriptions through the PostNord developer pricing page.
Integrating with logistics APIs, such as those provided by PostNord, often involves considerations beyond direct API costs, including development time, infrastructure for handling webhooks, and data storage for tracking information. For example, processing real-time updates from a tracking API might require a robust event-driven architecture, a common pattern described in Google Cloud's messaging patterns documentation.
Plans and tiers
PostNord offers a tiered pricing structure designed to scale with an application's needs. Each tier provides a specific allocation of API requests per month, with separate limits often applied to the Tracking API due to its distinct usage profile. The plans are generally categorized by request volume, moving from a free tier to paid plans like "Small Business," "Medium Business," and "Enterprise."
The following table outlines the general structure of PostNord's API plans and their key characteristics as of 2026:
| Plan Name | Monthly Price | Tracking API Requests/Month | Other API Requests/Month | Best For |
|---|---|---|---|---|
| Free | €0 | 500 | 100 | Evaluation, small personal projects, very low-volume applications |
| Small Business | €29 | 5,000 | 1,000 | Startups, small e-commerce sites, basic tracking integrations |
| Medium Business | €99 | 20,000 | 5,000 | Growing e-commerce, medium-sized logistics operations, advanced integrations |
| Large Business | €299 | 100,000 | 25,000 | Established e-commerce platforms, logistics providers, high-volume tracking |
| Enterprise | Custom | Custom | Custom | Large corporations, complex logistics systems, bespoke requirements |
These plans generally reset monthly, with unused requests typically not rolling over. Overage charges may apply if request limits are exceeded on paid plans, although specific details on overage rates are typically found on the PostNord pricing documentation.
Free tier and limits
PostNord provides a free tier designed for developers to explore its API capabilities and for applications with minimal usage requirements. This free plan includes specific monthly request limits:
- Tracking API: 500 requests per month
- Other APIs (Checkout, Service Point, Address): 100 requests per month
The free tier is suitable for:
- Proof-of-concept development: Developers can test integrations and build prototypes without immediate financial commitment.
- Personal projects: Small-scale applications that do not require high volumes of logistics data.
- Initial evaluation: Businesses can assess the suitability of PostNord's APIs for their needs before committing to a paid subscription.
While the free tier offers a valuable starting point, its limits are designed to encourage migration to a paid plan as an application grows or moves into production with higher traffic. Exceeding these limits on the free tier typically requires upgrading to a paid plan to continue service without interruption. For example, if an application consistently makes more than 500 tracking requests in a month, upgrading to the Small Business plan would be necessary.
Real-world cost examples
Understanding PostNord's pricing involves considering typical usage patterns for various business scenarios. Here are a few real-world examples:
Small e-commerce startup
An e-commerce startup in Sweden selling handcrafted goods might process around 100 orders per month. For each order, they might use the Delivery Tracking API twice (once at dispatch, once for customer update) and the Delivery Checkout API once to offer shipping options. They might also use the Service Point Finder API occasionally for manual lookups.
- Tracking API: 100 orders * 2 requests/order = 200 requests/month
- Delivery Checkout API: 100 orders * 1 request/order = 100 requests/month
- Service Point Finder API: 50 requests/month
Total requests: 200 (Tracking) + 100 (Checkout) + 50 (Service Point) = 350 requests. This usage would comfortably fit within the PostNord Free plan (500 tracking requests, 100 other API requests). The 100 requests for "other APIs" would be met by the 100 Checkout requests, leaving the Service Point requests to potentially incur overage or require an upgrade if they exceed the free tier's "other APIs" limit.
Medium-sized online retailer
A medium-sized online retailer operating across the Nordics processes approximately 2,000 orders per month. They integrate the Delivery Tracking API for real-time updates, the Delivery Checkout API to present dynamic shipping options, and the Address API for address validation.
- Tracking API: 2,000 orders * 3 requests/order (dispatch, in transit, delivered) = 6,000 requests/month
- Delivery Checkout API: 2,000 orders * 1 request/order = 2,000 requests/month
- Address API: 2,000 orders * 1 request/order = 2,000 requests/month
Total requests: 6,000 (Tracking) + 2,000 (Checkout) + 2,000 (Address) = 10,000 requests.
This usage would exceed the Small Business plan (5,000 tracking, 1,000 other). The retailer would likely need the Medium Business plan at €99/month, which offers 20,000 tracking requests and 5,000 other API requests, providing ample headroom.
Logistics platform for multiple clients
A logistics software platform providing services to 50 small businesses, each averaging 500 shipments per month. The platform primarily uses the Tracking API and Service Point Finder API.
- Tracking API: 50 clients * 500 shipments/client * 4 requests/shipment (multiple status updates) = 100,000 requests/month
- Service Point Finder API: 50 clients * 100 requests/client = 5,000 requests/month
Total requests: 100,000 (Tracking) + 5,000 (Service Point) = 105,000 requests.
This scenario would necessitate the Large Business plan at €299/month, which includes 100,000 tracking requests and 25,000 other API requests. If the tracking requests consistently exceed 100,000, the platform might need to discuss an Enterprise plan with PostNord for custom pricing and higher limits.
How the pricing compares
When evaluating PostNord's API pricing, it's useful to compare it with other logistics API providers, particularly those operating in or serving the Nordic region. Key alternatives include Bring, DSV, and UPS, each with distinct pricing models and geographical focuses.
- Bring: As another major Nordic logistics provider, Bring offers APIs for similar services like tracking, shipping, and service points. Their pricing is often tailored to business agreements, and explicit public API pricing tiers might not be as transparent as PostNord's developer portal. Integration costs can vary significantly based on negotiated volumes and specific service level agreements.
- DSV: DSV is a global transport and logistics company. While they offer robust digital solutions and API access for freight and supply chain management, their primary focus is often on larger enterprise clients with complex logistical needs. Publicly available tiered API pricing for smaller developers is less common, with costs typically integrated into broader service contracts.
- UPS: UPS provides a comprehensive suite of APIs globally, including shipping, tracking, rating, and address validation. UPS often provides a free developer account for testing, but production API usage is typically tied to negotiated rates based on shipping volume or specific service agreements. For a developer primarily focused on the Nordic region, integrating with a global carrier like UPS might involve higher base costs or more complex setup compared to a regional specialist like PostNord. The UPS Developer Kit outlines their API access process, which often involves a registration and approval process.
PostNord's transparent, tiered pricing model with a clear free tier makes it accessible for small to medium-sized businesses and individual developers focused on the Nordic market. This contrasts with many global carriers whose API pricing is often embedded in broader service contracts or requires direct engagement for custom quotes. For businesses with a primary operational footprint in the Nordics, PostNord's pricing structure can offer a predictable and cost-effective solution compared to global alternatives that might charge premiums for regional specialization or require higher minimum commitments.