For the complete documentation index, see llms.txt. This page is also available as Markdown.

Registers

Get registries

get
/registry

The method allows the user to get information about their registries or registries related to their profile in the registry.

🔸Registries are automatically filtered by creation source (clientapi or bc) depending on the method used. 🔸Shipments that were removed from the registry are not included in the response.

🔹Description of control elements:

SCHEMA Displays the full technical structure of the request or response, including field names, data types, required fields, allowed values, and validation rules.

  • Single line description A description that fits into a single line; any text that does not fit remains hidden.

  • Multiline description An expanded description that displays more than one line of text.

EXAMPLE Shows a ready-made sample JSON with correctly formatted values to demonstrate how a valid request or response should look.

Authorizations
AuthorizationstringRequired

Authorization JWT-token with a lifetime of 1 hour in header

Query parameters
isEURegistrybooleanOptional

Indicates that European registries should be returned.

Example: true
ids[]string[]Optional

Unique registry identifiers for which information should be retrieved. This parameter is required if the numbers parameter is not specified.

Example: 85544
numbers[]string[]Optional

Unique registry number for which information should be retrieved. This parameter is required if the ids parameter is not specified.

Example: CRPL0000004829
settlementIds[]string[]Optional

Unique settlement identifier.

Example: 22326
withShipmentsInfobooleanOptional

When set to true, the response includes extended shipment information in the shipmentsInfo array.

If omitted or set to false, the response contains only shipmentId and shipmentNumber in the shipments array.

Example: true
createdAtFromstring · dateOptional

Start date of the registry filtering period. Used to retrieve records created from this date onwards (inclusive). The createdAtFrom field must be a date before createdAtTo

Example: 23.09.2025
createdAtTostring · dateOptional

End date of the registry filtering period. Used to retrieve records created before this date (exclusive).

Example: 25.09.2025
pageintegerOptional

Number of page to return.

Example: 1
limitintegerOptional

Max number of items to return on page.

Example: 10
Responses
200

Registries list

application/json
current_pageintegerOptional

Indicates the current page number in the paginated response.

last_pageintegerOptional

Total number of available pages calculated.

per_pageintegerOptional

Number of registry records returned per page.

totalintegerOptional

Total number of registries that match the request criteria.

get
/registry

Create a shipment registry

post
/registry

The method is used to create a client registry of shipments, which combines multiple shipments into a single document for further processing.

This method is available for shipments from anywhere in the world to anywhere in the world.

Limitations for working with registers:

  1. A shipment can be added to a register only if the sender’s data (city, counterparty, address) are identical for all shipments being added.

  2. A shipment can be added only to one register — the same document cannot be added to multiple registers simultaneously.

  3. A shipment can be added to a register only until an express waybill has been created for it (or until the shipment has been scanned at a Nova Post branch/unit).

  4. A shipment marked for deletion cannot be added to a register.

  5. The maximum number of shipments in a single register is 100.

🔹Description of control elements:

SCHEMA Displays the full technical structure of the request or response, including field names, data types, required fields, allowed values, and validation rules.

  • Single line description A description that fits into a single line; any text that does not fit remains hidden.

  • Multiline description An expanded description that displays more than one line of text.

EXAMPLE Shows a ready-made sample JSON with correctly formatted values to demonstrate how a valid request or response should look.

Authorizations
AuthorizationstringRequired

Authorization JWT-token with a lifetime of 1 hour in header

Body

Registry creation request

descriptionstringRequired

Name of the registry.

shipmentsstring[] · min: 1 · max: 100Required

Array of unique shipment numbers for World parcels. Each shipment must belong to the same sender.

Responses
200

Registry successfully created.

application/json
idstringOptional

Unique identifier of the registry.

numberstringOptional

Registry number in the format: CR + alpha country code from the first shipment + unique number.

versionTrackingstringOptional

Registry version tracking identifier.

statusstringOptional

Registry status. After creation, the status is Open.

createdAtstring · date-timeOptional

Registry creation date.

updatedAtstring · date-timeOptional

Registry update date.

deletedAtstringOptional

Registry deletion date.

postedbooleanOptional

Registry posting status.

printedbooleanOptional

Registry printing status.

scannedBarcodesAmountintegerOptional

Number of shipments in the registry.

forScanBarcodesAmountintegerOptional

Number of shipments pending scanning.

descriptionstringOptional

Registry name specified during creation.

senderCompanyIdstringOptional

Sender company identifier.

senderCompanyTinstringOptional

Sender company TIN.

senderPhonestringOptional

Sender phone number.

senderCountryCodestringOptional

Sender country code in ISO 3166-1 alpha-2 format.

senderSettlementIdstringOptional

Sender settlement identifier.

senderSettlementExternalIdstringOptional
senderSettlementNamestringOptional

Sender settlement name.

senderDivisionIdstringOptional

Sender division identifier.

senderDivisionExternalIdstringOptional
senderDivisionNamestringOptional

Sender division name.

senderAddressstringOptional

Full sender address string.

post
/registry

