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

Pickups

Retrieve list of courier pickup requests

get
/pickups

This method allows business clients to retrieve a list of all courier pickup requests they have created. Clients can filter the list using specific parameters such as pickup IDs or pickup numbers. This method is available to business clients in EU countries where Nova Post operates.

🔹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
numbers[]stringOptional

Search pickups by document number. Can accept either a single search number or an array of numbers for conducting the search.

Example: PUCZ0000002671
ids[]integer · int32Optional

A list of pickup request IDs to search. Can accept either a single search number or an array of numbers for conducting the search.

Example: 28813
limitinteger · int32Optional

Max number of items to return on page.

Default: 15Example: 1
pageinteger · int32Optional

Number of page to return.

Example: 1
Responses
200

List of courier pickup requests retrieved successfully.

application/json
current_pageinteger · min: 1Optional

The current page of results in the paginated response.

last_pageinteger · min: 1Optional

The last available page in the paginated response.

per_pageinteger · min: 1Optional

The number of items per page.

totalintegerOptional

Total number of pickup requests matching the filter criteria.

get
/pickups

Create a courier pickup request

post
/pickups

This method allows business clients to create a new courier pickup request by specifying essential parameters such as the pickup address, parcel type, and additional details.

Initial Status (Draft): The pickup request is created in the Draft status, which allows clients to add all necessary shipments to the request.

Transition to Created: Once all shipments are added, clients must use the "Update pickup request status" method to change the status to Created. This indicates that the pickup is finalized and ready for processing by the courier service.

Time Intervals: To include a specific time interval for the pickup, clients should retrieve available time intervals using the corresponding method. This ensures that the requested pickup time aligns with the courier's schedule and availability.

This method is available to business clients in EU countries where Nova Post operates.

🔹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
notestring · max: 255Optional

Optional notes or instructions for the courier.

servicesstring[] · nullableOptional

List of additional services that can be included in the pickup request. This functionality is currently under development.

phonestring · min: 8 · max: 14Optional

The contact phone number of the sender, required to allow the courier to reach out if necessary.

emailstring · nullableOptional

While not mandatory, providing an email is recommended as a backup contact method in case the phone number is incorrect or for additional notifications regarding the pickup.

fullNamestring · max: 100Optional

Full name of the client sending the parcel, essential for identifying the sender and ensuring accurate handling of the pickup.

companyTinstring · min: 2 · max: 20Optional

The tax identification number (TIN) of a legal entity.

companyNamestring · min: 2 · max: 255Optional

Name of the company requesting the pickup.

countryCodestringOptional

ISO Alpha-2 code for the pickup location.

Pattern: ^[A-Z]{2}$
pickedTimeFromstring · date-time · nullableOptional

Start of the pickup time window, selected from available time intervals provided by the method that returns available time slots. If no time slot is specified, the courier will schedule the pickup at their discretion.

Pattern: ^20[0-9]{2}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}Z$
pickedTimeTostring · date-time · nullableOptional

End of the pickup time window, selected from available time intervals provided by the method that returns available time slots. If no time slot is specified, the courier will schedule the pickup at their discretion.

Pattern: ^20[0-9]{2}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}Z$
Responses
post
/pickups

Update a courier pickup request

put
/pickups/{id}

The method is used to update the details of an already created pickup request. It allows clients to modify information such as the pickup address, contact details, time window and other to ensure accurate and timely parcel collection. This method is available to business clients in EU countries where Nova Post operates.

🔹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
idinteger · min: 1Required

Unique identifier of the pickup request to be updated.

Body
notestring · max: 255Optional

Optional notes or instructions for the courier.

servicesstring[] · nullableOptional

List of additional services that can be included in the pickup request. This functionality is currently under development.

phonestring · min: 8 · max: 14Optional

The contact phone number of the sender, required to allow the courier to reach out if necessary.

emailstring · nullableOptional

While not mandatory, providing an email is recommended as a backup contact method in case the phone number is incorrect or for additional notifications regarding the pickup.

fullNamestring · max: 100Optional

Full name of the client sending the parcel, essential for identifying the sender and ensuring accurate handling of the pickup.

companyTinstring · min: 2 · max: 20Optional

The tax identification number (TIN) of a legal entity.

companyNamestring · min: 2 · max: 255Optional

Name of the company requesting the pickup.

lockVersioninteger · min: 1Optional

