Get By Context Component Product I Ds

Get a Bundle's Component Products

GET/catalog/products/{product_id}/relationships/component_products

Use it in a workflow

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

Request

Path parameters

product_idstringrequired

The product ID.

Query parameters

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-Channelstring

The list of channels in which this catalog can be displayed. A channel is the shopping experience, such as a mobile app or web storefront. If empty, the catalog rule matches all channels. The channel will eventually be included in the bearer token that is used for authorization, but currently, you must set the `EP-Channel` header in your requests.

EP-Context-Tagstring

Tags are used to refine the eligibility criteria for a rule. Requests populate the catalog rule tag using the `EP-Context-Tag` header.

Response

Returns 200 with an object. Read it in later steps with {{getByContextComponentProductIDs.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?