Skip to content

Fetch Brands

Brands represent the manufacturers or labels associated with products in your catalog. Each brand has a unique identifier and name, enabling customers to discover, filter, and differentiate products based on their preferred manufacturers or labels. In Fynd Commerce, brands serve as a critical catalog attribute that influences product organization, search, and customer purchasing decisions.

The Fetch Brands endpoint retrieves all brands configured for your company, with optional filtering capabilities. Use this API access brand metadata (including IDs, names, and slugs) which is essential when creating products, building brand-based navigation, or syncing catalog data between systems. The endpoint supports flexible querying by brand name and pagination for handling extensive brand catalogs.

Request Type: GET
Scheme: HTTPS
Endpoint: https://{{host}}/v3/catalog/company-brand

Try out Fynd Konnect's Fetch Brands Endpoint


Common Request Headers

HeaderMandatoryDescription
x-access-tokenYesAccess token used for authenticating API requests to Fynd Konnect
Content-TypeYesapplication/json
Use Cases
  • Retrieve the complete list of brands to populate product creation forms
  • Search for specific brands by name to validate brand assignments
  • Build brand-based navigation menus or filters for customer-facing storefronts
  • Sync brand data between your ERP/WMS and Fynd Commerce
  • Verify brand existence before creating or updating products

Query Parameters

brand_namestring

Search brands by name (partial match supported for fuzzy searching)

page_numberinteger>= 1

Page number for pagination (default: 1)

page_sizeinteger[ 1 .. 200 ]

Number of items to retrieve per page (1–200, default: 10)

Filtering Tips
  • Use brand_name for fuzzy searching to find brands with partial name matches
  • Leave brand_name empty to retrieve all brands in your catalog
  • Implement pagination for catalogs with large numbers of brands (e.g., multi-brand retailers)
  • Cache brand data to minimize API calls, as brands rarely change

Success Response

itemsArray of objects

List of brands matching the query filters

page_numberinteger

Current page number in the paginated response

page_sizeinteger

Number of items returned in this page

totalinteger

Total number of brands available matching the query

API Call Example

curl -i -X GET \
  'https://fyndkonnect.konnect.uat.fyndx1.de/v3/catalog/company-brand?brand_name=string&page_number=1&page_size=1' \
  -H 'x-access-token: YOUR_API_KEY_HERE'

Example Response

{
  "items": [
    {
      "id": "12345",
      "name": "Generic",
      "slug": "generic"
    }
  ],
  "page_number": 1,
  "page_size": 10,
  "total": 1
}

Best Practices

  1. Cache brand data: Brands change infrequently, so implement caching to reduce API calls and improve performance
  2. Store brand IDs and slugs: Save both brand IDs (UIDs) and slugs in your system for flexible product creation
  3. Validate brand existence: Always verify the brand exists before creating products to avoid validation errors
  4. Use brand slugs in product creation: Brand slugs are required when creating products via the Create Product endpoint
  5. Handle pagination: For multi-brand retailers with hundreds of brands, implement proper pagination logic
  6. Implement search functionality: Use the brand_name parameter to build brand search features in your system
Next Steps
© 2026 Shopsense Retail Technologies | MadeInIndia