Manage sub-suppliers

When to use this. A sub-supplier is any external company a supplier works with as part of their production network: fabric mills, trim suppliers, printing houses, embroidery workshops, and similar partners. Suppliers maintain their own library, which brand customers can then view to gain supply chain visibility. Use these endpoints to create, update, and query that library on behalf of a supplier organisation, or to read sub-suppliers across organisations your account has access to.

The workflow

Sub-suppliers belong to a supplier organisation. The typical path is to create the sub-supplier with location and contact details, optionally update or archive it as the relationship evolves, and soft-delete it when it is no longer part of the supply chain.

Create the sub-supplier

POST /api/organizations/{organizationId}/sub-suppliers to add one or more sub-suppliers to a specific supplier org, including the primary contact and relation type. Alternatively, use POST /api/sub-suppliers if your token is already scoped to the supplier org.

Retrieve or list

GET /api/sub-suppliers/{id} to fetch a single sub-supplier, or GET /api/sub-suppliers to list them with filters (country, relation type, custom ID, free-text search).

Update details

PUT /api/sub-suppliers/{id} for a full replace, or PATCH /api/sub-suppliers/{id} for partial JSON Patch updates (e.g. updating only the website or archiving). Use PUT /api/sub-suppliers to update multiple sub-suppliers in a single request.

Archive or delete

Set state to archived via PUT or PATCH to hide a sub-supplier from active lists without removing history. Call DELETE /api/sub-suppliers/{id} to soft-delete it and cascade to its contacts and associated facilities.

Walkthrough

Create a sub-supplier in your own organisation with POST /api/sub-suppliers. The body is an array: one or many sub-suppliers are created in a single all-or-nothing transaction. If any item fails validation or its name already exists in the organisation, nothing is created.

curl -X POST "https://service.my.delogue.com/api/sub-suppliers" \
  -H "Accept: application/json" \
  -H "X-Auth-Token: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '[
  {
    "name": "Foshan Brightweave Textiles Co., Ltd",
    "customId": "10004",
    "relationType": "styleSupplier",
    "address": "Unit 12, Building 3, No. 88 Chunhui Road, Chancheng District",
    "zipCode": "528000",
    "city": "Foshan City",
    "stateOrRegion": "Guangdong Province",
    "countryCode": "CN",
    "latitude": null,
    "longitude": null,
    "webSite": null,
    "vatNumber": null,
    "mid": "CNFOSBRI88CHA",
    "avatarColor": "7486FF",
    "contacts": [
      {
        "firstName": "Alex",
        "lastName": "Kim",
        "email": "alex.kim@example.com",
        "phone": "+86 000 0000 0000",
        "role": "Production Manager",
        "faxNumber": null,
        "properties": [
          "primaryContact"
        ],
        "countryCode": "CN"
      }
    ]
  }
]'

const res = await fetch("https://service.my.delogue.com/api/sub-suppliers", {
  method: "POST",
  headers: {
    "Accept": "application/json",
    "X-Auth-Token": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
  },
  body: JSON.stringify([
  {
    "name": "Foshan Brightweave Textiles Co., Ltd",
    "customId": "10004",
    "relationType": "styleSupplier",
    "address": "Unit 12, Building 3, No. 88 Chunhui Road, Chancheng District",
    "zipCode": "528000",
    "city": "Foshan City",
    "stateOrRegion": "Guangdong Province",
    "countryCode": "CN",
    "latitude": null,
    "longitude": null,
    "webSite": null,
    "vatNumber": null,
    "mid": "CNFOSBRI88CHA",
    "avatarColor": "7486FF",
    "contacts": [
      {
        "firstName": "Alex",
        "lastName": "Kim",
        "email": "alex.kim@example.com",
        "phone": "+86 000 0000 0000",
        "role": "Production Manager",
        "faxNumber": null,
        "properties": [
          "primaryContact"
        ],
        "countryCode": "CN"
      }
    ]
  }
]),
});
const { data } = await res.json();