Version number for concurrency control to avoid conflicting updates. When using this method and making updates, the value of this parameter must be incremented by 1 for each subsequent change.

countryCodestringOptional

ISO Alpha-2 code for the pickup location.

Pattern: ^[A-Z]{2}$
pickedTimeFromstring · date-time · nullableOptional

Start of the pickup time window, selected from available time intervals provided by the method that returns available time slots.

Pattern: ^20[0-9]{2}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}Z$
pickedTimeTostring · date-time · nullableOptional

End of the pickup time window, selected from available time intervals provided by the method that returns available time slots.

Pattern: ^20[0-9]{2}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}Z$
Responses
200

Pickup request updated successfully.

application/json
idinteger · min: 1Optional

Unique identifier for the updated pickup request.

numberstringOptional

Reference number for the pickup request.

Pattern: ^[A-Z]{4}\d{10}$
statusstringOptional

Current pickup status, representing the different stages in the pickup process.

Possible values include:

  • Draft: Initial stage where the pickup request is created but not yet finalized.
  • Created: The pickup request has been created and is ready for processing.
  • AppointedCourier: A courier has been assigned to the pickup request.
  • InProgress: The pickup process is underway.
  • Done: The pickup has been successfully completed.
  • ClientCanceled: The pickup was canceled by the client.
  • NotCompleted: The pickup process could not be completed.
  • Deleted: The pickup request has been removed from the system.
  • ReceivedByCourier: The parcel has been received by the courier.
lockVersionintegerOptional

Updated version number for concurrency control.

notestring · max: 255Optional

Updated notes for the courier.

pickedTimeFromstring · date-timeOptional

Updated start of the pickup time window.

Pattern: ^20[0-9]{2}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}Z$
pickedTimeTostring · date-timeOptional

Updated end of the pickup time window.

Pattern: ^20[0-9]{2}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}Z$
statusesobject[]Optional

Array of updated status objects tracking pickup status changes.

put
/pickups/{id}

Update pickup request status

put
/pickups/{id}/status

This method allows updating the status of an existing courier pickup request. It is specifically designed for transitioning a pickup request from Draft to Created.

While the request is in Draft status, it remains in a preparatory phase where all necessary shipments can be added. Once the status is updated to Created, the shipment management system recognizes the pickup as finalized and ready for processing by the courier service.

🔹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
idinteger · min: 1Required

The unique identifier of the pickup request.

Body
statusstring · enumRequired

This field is used to update the status of a pickup request to indicate that the pickup request is finalized and ready for processing by the shipment management system.

Possible values:
lockVersioninteger · min: 1Required

Version number for concurrency control to avoid conflicting updates. When using this method and making updates, the value of this parameter must be incremented by 1 for each subsequent change.

notestring · max: 255Optional

A required note or comment providing additional information about the reason for the status update. This field must be filled when changing the status to ensure proper tracking and context.

Responses
200

Status updated successfully

application/json
successbooleanOptional

Indicates whether the status update was successful.

put
/pickups/{id}/status

Delete a courier pickup request

delete
/pickups/{id}

This method allows business clients to fully delete an existing courier pickup request. When a pickup request is deleted, it is marked as removed in the system, and the deletion date-time is recorded. This method is available to business clients in EU countries where Nova Post operates.

🔹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
idinteger · min: 1Required

Unique identifier of the pickup request to be deleted.

Responses
200

Pickup request deleted successfully.

application/json
deletedAtstring · date-timeOptional

The date-time when the pickup request was marked as deleted.

Pattern: ^20[0-9]{2}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}Z$
delete
/pickups/{id}

Remove shipments from a pickup request

delete
/pickups/{id}/shipments

This endpoint allows removing specific shipments from an existing courier pickup request.

🔹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
idinteger · min: 1Required

The unique identifier of the pickup request.

Body
Responses
200

Shipments removed successfully

application/json
delete
/pickups/{id}/shipments

Add shipments to a courier pickup request

post
/pickups/{id}/shipments

This method is used to add already created shipments to an existing courier pickup request. According to the established business process, already created shipments must be added to the courier pickup request after it has been created. This method is available to business clients in EU countries where Nova Post operates.

🔹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
idinteger · min: 1Required

Unique identifier of the pickup request to which shipments are being added.

Body
Responses
200

Shipments successfully added to the pickup request.

application/json
post
/pickups/{id}/shipments

Last updated