QIMA Logo

Supplier Introduction

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

The Supplier module lets you manage supplier and factory records in QIMA's system. Suppliers must exist in QIMA before you can reference them (via supplierCode) when creating an Inspection, Audit, or Lab Testing order. This module provides full CRUD (create, read, update, delete) for suppliers, plus a factory-confirmation API used during the inspection booking flow.

This page documents the shared setup used by every Supplier guide. Each API-specific guide links back here for authentication, headers, and environment details.

Base URL

All Supplier APIs are served from the QIMA Public API host for your environment:

https://ppapi.qima.com

For production integrations, replace the host with the QIMA API host provided for your environment.

Required Headers

Call the Auth API first (POST /auth/v2/token) before any Supplier request. See the Getting Started Guide or Get Token API for authentication setup.

HeaderLocationSourceDescription
Ai-Api-Access-TokenRequest header (all Supplier APIs)Provided by QIMARequest source identifier. Each client may have a different value per environment.
Ai-User-IdRequest header (all Supplier APIs)Auth API response userIdQIMA client user login ID of the authenticated user.
AuthorizationRequest header (all Supplier APIs)Auth API access tokenFormat: Bearer <access-token>. Use the token from the same Auth API session as the other headers.
RefererRequest header (all Supplier APIs)Fixed valuehttps://preprodmy.qima.com/

Common Authentication Errors

StatusMeaningRecommended Action
401 UnauthorizedToken or user authentication failed.Confirm the Authorization, Ai-User-Id, and Ai-Api-Access-Token headers are from the same Auth API session and environment.
403 ForbiddenThe user does not have access to the requested resource.Verify account permissions for the target Supplier operation.

Common Response Shape

Every Supplier API wraps its data in the same envelope:

{
  "message": null,
  "content": "... the actual data, shape varies per API ..."
}

Available APIs

APIMethodEndpointGuideAPI Reference
Create a new supplierPOST/user/v2/{userId}/supplierCreate GuideAPI Reference
Get supplier detailsGET/user/v2/{userId}/supplier/{supplierId}Detail GuideAPI Reference
Update a supplierPUT/user/v2/{userId}/supplier/{supplierId}Update GuideAPI Reference
Search suppliersGET/user/v2/{userId}/suppliersSearch GuideAPI Reference
Delete one or more suppliersDELETE/user/v2/{userId}/suppliers/{supplierIds}Delete GuideAPI Reference
Confirm inspection date and factoryPUT/order/v2/{orderId}/factoryConfirm Factory GuideAPI Reference

Integration Workflows

1. Authenticate (Required for All Flows)

POST /auth/v2/token

Extract userId, access token

Set Ai-User-Id, Authorization headers

2. Create and Manage a Supplier

1. POST /auth/v2/token

2. POST /user/v2/{userId}/supplier

Store id from response

Need to change details?

3. PUT /user/v2/{userId}/supplier/{supplierId}

Use supplierCode/id when booking Inspection, Audit, or Lab Testing orders

StepGuide
Create supplierCreate Guide
Update supplierUpdate Guide
Look up existing suppliersSearch Guide
Get full details of one supplierDetail Guide

3. Factory Confirmation (Inspection Booking Flow)

Use this when a supplier needs to confirm the inspection date, container ready date, and factory details for an order that was booked without full factory information (see Inspection Booking).

Inspection order created
without factory confirmed

PUT /order/v2/{orderId}/factory
password + inspectionDate + containerReadyDate

Order proceeds

StepGuide
Confirm factoryConfirm Factory Guide

Choosing the Right API

Your goalRecommended APIs
Register a new supplier before booking ordersCreate a Supplier
Look up existing suppliersSearch Suppliers
View full details of one supplierGet Supplier Details
Change a supplier's informationUpdate a Supplier
Remove suppliers no longer in useDelete Suppliers
Confirm factory/inspection details for a booked orderConfirm Inspection Date and Factory