UiPath Documentation
industry-department-solutions
latest
false
  • Overview
    • Introduction
    • Getting Started
    • API Guide
    • Customizations
    • Data Onboarding Checklist
  • API Resources
UiPath logo, featuring letters U and I in white

Supply Chain & Retail Solutions API guide

Last updated Apr 16, 2026

Products Parent Child Mapping

Overview

The Products Parent Child Mapping resource defines hierarchical relationships between products, such as a parent SKU and its variants (e.g. colour or size variants of a base product). Each record links a child product to its parent product, providing a label to describe the relationship type and a rank to control the ordering of child products within the hierarchy.

Resource Endpoint

/api/v2/ingest/object/INV_PRODUCTS_PARENT_CHILD_MAPPING_OOTB
/api/v2/ingest/object/INV_PRODUCTS_PARENT_CHILD_MAPPING_OOTB

Supported Methods

MethodReturn TypeDescription
POSTResponseIngest (create/update) Products Parent Child Mapping records via UPSERT operation

Request Headers

HeaderRequiredDescription
AuthorizationYesYour Personal Access Token (PAT) from platform.peak.ai
Content-TypeYesMust be application/json

Properties

Primary Keys

  • child_id (string) - Unique identifier for the child product. Part of the composite primary key.
  • updated_at (timestamp) - Timestamp of the most recent update to the record. Part of the composite primary key.

Attributes

AttributeData TypeRequiredDescription
parent_idstringYesUnique identifier of the parent product in the hierarchy
child_idstringYesUnique identifier of the child product in the hierarchy
child_labelstringYesA label describing the nature of the child relationship (e.g. "variant", "component")
child_rankintegerYesNumeric rank controlling the display or processing order of child products under the same parent
updated_attimestampYesTimestamp of the most recent update to this record

Relationships

Outbound References

The products_parent_child_mapping resource does not reference any downstream resources as foreign keys.

Inbound References

Both parent_id and child_id reference the products resource:

  • products (parent) — parent_idproducts.product_id
  • products (child) — child_idproducts.product_id

JSON Representation

{
  "solutionName": "INV_OOTB",
  "data": [
    {
      "parent_id": "PROD-001",
      "child_id": "PROD-001-RED",
      "child_label": "variant",
      "child_rank": 1,
      "updated_at": "2025-01-15 08:00:00"
    }
  ],
  "operationType": "UPSERT"
}
{
  "solutionName": "INV_OOTB",
  "data": [
    {
      "parent_id": "PROD-001",
      "child_id": "PROD-001-RED",
      "child_label": "variant",
      "child_rank": 1,
      "updated_at": "2025-01-15 08:00:00"
    }
  ],
  "operationType": "UPSERT"
}

Example Request

curl -X POST \
  'https://service.peak.ai/ingestion-api/api/v2/ingest/object/INV_PRODUCTS_PARENT_CHILD_MAPPING_OOTB' \
  -H 'Authorization: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "solutionName": "INV_OOTB",
    "data": [
      {
        "parent_id": "PROD-001",
        "child_id": "PROD-001-RED",
        "child_label": "variant",
        "child_rank": 1,
        "updated_at": "2025-01-15 08:00:00"
      }
    ],
    "operationType": "UPSERT"
  }'
curl -X POST \
  'https://service.peak.ai/ingestion-api/api/v2/ingest/object/INV_PRODUCTS_PARENT_CHILD_MAPPING_OOTB' \
  -H 'Authorization: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "solutionName": "INV_OOTB",
    "data": [
      {
        "parent_id": "PROD-001",
        "child_id": "PROD-001-RED",
        "child_label": "variant",
        "child_rank": 1,
        "updated_at": "2025-01-15 08:00:00"
      }
    ],
    "operationType": "UPSERT"
  }'

Important Notes

  • child_id and updated_at together form the composite primary key. Both fields must be provided on every record.
  • Each child_id can only have one parent_id; a child product maps to exactly one parent in the hierarchy.
  • parent_id and child_id must both correspond to existing records in the Products resource. Ensure parent products are ingested before their child mappings.
  • child_label is required and should consistently describe the relationship type across your dataset (e.g. always "variant" for size/colour variants).
  • child_rank is required and must be a positive integer. Lower values typically indicate higher priority or display order.
  • Timestamps must be provided in YYYY-MM-DD HH:MM:SS format.
  • Records are ingested via UPSERT: an existing record with matching primary keys will be updated; otherwise a new record is inserted.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated