> 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/documentation/get-registry-print.md).

# GET /registry/print

### General Information <a href="#general-information" id="general-information"></a>

| **Method name**  | The method of printing parcel registers |
| ---------------- | --------------------------------------- |
| **Direction**    | EU, UA                                  |
| **HTTP Method**  | GET                                     |
| **Route(s)**     | `/v.1.0/registry/print/?id={id}`        |
| **Autorization** | `Authorization: Bearer jwt-token…`      |

### Description <a href="#description" id="description"></a>

The method allows users to receive a generated PDF file of a registry for further printing.

**European registers** use only general registry type printing.\
**Ukrainian registers** (UA-World) can print\
\- general registry and\
\- international express waybills (IEW),\
\- markings of international express waybills,\
\- invoices of international express waybills.\ <br>

### Path parameters <a href="#path-parameters" id="path-parameters"></a>

| **Name**        | **Type** | **Value**                                                                                              | **Description**                                                                                  |
| --------------- | -------- | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
| id              | number   |                                                                                                        | Registry identifier in the OM system (mandatory)                                                 |
| type\*          | string   | <ul><li><code>international</code></li><li><code>invoice</code></li><li><code>marking</code></li></ul> | type of printed format (optional)                                                                |
| printSizeType\* | string   | <ul><li><code>size\_100\_100</code></li></ul>                                                          | <p>size of printed marking, mandatory for<br><code>type</code>= <code>marking</code><br><br></p> |
| copies\*\*      | number   |                                                                                                        | <p>Number of copies of printed document (optional)<br>Default value: 1</p>                       |

\* - applicable only for registers in direction Ukraine - World\
\*\* - applicable only for registers **excluding** direction Ukraine-World and Ukraine-Ukraine

### Request and response parameters <a href="#request-and-response-parameters" id="request-and-response-parameters"></a>

Request .../v.1.0/registry/print/?id={id}Response .../v.1.0/registry/print/?id={id}

### Acceptable HTTP status code  <a href="#acceptable-http-status-codes-response" id="acceptable-http-status-codes-response"></a>

| **HTTP-code** | **Status**            | **Description**                                                         |
| ------------- | --------------------- | ----------------------------------------------------------------------- |
| 200           | OK                    | Request successful. The server has responded as required.               |
| 422           | Unprocessable entity  | ErrorMessage: "The id field must be a number".                          |
| 500           | Internal Server Error | The specified registry was not found. ErrorMessage:"validation.invalid" |

&#x20;


---

# 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 dynamically by asking a question.

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

```
GET https://api-portal.novapost.com/changelog-1/documentation/get-registry-print.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.