API tracking shipment quốc tế

Tra cứu bằng mọi mã được hỗ trợ

Khi không biết ID lô hàng HioBuy, hãy dùng GET /v1/fulfillment/tracking?sn={sn}. sn có thể là mã vận đơn (logistics_sn), mã đơn hàng kho (order_sn) hoặc mã bên ngoài do nhà phát triển cung cấp (client_order_sn). HioBuy chuyển nguyên giá trị và kho tự động xác định loại. Cần scope tracking:read. Không nhúng API Key vào mã trình duyệt.

GET /v1/fulfillment/shipments/{shipment_id}/tracking — warehouse → overseas recipient.

Not domestic procurement trace (seller → warehouse).
Not package tracking (HioBuy warehouse inbound timeline).
Not shipment detail: that response holds tracking numbers (international_tracking, shipping_legs[], boxes[].tracking) and warehouse business timeline[] (created / packed / paid). This route returns carrier scan events.

Path {shipment_id} accepts the HioBuy shipment id or the external_shipment_id supplied at create time. Numeric-only values are sent as shipment_id; any value containing a non-digit is sent as external_shipment_id. Prefix developer identifiers, for example shp_MY-ORDER-001.

Warehouse upstream: POST /api/gateway-worker/v1/shipments/track. Retired: POST /v1/fulfillment/shipments/logistics/trace.

Request

GET /v1/fulfillment/shipments/107/tracking?language=en
Authorization: Bearer <API_KEY>

Response

The response includes status, independent interception, and newest-first timeline[]. interception is null when no interception was requested; otherwise it reports the interception request state without replacing the shipment lifecycle status. Every event requires { code, status, title, occurred_at, details }; code is stable and non-null, occurred_at is timezone-aware ISO 8601, and details is {} when empty. Use code and status for program logic; title is localized display copy. Standard codes and interception semantics are documented in Shipments · timeline contract.