{
  "status": "success",
  "code": "sub_suppliers_created",
  "data": [
    {
      "id": "6AE876DD-547D-4202-B004-AC8617E3744A",
      "organizationId": 18931,
      "name": "Foshan Brightweave Textiles Co., Ltd",
      "customId": "10004",
      "relationType": "styleSupplier",
      "relationTypeName": "Style Supplier",
      "address": "Unit 12, Building 3, No. 88 Chunhui Road, Chancheng District",
      "zipCode": "528000",
      "city": "Foshan City",
      "stateOrRegion": "Guangdong Province",
      "countryCode": "CN",
      "countryName": "China",
      "latitude": null,
      "longitude": null,
      "webSite": null,
      "vatNumber": null,
      "mid": "CNFOSBRI88CHA",
      "avatarColor": "7486FF",
      "processingTypes": null,
      "facilityCount": 0,
      "state": "active",
      "createdAt": "2026-06-29T06:52:20.767Z",
      "contacts": [
        {
          "id": 101,
          "firstName": "Alex",
          "lastName": "Kim",
          "email": "alex.kim@example.com",
          "phone": "+86 000 0000 0000",
          "role": "Production Manager",
          "faxNumber": null,
          "properties": [
            "primaryContact"
          ],
          "countryCode": "CN"
        }
      ]
    }
  ]
}

The response wraps the created sub-suppliers in the standard envelope. Hold onto each id (UUID): you use it for single-record reads, updates, and deletes.

Field reference

The fields that matter most when creating or updating a sub-supplier:

Field	What it means at Delogue
`address`	Street address of the sub-supplier.
`avatarColor`	Hex colour code for the avatar, e.g. 7486FF.
`city`	City.
`contacts`	Initial list of contact persons to create with the sub-supplier.
`countryCode`	ISO 3166-1 alpha-2 country code. Required.
`customId`	Customer-defined identifier for the sub-supplier.
`latitude`	Geographic latitude in decimal degrees.
`longitude`	Geographic longitude in decimal degrees.
`mid`	Manufacturer Identification (MID) number.
`name`	Display name of the sub-supplier company. Required.
`relationType`	Commercial relationship type: distributor, itemSupplier, sourcingAgency, or styleSupplier.
`stateOrRegion`	State, province, or region.
`vatNumber`	VAT registration number.
`webSite`	Website URL.
`zipCode`	Postal or ZIP code.

Roles & permissions

Sub-supplier endpoints check the suppliers permission: read level to list and read, write level to update, and admin level to create and delete.

Supplier accounts need, by default, the SupplierAdmin or SupplierUser role.
Designer (brand) accounts need the Supplier Chain module and, by default, one of the CompanyAdmin, ComplianceAdmin, ComplianceUser, or SupplierManager roles.

The org-scoped endpoints (GET /api/organizations/{organizationId}/sub-suppliers and POST /api/organizations/{organizationId}/sub-suppliers) also require that you belong to that supplier organisation (supplier user) or have an active connection to it (designer user).

When things go wrong

Errors use the standard envelope (status: "error", a code, and error.details[]). See Errors & responses for the full list of codes and how to resolve them. Common cases:

404: the sub-supplier UUID does not exist. DELETE /api/sub-suppliers/{id} also returns 404 for a sub-supplier that belongs to a different organisation.
403: the sub-supplier belongs to a different organisation (on reads and updates), your account does not have an active connection with the supplier org, or it lacks the suppliers permission.
400: a required field (name, countryCode) is missing, or an enum value (relationType, state) is invalid.

What to call next

Facilities

Colours

Manage the brand’s reusable colour library that styles and items reference.

Seasons

Create the seasons that styles are filed under: the top-level collection structure.

Supplier connections

Count a brand’s supplier connections and list its open connection requests.

Style contacts

Look up the supplier and contact people assigned to a style.

API Reference

Full parameter and response schemas for all sub-supplier endpoints.

Getting Started

Concepts

Guides

The workflow

Walkthrough

Field reference

Roles & permissions

When things go wrong

What to call next

Facilities

Colours

Seasons

Supplier connections

Style contacts

API Reference

​The workflow

​Walkthrough

​Field reference

​Roles & permissions

​When things go wrong

​What to call next

Facilities

Colours

Seasons

Supplier connections

Style contacts

API Reference

The workflow

Walkthrough

Field reference

Roles & permissions

When things go wrong

What to call next