Add shipments to registry

post
/registry/{id}/shipments

This method allows users to add a parcel to an existing shipment registry, which simplifies further shipping.

The method supports:

  • European shipments (shipment numbers such as SHPL...)

  • Ukrainian shipments (MEN/ID identifiers)

Limitations for working with registers:

  1. This method is available for shipments from anywhere in the world to anywhere in the world.

  2. A shipment can be added to a register only if the sender’s data (city, counterparty, address) are identical for all shipments being added.

  3. A shipment can be added to only one register — the same document cannot be added to multiple registers simultaneously.

  4. A shipment can be added to a register only until an express waybill has been created for it (or until the shipment has been scanned at a Nova Poshta branch/unit).

  5. A shipment marked for deletion cannot be added to a register.

  6. The maximum number of shipments in a single register is 100.

This method is used to add already created shipments to an existing registry.

🔹Description of control elements:

SCHEMA Displays the full technical structure of the request or response, including field names, data types, required fields, allowed values, and validation rules.

  • Single line description A description that fits into a single line; any text that does not fit remains hidden.

  • Multiline description An expanded description that displays more than one line of text.

EXAMPLE Shows a ready-made sample JSON with correctly formatted values to demonstrate how a valid request or response should look.

Authorizations
AuthorizationstringRequired

Authorization JWT-token with a lifetime of 1 hour in header

Path parameters
idstringRequired

Unique register identifier to which the shipment will be added.

Example: 111111
Body
shipmentsstring[] · min: 1 · max: 100Required

Array of shipment identifiers that should be added to the registry. Each shipment must belong to the same sender.

Responses
200

Registry

application/json
idstringOptional

Unique identifier of the registry.

numberstringOptional

Registry number.

versionTrackinginteger · nullableOptional

Registry version number.

statusstringOptional

Registry status.

createdAtstring · date-timeOptional

Date of registry creation.

updatedAtstring · date-timeOptional

Date of registry update.

deletedAtstring · nullableOptional

Date of registry deletion.

postedbooleanOptional

Mark of registry post.

printedbooleanOptional

Mark of registry print.

scannedBarcodesAmountintegerOptional

Number of shipments in the registry.

descriptionstringOptional

User name of the registry.

senderCompanyIdstring · nullableOptional

Sender company identifier.

senderCompanyTinstringOptional

Sender company TIN.

senderPhonestringOptional

Sender phone number.

senderCountryCodestringOptional

Sender country code.

senderSettlementIdstringOptional

Sender settlement identifier.

senderSettlementExternalIdstring · nullableOptional

External settlement identifier.

senderSettlementNamestringOptional

Sender settlement name.

senderDivisionIdstringOptional

Sender division identifier.

senderDivisionExternalIdstring · nullableOptional

External division identifier.

senderDivisionNamestringOptional

Sender division name.

senderAddressstringOptional

Full sender address.

post
/registry/{id}/shipments

Remove shipments from registry

delete
/registry/{id}/shipments

The method allows users to delete shipment from an existing client registry.

The method supports:

  • European shipments (shipment numbers such as SHPL...)

  • Ukrainian shipments (MEN/ID identifiers)

🔹Description of control elements:

SCHEMA Displays the full technical structure of the request or response, including field names, data types, required fields, allowed values, and validation rules.

  • Single line description A description that fits into a single line; any text that does not fit remains hidden.

  • Multiline description An expanded description that displays more than one line of text.

EXAMPLE Shows a ready-made sample JSON with correctly formatted values to demonstrate how a valid request or response should look.

Authorizations
AuthorizationstringRequired

Authorization JWT-token with a lifetime of 1 hour in header

Path parameters
idstringRequired

Unique register identifier from which the shipment must be removed.

Example: 111111
Body
shipmentsstring[] · min: 1 · max: 100Required

Array of shipment identifiers that should be removed from the registry. Each shipment must belong to the same sender.

Responses
200

Shipment successfully removed from registry.

application/json
idstringOptional

Unique registry identifier.

numberstringOptional

Registry number.

versionTrackinginteger · nullableOptional

Registry version number.

statusstring · nullableOptional

Registry status.

createdAtstring · date-timeOptional

Registry creation date and time.

updatedAtstring · date-time · nullableOptional

Registry update date and time.

deletedAtstring · date-time · nullableOptional

Registry deletion date and time.

postedboolean · nullableOptional

Indicates whether the registry has been posted.

printedboolean · nullableOptional

Indicates whether the registry has been printed.

scannedBarcodesAmountinteger · nullableOptional

Number of shipments in the registry.

descriptionstringOptional

Registry name.

senderCompanyIdstring · nullableOptional

Sender company identifier.

senderCompanyTinstringOptional

Sender company TIN.

senderPhonestringOptional

Sender phone number.

senderCountryCodestringOptional

Sender country code (ISO Alpha-2).

senderSettlementIdstringOptional

Sender settlement identifier.

senderSettlementExternalIdstring · nullableOptional

External settlement identifier.

senderSettlementNamestringOptional

