> For the complete documentation index, see [llms.txt](https://api-portal.novapost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-portal.novapost.com/changelog-1/2026/october-2.md).

# October (2)

26 OCT 2026 **`UPDATED`**

Discontinuation of `externalId` for Division Identification

<details>

<summary>Details</summary>

From **January 1, 2027**, the internal logic and purpose of the `externalId` field in the response of the `GET /v.1.0/divisions` method will change. The `items[].id` field must be used to identify divisions.

<a href="https://api-portal.novapost.com/checklists/change-in-the-semantics-of-the-externalid-field-in-the-division-directory" class="button secondary">More details</a>

</details>

16 OCT 2026 **`ADDED`**

Upcoming API Changes: New Product Data Requirements for Shipments to the EU

<details>

<summary>Details</summary>

From **November 1, 2026**, new requirements for the information submitted to customs authorities during the customs clearance of goods sold online and imported from countries outside the EU will come into effect in the European Union.

The main change concerns **Product Identifiers (PID)** for B2C shipments. The new requirements involve providing more detailed information about each product to ensure its traceability and simplify customs control.

In this regard, **Nova Post is working on an API extension** that will add three new fields for providing information about each product item in shipments from Ukraine to the EU.

**What do clients need to do?**

We recommend starting to prepare your systems and integrations for the new requirements now to ensure that **additional data can be provided from November 1, 2026** when creating shipments.

<table><thead><tr><th width="85">Field</th><th width="135">Required</th><th width="115">Type</th><th width="150">Recommended length</th><th>Example</th></tr></thead><tbody><tr><td>mPid</td><td>Yes</td><td>string</td><td>up to 50 characters</td><td>GIFT-MUG-LOGO-RED</td></tr><tr><td>nsPid</td><td>Yes</td><td>string</td><td>up to 50 characters</td><td>PROMO-MUG-350ML</td></tr><tr><td>sPid</td><td>Yes</td><td>string | null</td><td>up to 30 characters</td><td>5901234567890</td></tr></tbody></table>

**Important:** the new fields are currently unavailable in the API production environment. Nova Post is working on their implementation. Detailed technical specifications of the fields, completion rules, and information about their availability are published in this [article](https://api-portal.novapost.com/checklists/changes-to-eu-customs-clearance-rules-for-goods-from-november-1-2026).

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://api-portal.novapost.com/changelog-1/2026/october-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
