Skip to content

Table of Contents

  1. Why This Change?
  2. Who Should Use This Guide?
  3. Who Migrates First?
  4. Key Changes & Improvements
  5. Why Migrate Now?
  6. Need Help?

Migration Guide

Important for PL-based merchants: Please keep in mind that a Friends and Family phase is currently ongoing. If you’d like to be included in the first migration phase, please contact us.

Why This Change?

At InPost Group, our mission is to simplify your operations by reducing integration costs and complexity. As we expand internationally, it's essential that working with our services remains fast, seamless, and future-proof.

To support this, we are consolidating our services under a single REST API – the Global API. This unified entry point will cover core functionalities such as shipment creation and manifestation, ensuring consistency across markets. While some capabilities (like tracking) may remain separate initially, they will be aligned with our global strategy over time.

This guide will help you understand the upcoming changes and support your transition from legacy systems to the Global API.

Who Should Use This Guide?

This guide is for partners currently integrated with any of the following InPost APIs:

  • API v2 → api.paczkomaty.pl
  • API v4 PL → api-pl.easypack24.net
  • API TRUCKER → api-kurier.inpost.pl
  • PL API Gateway → api.inpost.pl
  • ShipX API PL → api-shipx-pl.easypack24.net

These APIs are now considered deprecated, meaning:

  • They remain active and fully operational.
  • No new major features will be added.
  • A sunset date has not yet been defined (as of October 2025).

We plan to announce clear deprecation timelines by late 2025 or early 2026. Your feedback during this period is crucial for ensuring a smooth transition.

Who Migrates First?

Our initial focus is on merchants with logistics contracts integrated with Poland and its local APIs.

Other markets will follow, including:

  • Italy → api-shipx-it.easypack24.net
  • UK → api-uk.easypack24.net
  • Mondial Relay → connect-api.mondialrelay.com

Key Changes & Improvements

Some features from legacy APIs will be reworked or gradually reintroduced in the Global API. Here's what to expect:

Access & Credentials

Authentication in the Global API is standardized across all markets, making integration simpler and more secure.

Authentication flow:

  • The Global API uses OAuth 2.0 for secure access.
  • You must obtain an access token using your client credentials before making API calls.
  • Tokens are scoped to specific permissions (e.g., api:shipments:read, api:points:read).

Steps to authenticate:

  1. Register your application via the InPost Developer Portal.
  2. Obtain client credentials (Client ID and Client Secret).
  3. Request an access token using the /oauth/token endpoint.
Authorization: Bearer {access_token}

Scopes and permissions:

Scopes define what your token can access. For example:

  • api:shipments:read – read shipment data
  • api:points:read – access locker and PUDO point data
  • api:labels:read – retrieve shipping labels

Token management tips:

  • Tokens have a limited lifespan – refresh them as needed.
  • Store tokens securely and avoid exposing them in client-side code.
  • Use environment-specific credentials for development, staging, and production.

📄 Full authentication guide

Points & Locker List

The Global API introduces a unified approach to accessing pickup and drop-off locations across all supported markets.

What’s new:

  • A single Points API now returns both lockers and PUDO points, regardless of country or region.
  • No need to query separate endpoints per market – one request gives you a complete, cross-market list.

This unified system simplifies location-based services and ensures consistency in user experience across borders.

Shipment Creation

The Global API streamlines shipment creation with a fast, consistent, and flexible process across all supported markets.

What’s new:

  • Synchronous processing – tracking numbers are returned immediately in the shipment creation response, enabling instant label generation and fulfillment.
  • Consistent structure across markets – the same request format applies whether you're shipping domestically or internationally, reducing integration complexity.
  • Support for international and domestic shipments – built-in handling of customs clearance data ensures smooth cross-border operations → shipping methods guide
  • Each reference field now has a dedicated purpose (e.g., for label printing, internal tracking).
  • Up to three merchant-defined searchable references are available for custom use, making it easier to locate shipments based on your own identifiers.
  • Asynchronous mode is planned as a future enhancement for high-volume or deferred processing scenarios.

This unified approach simplifies development and ensures reliable shipment handling across all regions.

Labels

The Global API offers flexible label generation options to support various operational needs.

Label formats supported:

Labels can be retrieved in multiple formats, either as a binary file or Base64-encoded content:

  • PDF

    • application/pdf;format=A4 – Scales the A6 label to fit an A4 page.
    • application/pdf;format=A6 – Returns the label in A6 portrait size (approx. ¼ of A4).

  • ZPL (Zebra Programming Language)

    • text/zpl;dpi=300
    • text/zpl;dpi=203

  • EPL2 (Eltron Programming Language)

    • text/epl2;dpi=203

  • JSON-wrapped formats (Base64 content in JSON object)

    • application/pdf+json;format=A4
    • application/pdf+json;format=A6
    • text/zpl+json;dpi=300
    • text/zpl+json;dpi=203
    • text/epl2+json;dpi=203

Pickups

The Global API introduces a simplified and more reliable pickup process, replacing legacy ad-hoc solutions.

What’s new:

  • One-time pickups now replace legacy ad-hoc pickup models.
  • No need to pre-assign shipments before creating a pickup order – reducing friction and setup time.
  • Duplicate pickup orders are blocked to prevent operational errors → details here.
  • A new cut-off times resource enables you to check same-day pickup availability by postal code, helping you plan more efficiently.

These changes are designed to streamline your logistics operations and improve pickup reliability across markets.

Tracking

The Global API introduces a unified and enhanced tracking experience across all supported markets and carriers.

What’s new:

  • Cross-market tracking events – standardized event types and statuses across countries.
  • Unified tracking history – consistent parcel journey data, regardless of origin or destination.
  • Webhook support – receive real-time updates via webhooks or query via API.

Key features:

  • Full coverage of international and domestic shipments.
  • Visibility into event locations such as warehouses, lockers, and APMs.
  • Support for exception events (e.g., missing at locker, cancelled, damaged).
  • Parcel history retention of up to 121 days.
  • End-to-end tracking of RTS (Return to Sender) parcels under the original outbound tracking number.
  • Cloud-based architecture for scalable and reliable tracking data delivery

Why Migrate Now?

The Global API is more than a technical upgrade – it's a foundation for the future of your integration with InPost services.

By migrating, you will:

  • Simplify integration – one API for multiple markets, less maintenance.
  • Reduce long-term costs – no duplicate integrations or custom fixes.
  • Stay future-proof – new features will be released only on the Global API.
  • Gain flexibility – adopt new services gradually, without disruption.

We understand migrations require planning. That’s why we’ve designed this process to be smooth and merchant-friendly. You can migrate at your own pace, with full support from our team.

Need Help?

Your success is our priority. If you have questions, need clarification, or want tailored guidance, our integration team is here to help.

📩 Contact your Local Integration Support Team anytime: