Get Component Product I Ds

Get a Bundle's Component Products

GET/catalogs/{catalog_id}/releases/{release_id}/products/{product_id}/relationships/component_products

Use it in a workflow

Add a step and choose the Elastic Path connector.
Pick the Get Component Product I Ds action (under Catalog).
Fill in the fields below, then reference the result from later steps as {{getComponentProductIDs.response.data}}.

Request

Path parameters

catalog_idstringrequired

The catalog ID.

release_idstringrequired

The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.

product_idstringrequired

The product ID.

Query parameters

includearray<string>

Using the include parameter, you can retrieve top-level resources. - Files or main image. For example, `include=files,main_image`. - Component product data. For example, `include=component_products`. - Key attribute data, such as SKU or slug.

page[limit]integer (int64)

The maximum number of records per page for this response. You can set this value up to 100. If no page size is set, the [page length](/docs/api/settings/settings-introduction#page-length) store setting is used.

page[offset]integer (int64)

The current offset by number of records, not pages. Offset is zero-based. The maximum records you can offset is 10,000. You would normally increment the page offset by multiples of the page limit to paginate through the results.

Headers

EP-Pricebook-IDs-For-Price-Segmentation-Previewarray<string>

Supply a comma delimited list of pricebook ids to be used to lookup product prices from when the catalog supports price segmentation. The first pricebook will be highest priority (if more than one is supplied) and the rest in descending priority order. Used only for admin endpoints that dont support shopper context lookup.

EP-Pricebook-IDs-Of-Available-Prices-To-Showarray<string>

Supply a comma delimited list of pricebook ids to be listed in meta sections available prices . 'all' is a permitted value and will ensure all available prices for a product are shown. 'all' is not recommended if there are lots(10+) of available prices due the large response size.

Response

Returns 200 with an object. Read it in later steps with {{getComponentProductIDs.response.data.<field>}}.

metaobject

Contains the results for the entire collection.

resultsobject1 fields

Total number of results for the entire collection.

pageobject4 fields

dataarray<object>

A list of product identifiers.

idstring (uuid)

A unique identifier for a product.

typestring

This represents the type of object being returned. Always `product`.

One ofproduct

linksobject

Links allow you to move between requests.

selfstring (uri)

Single entities use a `self` parameter with a link the specific resource.

firststring (uri)

Always the first page.

laststring (uri)

This is `null` if there is only one page.

prevstring (uri)

This is `null` if there is only one page.

nextstring (uri)

This is `null` if there is only one page.

json

{
  "meta": {
    "results": {
      "total": 0
    },
    "page": {
      "limit": 0,
      "offset": 0,
      "current": 0,
      "total": 0
    }
  },
  "data": [
    {
      "id": "00000000-0000-0000-0000-000000000000",
      "type": "product"
    }
  ],
  "links": {
    "self": "string",
    "first": "string",
    "last": "string",
    "prev": "string",
    "next": "string"
  }
}

Need more? See the Elastic Path guide for connection setup and behaviour shared by every action.

Was this page helpful?