International shipment tracking API
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 nodes in the same field shape as the detail subset below.
Path {shipment_id} is create/detail id (live warehouse numeric PK as a string, e.g. "115"). Warehouse also accepts order_sn. Sandbox uses sbs_* / sb_shp_*. Optional language is for display copy in sandbox; the warehouse body is { "shipment_id" } only.
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>| Param | In | Required | Description |
|---|---|---|---|
shipment_id | path | yes | Shipment order ID |
language | query | no | Display copy (sandbox). Not forwarded in the warehouse body |
Response
Detail-aligned subset: id, order_sn, shipping_channel, international_tracking, status, status_label, timeline[].
{
"id": "118",
"order_sn": "JIYUNRI1358",
"shipping_channel": {
"code": "CJ-SEA",
"name": "E-commerce Sea - CJ"
},
"international_tracking": {
"tracking_number": null,
"carrier": null
},
"status": "PENDING",
"status_label": "Pending",
"timeline": [
{
"code": null,
"title": "Order created",
"occurred_at": "2026-08-23 11:14:58"
}
],
"request_id": "req_xxx"
}Field reference: response models.
Get Support
Need integration help? Contact Developer Support at support@hiobuy.com · Response within 1–2 business days