Skip to content
Last updated

Konnect's Catalog API Suite

The Fynd Konnect Catalog API is a unified suite of REST APIs, built on the Konnect extension, that enables brands and third-party aggregator systems to seamlessly manage product catalogs on the Fynd Core Platform. It serves as a bridge between external systems (ERP, POS, WMS, etc.) and Fynd, helping partners maintain a consistent, structured catalog without repetitive manual entry.

Through this integration, partners can create, update, and delete products in Fynd while also retrieving essential data, including core catalog entities (products, brands, categories, departments) and reference metadata (templates, attributes, HS codes, and tax rules). By polling this data from Fynd before making catalog changes, external systems ensure compliance with Fynd’s standards - resulting in faster onboarding, fewer errors, and greater scalability.

Additionally, partners can debug and track product creation or update issues using the Check Product Status API, which provides detailed feedback on whether a product was successfully processed or failed due to validation errors.

Third parties can create products only by referencing entities that already exist in Fynd - departments, categories, templates, attributes, brands, tax rules, and HS codes. The said parties cannot add departments, categories, templates, or attributes (admin-managed); they can only create brands, HS codes, and tax rule IDs via Fynd Commerce.

Need a new admin-managed entity?

Raise a request to Fynd; once it is added, you can fetch it via the APIs and use it

Key Highlights & Benefits

Metadata-Driven Creation

Poll Fynd catalog metadata first; then create, update, or delete products with confidence

Template-Driven Standards

Enforce Fynd’s catalog structure for data completeness and compliance

Bulk Operations

Process multiple products of the same template in a single request for faster uploads

Near Real-Time Updates

Reflect changes to price, attributes, and descriptions quickly on the Fynd Platform

Data Accuracy & Consistency

Validate against Fynd rules to prevent mismatches across systems

Easy Debugging

Use Check Product Status for transparent validation errors and status tracking

Scalable

Handle high SKU volumes with batch APIs and robust performance

Faster Go-Live

Reduce manual catalog entry so products reach channels quicker

Core Features

  • Product Creation – Add new products using the Create Product API, leveraging predefined templates to ensure compliance with Fynd’s catalog structure.

  • Product Updates – Modify existing product details (e.g., name, price, description, traders, product attributes, global attributes) via the Update Product API, while respecting immutable fields (e.g., slug, brand, item_code).

  • Product Deletion – Remove entire products or specific variants (sizes) using the Delete Product API.

  • Metadata Retrieval APIs – Fetch reference data before creating or updating products:

    • Get Departments – Retrieve available departments.
    • Get Categories – Retrieve category hierarchies (L1 → L2 → L3).
    • Get Brands – List available brands.
    • Get Templates – Obtain product templates for structured creation.
    • Get Attributes, HS Codes & Tax Rules – Fetch validation data for product compliance.
    • Product Retrieval – Use Get Products to fetch and verify product records created on the Fynd Platform.
  • Check Product Status – Track and debug product creation, update, or delete requests. Returns status (COMPLETED, PENDING, FAILED) and validation error details (if any).

Common Scenarios

  1. New Product Creation: When a brand launches a new SKU in its ERP system, the integration fetches metadata (department, category, brand, template, attributes, HS code, tax rule ID) from Fynd, validates the product details, and uses the Create Product API to onboard the product to the Fynd platform.

  2. Price Updates: When the ERP or POS system updates a product’s price (e.g., applying a discount or changing the MRP), the integration calls the Update Product API to sync pricing details with Fynd, ensuring customers always see accurate prices.

  3. Discontinuing Products or Variants: If a product or a specific variant (e.g., size “UK 9”) is discontinued, the integration uses the Delete Product API to remove it from Fynd, preventing it from being displayed or sold.

  4. Category, Brand & Template Mapping: Before creating products, the integration fetches catalog metadata using Get Departments, Get Categories, Get Brands, and Get Templates APIs. This ensures proper mapping and prevents rejections during product creation.

  5. Bulk Product Uploads: When onboarding large collections (e.g., 500 new SKUs under the same template), the aggregator groups them into a single payload and submits via the Create Product API, reducing manual effort and time.

  6. Debugging Product Creation Failures: If product creation fails due to validation errors (e.g., missing primary_material, invalid HS code, category name, or template slug), the aggregator uses Check Product Status to identify errors and resubmit corrected data.

Important Notes & Constraints

  • Fetch before you send. Before sending values for brand, HS code, category, department, template, and product attribute, fetch them from Fynd using the relevant Read APIs to ensure they exist on the platform.
  • Immutable fields (cannot be updated once created): slug, brand, item_code.
  • Bulk operations: Multiple products of the same template can be created in a single request.
  • Stock quantity updates are not supported via Konnect Catalog APIs.
  • Status Tracking: Use Check Product Status to monitor asynchronous processing of create, update, or delete requests.
    • COMPLETED – The request was processed successfully.
    • PENDING – The request is still being processed.
    • FAILED – The request was rejected; response includes validation error details to aid troubleshooting.