Мethods
The Methods section contains Nova Post API tools for integrating core logistics processes into external systems and automating interaction with delivery services.
Last updated
The Methods section contains Nova Post API tools for integrating core logistics processes into external systems and automating interaction with delivery services.
Methods are grouped by key integration areas:
Authorization — obtaining API keys and JWT tokens for authorized requests;
Dictionaries — access to reference data required for building valid API requests;
Services — additional methods for specific service scenarios;
Shipments — creating, updating, calculating, and managing deliveries;
Courier delivery — creating and managing courier pickup requests;
Webhooks — receiving events and status updates automatically via subscriptions;
Fulfillment — managing goods, stock balances, orders, and inbound operations.
Each section includes endpoint descriptions, request parameters, response examples, and usage rules required for integration.
This is a collection of predefined requests for testing API methods, designed to simplify integration and eliminate the need to create requests manually.
The NovaPost API SDK is an official PHP library that simplifies integration with the Nova Post API. It provides ready-to-use methods for working with shipments, tracking, calculations, and other Nova Post services while supporting modern PHP standards and flexible customization.
Nova Post uses API versioning to introduce significant changes while keeping existing client integrations stable.
Each major API version is published separately in the API documentation. When a new major version becomes available, the previous version continues to operate during a transition period, allowing clients to plan and complete their migration without interrupting their services.
We use URL-based versioning. The version number is included in the API endpoint path:
https://api.novapost.com/v1.0/shipments - current version
https://api.novapost.com/v2.0/shipments - future version
When we release a new major version, the previous version enters a support period. Your existing integration continues to work unchanged until you are ready to migrate and to the .
Last updated