Get All Node Children

Get a node's children

GET/pcm/hierarchies/{hierarchyID}/nodes/{nodeID}/children

Use it in a workflow

Add a step and choose the Elastic Path connector.
Pick the Get All Node Children action (under PIM).
Fill in the fields below, then reference the result from later steps as {{getAllNodeChildren.response.data}}.

Request

Path parameters

hierarchyIDstringrequired

A unique identifier for the hierarchy.

nodeIDstringrequired

A unique identifier for the node.

Query parameters

filterstring

Many Commerce API endpoints support filtering. The general syntax is described [**here**](/guides/Getting-Started/filtering).

page[offset]integer (int64)

The number of records to offset the results by.

page[limit]integer (int64)

The number of records per page. The maximum limit is 100.

Response

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

dataarray<object>

An array of nodes.

idstringrequired

The unique identifier of a node.

typestringrequired

This represents the type of resource object being returned. Always `node`.

One ofnode

attributesobjectrequired7 fields

relationshipsobjectrequired3 fields

Relationships allow you to move between requests. Includes links to the child nodes and products associated with a hierarchy or node.

metaobjectrequired8 fields

metaobject

resultsobject1 fields

Contains the results for the entire collection.

linksobject

Links allow you to navigate between pages of results. :::caution Planned pagination changes — on or after 1 September 2026 The pagination behaviour of PIM list endpoints (for example, `GET /pcm/products` and `GET /pcm/hierarchies`) currently differs from the rest of the Elastic Path Commerce Cloud platform. We plan to align PIM pagination with the platform standard on or after **1 September 2026**. Please review the details below and check that your integration code will handle the new behaviour correctly. ::: #### Current behaviour The current pagination link behaviour in PIM has the following known issues: - The `current` link is **not returned**. - The `first` and `last` links are **not always returned**. - The `prev` link is omitted on both the first **and** second pages. It should only be omitted on the first page. - The `next` link is omitted on both the last **and** second-to-last pages. It should only be omitted on the last page. #### Planned behaviour (on or after 1 September 2026) On or after 1 September 2026, PIM list endpoints will adopt the following pagination link behaviour, aligning with the rest of the platform: - `current` — always present, pointing to the current page. - `first` — always present. - `last` — present on all pages **except the final page**. Omitting `last` on the final page is intentional, to avoid triggering infinite‑loop bugs in integration code that uses the presence of `last` to detect whether more pages remain. - `next` — present on all pages except the last page. - `prev` — present on all pages except the first page.

currentstring

A link to the current page of results. **Note:** this link is not currently returned by PIM endpoints. It will be introduced on or after 1 September 2026.

firststring

A link to the first page of results. Currently this may not always be present. After the planned changes it will always be present.

laststring

A link to the last page of results. Currently this may not always be present. After the planned changes it will be present on all pages except the final page (where it is intentionally omitted).

nextstring

A link to the next page of results. Should be absent on the last page. Currently this is incorrectly absent on the second-to-last page as well; this will be fixed on or after 1 September 2026.

prevstring

A link to the previous page of results. Should be absent on the first page. Currently this is incorrectly absent on the second page as well; this will be fixed on or after 1 September 2026.

json

{
  "data": [
    {
      "id": "string",
      "type": "node",
      "attributes": {
        "name": "string",
        "description": "string",
        "slug": "string",
        "curated_products": [
          "string"
        ],
        "admin_attributes": {
          "cost_of_goods": "42.0",
          "charge_type": "credit card"
        },
        "shopper_attributes": {
          "cost_of_goods": "42.0",
          "charge_type": "credit card"
        },
        "locales": {}
      },
      "relationships": {
        "children": {
          "data": [
            null
          ],
          "links": {
            "related": "string"
          }
        },
        "parent": {
          "data": {
            "type": "node",
            "id": "string"
          }
        },
        "products": {
          "data": [
            null
          ],
          "links": {
            "related": "string"
          }
        }
      },
      "meta": {
        "sort_order": 0,
        "created_at": "2020-09-22T09:00:00.000Z",
        "updated_at": "2020-09-22T09:00:00.000Z",
        "parent_name": "string",
        "owner": "store",
        "has_children": false,
        "hierarchy_id": "string",
        "breadcrumbs": [
          {
            "id": "string",
            "name": "string",
            "slug": "string",
            "locales": {}
          }
        ]
      }
    }
  ],
  "meta": {
    "results": {
      "total": 30
    }
  },
  "links": {
    "current": "/pcm/hierarchies?page[offset]=10&page[limit]=10",
    "first": "/pcm/hierarchies?page[offset]=0&page[limit]=10",
    "last": "/pcm/hierarchies?page[offset]=20&page[limit]=10",
    "next": "/pcm/hierarchies?page[offset]=10&page[limit]=10",
    "prev": "/pcm/hierarchies?page[offset]=8&page[limit]=10"
  }
}

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

Was this page helpful?