Sender settlement name.

senderDivisionIdstringOptional

Sender division identifier.

senderDivisionExternalIdstring · nullableOptional

External division identifier.

senderDivisionNamestringOptional

Sender division name.

senderAddressstringOptional

Sender address.

senderAddressPartsobjectOptional

Structured sender address.

delete
/registry/{id}/shipments

Rename registry

put
/registry/{id}/rename

The method allows users to rename an existing registry.

The method supports:

  • European shipments (shipment numbers such as SHPL...)

  • Ukrainian shipments (MEN/ID identifiers)

🔹Description of control elements:

SCHEMA Displays the full technical structure of the request or response, including field names, data types, required fields, allowed values, and validation rules.

  • Single line description A description that fits into a single line; any text that does not fit remains hidden.

  • Multiline description An expanded description that displays more than one line of text.

EXAMPLE Shows a ready-made sample JSON with correctly formatted values to demonstrate how a valid request or response should look.

Authorizations
AuthorizationstringRequired

Authorization JWT-token with a lifetime of 1 hour in header

Path parameters
idstringRequired

Unique register identifier.

Example: 111111
Body
descriptionstringRequired

New name of registry.

Responses
200

Request successful. The registry was renamed.

application/json
idstringOptional

Unique registry identifier.

numberstringOptional

Registry number.

versionTrackinginteger · nullableOptional

Registry version number.

statusstring · nullableOptional

Registry status.

createdAtstring · date-timeOptional

Registry creation date and time.

updatedAtstring · date-time · nullableOptional

Registry update date and time.

deletedAtstring · date-time · nullableOptional

Registry deletion date and time.

postedboolean · nullableOptional

Indicates whether the registry has been posted.

printedboolean · nullableOptional

Indicates whether the registry has been printed.

scannedBarcodesAmountinteger · nullableOptional

Number of shipments in the registry.

descriptionstringOptional

Registry name.

senderCompanyIdstring · nullableOptional

Sender company identifier.

senderCompanyTinstringOptional

Sender company TIN.

senderPhonestringOptional

Sender phone number.

senderCountryCodestringOptional

Sender country code (ISO Alpha-2).

senderSettlementIdstringOptional

Sender settlement identifier.

senderSettlementExternalIdstring · nullableOptional

External settlement identifier.

senderSettlementNamestringOptional

Sender settlement name.

senderDivisionIdstringOptional

Sender division identifier.

senderDivisionExternalIdstring · nullableOptional

External division identifier.

senderDivisionNamestringOptional

Sender division name.

senderAddressstringOptional

Sender address.

senderAddressPartsobjectOptional

Structured sender address.

put
/registry/{id}/rename

Delete registry

delete
/registry/{id}

The method allows users to delete an existing registry.

🔸Currently, deleting the registry is only possible after deleting all shipments from the registry.

The method supports:

  • European shipments (shipment numbers such as SHPL...)

  • Ukrainian shipments (MEN/ID identifiers)

🔹Description of control elements:

SCHEMA Displays the full technical structure of the request or response, including field names, data types, required fields, allowed values, and validation rules.

  • Single line description A description that fits into a single line; any text that does not fit remains hidden.

  • Multiline description An expanded description that displays more than one line of text.

EXAMPLE Shows a ready-made sample JSON with correctly formatted values to demonstrate how a valid request or response should look.

Authorizations
AuthorizationstringRequired

Authorization JWT-token with a lifetime of 1 hour in header

Path parameters
idstringRequired

Unique register identifier of the registry to be deleted.

Example: 111111
Responses
200

Request successful. The registry was deleted.

application/json
successbooleanRequired

Indicates whether the registry was successfully deleted.

delete
/registry/{id}

Print parcel registry

get
/registry/print

The method allows users to receive a generated PDF file with a list of client parcels for further printing.

The response is returned as a generated file and contains a printable register with the list of shipments included in the selected registry.

🔹Description of control elements:

SCHEMA Displays the full technical structure of the request or response, including field names, data types, required fields, allowed values, and validation rules.

  • Single line description A description that fits into a single line; any text that does not fit remains hidden.

  • Multiline description An expanded description that displays more than one line of text.

EXAMPLE Shows a ready-made sample JSON with correctly formatted values to demonstrate how a valid request or response should look.

Authorizations
AuthorizationstringRequired

Authorization JWT-token with a lifetime of 1 hour in header

Query parameters
idintegerRequired

Registry identifier in the system.

Example: 85544
typestring · enumOptional

Type of printable document.

Applicable only to Ukrainian registries.

Available values:

  • international - international shipment documents
  • invoice - shipment invoices
  • marking - shipment marking labels
Example: internationalPossible values:
printSizeTypestring · enumOptional

Marking print size.

Applicable only to Ukrainian registries.

Required for type=marking.

Example: size_100_100Possible values:
copiesintegerOptional

Number of copies of the printed document.

Default: 1Example: 2
Responses
200

Generated file.

application/octet-stream
string · binaryOptional
get
/registry/print

Last updated