1. Introduction
2. Work Order Module API
2.1. Query Work Order API
2.1.1. SERVICE_TYPE
GLINK_QUERY_WORK_ORDER
2.1.2. Request Parameters
Query work order request
| Parameter | Type | List | Required | Notes |
|---|---|---|---|---|
| partnerId | string | N | N | Partner ID |
| ownerCode | string | N | Y | Owner code |
| warehouseCode | string | N | Y | Warehouse code |
| createdTimeFrom | string | N | Conditional | Creation time from. Format: yyyy-MM-dd HH:mm:ss |
| createdTimeTo | string | N | Conditional | Creation time to. Format: yyyy-MM-dd HH:mm:ss |
| updatedTimeFrom | string | N | Conditional | Update time from. Format: yyyy-MM-dd HH:mm:ss |
| updatedTimeTo | string | N | Conditional | Update time to. Format: yyyy-MM-dd HH:mm:ss |
| workOrderList | string | Y | N | Work order number list. Maximum 100 records. |
| workOrderType | string | N | N | Work order type. Specific values depend on the work order type configuration agreed by both parties. |
| status | string | N | N | Work order status: PENDING (pending), PROCESSING (processing), PROCESSED (processed), CLOSED (closed). |
| source | string | N | N | Work order source: WAREHOUSE_WORK_ORDER (warehouse work order), CUSTOMER_WORK_ORDER (customer work order). |
| page | int | N | N | Page number. Default: 1. |
| pageSize | int | N | N | Page size. Default: 100. Maximum: 200. |
When
workOrderListis empty, at least one complete start/end time range must be provided:createdTimeFrom/createdTimeToorupdatedTimeFrom/updatedTimeTo.
2.1.3. Request Example
JSON
{
"partnerId": "GLINK",
"ownerCode": "CUSTOMER001",
"warehouseCode": "WH001",
"createdTimeFrom": "2026-06-23 00:00:00",
"createdTimeTo": "2026-06-23 23:59:59",
"workOrderList": [
"WO202606230001"
],
"workOrderType": "RETURN_CHECK",
"status": "PROCESSING",
"source": "WAREHOUSE_WORK_ORDER",
"page": 1,
"pageSize": 50
}
2.1.4. Response Parameters
| Parameter | Type | List | Required | Notes |
|---|---|---|---|---|
| success | boolean | N | N | Success flag |
| code | string | N | N | Response code |
| message | string | N | N | Response message |
| total | long | N | N | Total record count |
| workOrderVoList | object | Y | N | Work order list |
| └ wmsWorkOrder | string | N | N | WMS work order number |
| └ workOrderType | string | N | N | Work order type |
| └ status | string | N | N | Work order status: PENDING (pending), PROCESSING (processing), PROCESSED (processed), CLOSED (closed). |
| └ taskStage | string | N | N | Work order task stage: RELEASED (released), ASSIGNED (assigned), PROCESSING (processing), SUSPENDED (suspended), COMPLETED (completed), CLOSED (closed). |
| └ ownerCode | string | N | N | Owner code |
| └ warehouseCode | string | N | N | Warehouse code |
| └ source | string | N | N | Work order source: WAREHOUSE_WORK_ORDER (warehouse work order), CUSTOMER_WORK_ORDER (customer work order). |
| └ workOrderTitle | string | N | N | Work order title |
| └ handler | string | N | N | Assigned handler |
| └ createdTime | date | N | N | Work order creation time |
| └ completedTime | date | N | N | Work order completion time |
| └ updatedTime | date | N | N | Work order update time |
| └ updatedBy | string | N | N | Work order updater |
| └ remark | string | N | N | Work order remarks |
| └ quantity | decimal | N | N | Work order header quantity |
| └ otherFeedbackRemark | string | N | N | Other feedback remarks |
| └ headerAttachmentList | object | Y | N | Work order header attachments |
| └ fileName | string | N | N | File name |
| └ url | string | N | N | File URL |
| └ otherFeedbackAttachmentList | object | Y | N | Other feedback attachments |
| └ fileName | string | N | N | File name |
| └ url | string | N | N | File URL |
| └ handlingList | object | Y | N | Work order additional activities |
| └ additionalActivity | string | N | N | Additional activity code |
| └ additionalActivityDesc | string | N | N | Additional activity name |
| └ unit | string | N | N | Unit |
| └ quantity | decimal | N | N | Quantity |
| └ remark | string | N | N | Remarks |
| └ skuItemList | object | Y | N | Work order related SKUs |
| └ skuCode | string | N | N | SKU code |
| └ qty | decimal | N | N | Quantity |
| └ relatedRemark | string | N | N | Related information remarks |
| └ feedbackRemark | string | N | N | SKU feedback remarks |
| └ attachmentList | object | Y | N | SKU business attachments |
| └ fileName | string | N | N | File name |
| └ url | string | N | N | File URL |
| └ imageList | object | Y | N | SKU images |
| └ fileName | string | N | N | File name |
| └ url | string | N | N | File URL |
2.1.5. Response Example
JSON
{
"success": true,
"code": "SUCCESS",
"message": "success",
"total": 1,
"workOrderVoList": [
{
"wmsWorkOrder": "WO202606230001",
"workOrderType": "RETURN_CHECK",
"status": "PROCESSING",
"taskStage": "PROCESSING",
"ownerCode": "CUSTOMER001",
"warehouseCode": "WH001",
"source": "WAREHOUSE_WORK_ORDER",
"workOrderTitle": "Returned Goods Inspection Work Order",
"handler": "operator01",
"createdTime": "2026-06-23 10:00:00",
"completedTime": null,
"updatedTime": "2026-06-23 11:00:00",
"updatedBy": "operator01",
"remark": "Please inspect the appearance of the returned goods.",
"quantity": 2,
"otherFeedbackRemark": "Processing",
"headerAttachmentList": [
{
"fileName": "work-order.pdf",
"url": "https://example.com/files/work-order.pdf"
}
],
"otherFeedbackAttachmentList": [],
"handlingList": [
{
"additionalActivity": "PHOTO",
"additionalActivityDesc": "Photo",
"unit": "COUNT",
"quantity": 2,
"remark": "Outer carton photos"
}
],
"skuItemList": [
{
"skuCode": "SKU001",
"qty": 2,
"relatedRemark": "Returned item",
"feedbackRemark": "Appearance is intact.",
"attachmentList": [
{
"fileName": "sku-file.pdf",
"url": "https://example.com/files/sku-file.pdf"
}
],
"imageList": [
{
"fileName": "sku-photo.jpg",
"url": "https://example.com/files/sku-photo.jpg"
}
]
}
]
}
]
}
2.2. Work Order Feedback API
2.2.1. SERVICE_TYPE
GLINK_WORK_ORDER_FEED_BACK
2.2.2. API Description
When the work order status or handling information changes, the platform pushes work order feedback information to the customer system according to configuration. The customer system must return the processing result.
2.2.3. Request Parameters
Work order feedback request
| Parameter | Type | List | Required | Notes |
|---|---|---|---|---|
| partnerId | string | N | Y | Partner ID |
| wmsWorkOrder | string | N | Y | WMS work order number |
| workOrderType | string | N | Y | Work order type |
| status | string | N | Y | Work order status: PENDING (pending), PROCESSING (processing), PROCESSED (processed), CLOSED (closed). |
| taskStage | string | N | N | Work order task stage: RELEASED (released), ASSIGNED (assigned), PROCESSING (processing), SUSPENDED (suspended), COMPLETED (completed), CLOSED (closed). |
| ownerCode | string | N | Y | Owner code |
| warehouseCode | string | N | Y | Warehouse code |
| source | string | N | Y | Work order source: WAREHOUSE_WORK_ORDER (warehouse work order), CUSTOMER_WORK_ORDER (customer work order). |
| workOrderTitle | string | N | Y | Work order title |
| handler | string | N | N | Assigned handler |
| createdTime | date | N | Y | Work order creation time |
| completedTime | date | N | N | Work order completion time |
| updatedTime | date | N | Y | Work order update time |
| updatedBy | string | N | Y | Work order updater |
| remark | string | N | N | Work order remarks |
| quantity | decimal | N | N | Work order header quantity |
| otherFeedbackRemark | string | N | N | Other feedback remarks |
| headerAttachmentList | object | Y | N | Work order header attachments |
| └ fileName | string | N | N | File name |
| └ url | string | N | N | File URL |
| otherFeedbackAttachmentList | object | Y | N | Other feedback attachments |
| └ fileName | string | N | N | File name |
| └ url | string | N | N | File URL |
| handlingList | object | Y | N | Work order additional activities |
| └ additionalActivity | string | N | N | Additional activity code |
| └ additionalActivityDesc | string | N | N | Additional activity name |
| └ unit | string | N | N | Unit |
| └ quantity | decimal | N | N | Quantity |
| └ remark | string | N | N | Remarks |
| skuItemList | object | Y | N | Work order related SKUs |
| └ skuCode | string | N | N | SKU code |
| └ qty | decimal | N | N | Quantity |
| └ relatedRemark | string | N | N | Related information remarks |
| └ feedbackRemark | string | N | N | SKU feedback remarks |
| └ attachmentList | object | Y | N | SKU business attachments |
| └ fileName | string | N | N | File name |
| └ url | string | N | N | File URL |
| └ imageList | object | Y | N | SKU images |
| └ fileName | string | N | N | File name |
| └ url | string | N | N | File URL |
2.2.4. Request Example
JSON
{
"partnerId": "GLINK",
"wmsWorkOrder": "WO202606230001",
"workOrderType": "RETURN_CHECK",
"status": "PROCESSED",
"taskStage": "COMPLETED",
"ownerCode": "CUSTOMER001",
"warehouseCode": "WH001",
"source": "WAREHOUSE_WORK_ORDER",
"workOrderTitle": "Returned Goods Inspection Work Order",
"handler": "operator01",
"createdTime": "2026-06-23 10:00:00",
"completedTime": "2026-06-23 12:00:00",
"updatedTime": "2026-06-23 12:00:00",
"updatedBy": "operator01",
"remark": "Returned goods inspection completed.",
"quantity": 2,
"otherFeedbackRemark": "The item appearance is intact.",
"headerAttachmentList": [
{
"fileName": "work-order.pdf",
"url": "https://example.com/files/work-order.pdf"
}
],
"otherFeedbackAttachmentList": [],
"handlingList": [
{
"additionalActivity": "PHOTO",
"additionalActivityDesc": "Photo",
"unit": "COUNT",
"quantity": 2,
"remark": "Outer carton photos"
}
],
"skuItemList": [
{
"skuCode": "SKU001",
"qty": 2,
"relatedRemark": "Returned item",
"feedbackRemark": "Appearance is intact.",
"attachmentList": [
{
"fileName": "sku-file.pdf",
"url": "https://example.com/files/sku-file.pdf"
}
],
"imageList": [
{
"fileName": "sku-photo.jpg",
"url": "https://example.com/files/sku-photo.jpg"
}
]
}
]
}
2.2.5. Response Parameters
| Parameter | Type | List | Required | Notes |
|---|---|---|---|---|
| success | boolean | N | Y | Customer system processing result. true indicates success, and false indicates failure. |
| code | string | N | N | Status code |
| message | string | N | N | Message |
| data | string | N | N | Extended response information |
2.2.6. Response Example
JSON
{
"success": true,
"code": "SUCCESS",
"message": "success",
"data": null
}