Built on the official Status Tracking API
The adapter is built from Ukrposhta's official documentation (dev.ukrposhta.ua), not copied from another carrier: real endpoints, Bearer authorization, and the official status event codes.
Technical details
- Base
- https://www.ukrposhta.ua/status-tracking/0.0.1
- Authorization
- Authorization: Bearer {UUID}
- Endpoint
- GET /statuses/last?barcode=&lang=en
- CRM endpoint
- POST /api/v1/adapters/ukrposhta/{id}/tracking
Official event-code mapping
Ukrposhta numeric codes map to CRM shipment statuses.
What you get
- The Bearer token (UUID) is stored separately from the adapter secret
- The connection test validates the token before any request
- A barcode-list request returns mapped statuses
- A clickable link to the Ukrposhta tracking page
Setup
- 1
Get the Bearer token
The authorization bearer (UUID) is issued in the contract annex with Ukrposhta.
- 2
Paste the token and test
Enter the token in the adapter settings and click Test connection.
- 3
Poll tracking
A worker posts a barcode list to /tracking with X-Adapter-Secret and gets statuses.
Frequently asked questions
Can I create waybills?
In v1 it's status tracking. Declaration creation via the eCom API is planned separately as v2 (a multi-step flow).
Where do statuses come from?
From the official Ukrposhta Status Tracking API; we map the official event codes (10100, 20700, 41000, etc.) to shipment statuses.
Is the token secure?
Yes — it is stored server-side, never exposed to the browser, and used only for requests to Ukrposhta.
Add Ukrposhta tracking
Shipment statuses update automatically on the official API.
Start for free