# May (3)

21 MAY 2026 **`UPDATED`**

Default application/json Content-Type for tracking push webhooks

<details>

<summary>Details</summary>

We've updated our tracking push subscription methods to set the default content type to `application/json` for new webhooks and responses, replacing the previous `text/plain` default. All previously created subscriptions will remain unchanged and continue to use `text/plain`.

</details>

20 MAY 2026 **`ADDED`**

Added shipment registry management methods

<details>

<summary>Details</summary>

Implemented unified registry handling functionality for Client API covering both shipment directions: Ukraine and Europe. The update introduces a single integration approach for registry creation and management across supported regions.

<a href="/spaces/LXGLYgqb2zoukydE2trn/pages/ru3YuWbqP1IDgJb4qG4D" class="button secondary">More details</a>

</details>

13 MAY 2026 **`UPDATED`**&#x20;

Added custom invoice attachments for business shipments

<details>

<summary>Details</summary>

Now, within the `invoice` array, you can:

* specify whether the invoice is client-provided;
* define the invoice type and its attributes;
* attach a scanned invoice file.

This allows the system to automatically determine the correct customs codes and synchronize data between the client, Nova Post systems, and customs authorities.

<a href="/spaces/LXGLYgqb2zoukydE2trn/pages/AOUIDlvQeAlnS7qUvK4Y" class="button secondary">More details</a>

</details>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://api-portal.novapost.com/changelog-1/2026/may-3.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.