FAQ – Switching to the new tracking API

We have prepared answers to the most frequently asked questions regarding the update in the field of parcel tracking.

Download instructions


To enhance efficiency, security, and user experience, Pošta Slovenije will transition to a new cloud-based shipment tracking service on the Azure platform as of October 1, 2025.

What does the new system bring?

  • Greater reliability and resilience to outages
  • Enhanced security with advanced technologies and strict access control
  • Faster data processing and improved user experience
  • The ability to retrieve statuses for multiple barcodes simultaneously, reducing the number of service calls

How and where do I access the new service?

Contact your contract administrator. Your administrator will send you:

  • The URL of the new service
  • A username and password
  • An OAuth login token
What changes related to documents can I expect?

Upon activation, you will receive an updated “RC script” (examples of calls + responses) that replaces old documents.

What will happen to the existing keys and certificates (login data)?

Old data will no longer be valid. For the new service you will receive the following: new username, password, Bearer token and new URL.

What is the exact timeframe and will there be any interruptions?
Step Date & time What does that mean for you?
Old API shutdown 1 October 2025 at 00:01 This is the date and time when the old API will be finally shut down.
New API operation Already active The new API is already operational and you can start using it at any time prior to the above date.
Planned outages None As the new API is operating in parallel, we do not expect any tracking interruptions.
What will happen in the event of not switching to the new API by the deadline?
  • Tracking with the old API will no longer be available.
  • In the event of emergency, you can still use the Business Portal > Reports or the Tracking portal.
What are the key differences between the old and new API?
  • The login is carried out through an OAuth (Bearer token).
  • Changed JSON structure (new field names).
  • An option to run simultaneous queries for multiple barcodes.
Who is in charge of support and how can I contact them?

Your first contact: your contract administrator.
Technical support (email/phone): working hours from 8 a.m. till 3 p.m. You will receive data together with instructions.

How to test and validate the transition?

Use the RC script and login data that you receive from your administrator.

What actions are recommended for a smooth transition?
  • You can simultaneously use the old and new API until 1 October 2025 → we recommend a gradual migration.
  • Since a rollback after 1 October 2025 will not be possible, you should carry out the transition in time.
What are the benefits of the new tracking service?
  • Reliability: higher availability, resilience to outages.
  • Security: contemporary security practices and strict access control.
  • Speed: an optimised infrastructure for faster responses.
  • Fewer calls: one call can return statuses for multiple (up to 10) barcodes simultaneously.
What methods are available in the new tracking API?
  • A status for one barcode (in the past 60 days).
  • Statuses for multiple barcodes simultaneously (up to 10 in the past 60 days).
  • A status for one barcode (for the past 1 year).
  • Statuses for all postal items submitted for delivery in the past X days (max 5 days).
Will switching to the new tracking API in any way affect the API for submitting e-data on the transport of postal items?

No. The changes apply only to the tracking API.

What is the time validity of the OAuth token?

The validity (claim exp) is recorded in the JWT itself.

Is there any need to change our existing contract?

No. Switching to the new service does not require any change to your contract.