Create Finished Goods Inspections

If your inspections are carried out in another system, you can send the results to Inspectorio QRM with the Inspection API. Each request creates finished goods (FG) inspections from the inspection data you provide.

Before you start

• Generate an API key for your organization and use it to authenticate your API requests.
• Use the IDs of the organizations, product line, and product category as they are configured in Inspectorio.

Send the inspection data

Use the Create FG Inspections endpoint:

POST https://sight.inspectorio.com/integration-hub/events/v1/ics

The main fields of the request are:

Field	Description
receiverCustomId	The organization receiving the inspection. Set it to data_provider to use your own organization.
factoryCustomId	The factory that was inspected.
executorOrgCustomId	Optional. The organization that performed the inspection. Defaults to your organization.
inspectionTypeCode	The inspection type, for example DUPRO.
workflowUuid, bookingTemplateUuid	Optional. The workflow and booking template to use.
inspectionData[]	One entry per inspected item, with the result.

Each inspectionData entry requires internalIntegrationId, inspectedDate, opoNumber, itemId, style, color, size, productLineId, productCategoryId, inspectedQuantity, inspector (email), and result (pass or fail). You can also add defect details: defect, defectComment, defectSection (packaging, workmanship, or measurement), and occurrence.

{
  "receiverCustomId": "data_provider",
  "factoryCustomId": "Factory 01",
  "inspectionTypeCode": "DUPRO",
  "inspectionData": [
    {
      "internalIntegrationId": "1A2B",
      "inspectedDate": "2024-03-24",
      "opoNumber": "OPO_Number",
      "itemId": "Item A",
      "style": "Style 1A",
      "color": "Red",
      "size": "S",
      "productLineId": "PL-001",
      "productCategoryId": "PC-001",
      "inspectedQuantity": "100",
      "inspector": "[email protected]",
      "result": "fail",
      "defect": "Broken stitch",
      "defectSection": "workmanship",
      "occurrence": "2"
    }
  ]
}

Check the result

The request is processed asynchronously. A successful request returns 202 Accepted, meaning the message was queued, with one execution ID per queued message:

{
  "status": "Message received",
  "messageExecutionIds": ["d0236606-..."]
}

A 202 response confirms that the message was queued, not that the inspection was created. Keep the messageExecutionIds: include them when you contact [email protected] about a request.