Supplier Confirm Factory Guide

Latest Update Time: 2026-07-02 00:00:00

Use this API to confirm the inspection date, container ready date, and factory details for an inspection order that was booked without the factory being auto-confirmed.

See the Supplier Introduction for base URL, authentication, and required headers.

Endpoint

PUT https://ppapi.qima.com/order/v2/{orderId}/factory

This API additionally requires the Content-Type: application/json header.

Prerequisites

In addition to the required headers and authentication setup:

An orderId from an Inspection order that needs factory confirmation (see Inspection Booking)

Path Parameters

Parameter	Required	Description
`orderId`	Yes	Inspection order ID.

Query Parameters

Parameter	Required	Description
`password`	No	Confirmation password: MD5-hash it, then SHA1-hash the result. Only needed in specific authorization contexts — most calls omit it.
`inspectionDate`	Yes	Confirmed inspection date, `YYYY-MM-DD`.
`containerReadyDate`	Yes	Date the container will be ready for loading, `YYYY-MM-DD`.

Request Body

Uses the OrderFactoryBean schema — factory identification, contact, location, and product lines. See the interactive API reference for the complete field list.

Request Example

curl --location --request PUT 'https://ppapi.qima.com/order/v2/<order-id>/factory?inspectionDate=2026-08-15&containerReadyDate=2026-08-15' \
  --header 'Ai-Api-Access-Token: {your api access token}' \
  --header 'Ai-User-Id: {your user ID}' \
  --header 'Authorization: Bearer {your token}' \
  --header 'Referer: https://preprodmy.qima.com/' \
  --data-raw '{
    "orderId": "<order-id>",
    "factoryId": "0ABD272CC7A8498EA4317986F1392E8F",
    "factoryName": "new-factory-su",
    "factoryMGRName": "louis.yi",
    "factoryMGRNumber": "+8612342312341",
    "factoryMGRMobile": "+868576710402",
    "factoryMGREmail": "louis.yi@qima.com",
    "factoryMGREmailList": ["louis.yi@qima.com"],
    "factoryAddress": "new street 123",
    "factoryCity": "12687656",
    "factoryCityName": "Shenzhen",
    "factoryProvince": "12578019",
    "factoryCountry": "23424781",
    "factoryContinent": "24865671",
    "factoryProductLines": "bigCat1_s1;bigCat1_s2",
    "factoryProductLinesList": ["bigCat1_s1", "bigCat1_s2"],
    "factoryAIOffice": "Shenzhen office",
    "isMutiLocation": "Yes",
    "supplierId": "402FA958F78743B68428A62BF4D6F71B"
  }'

The real capture's request body includes several additional internal/audit fields (keyValue, id, accessTime, recordIndex, table, keyName, createBy, createTime, updateBy, updateTime, seq) that appear to be echoed from a prior "get order" response rather than client-supplied input — trimmed from the example above. Sending them is likely harmless but not required.

Successful Response

HTTP 200 OK with content: true means the factory was confirmed successfully.

{
    "message": null,
    "content": true
}

Common Errors

See common authentication errors for 401 and 403 responses.

Next Steps

Use Get Inspection Order Details to verify the factory confirmation was applied.

Documents