Every API here is available over the APIs.io API and to AI agents over MCP.
openapi: 3.2.0
info:
title: Catalogs Introduction Administrator Latest Releases Catalog API
description: 'Use the catalog-view Service API to create your catalogs.
You also have the flexibility to create catalogs for different scenarios by combining hierarchies of products with a price book. Scenarios might include:
- Multiple geographical regions. Display different catalogs in different regions with suitable pricing or combine product hierarchies from two different regions to display in a third region.
- Multiple channels. Display different catalogs based on how a shopper accesses your store, such as through a mobile app or a web storefront.
- Direct to business versus direct to customers. Offer different products and prices for business customers versus retail customers.
- Preferred customers. Offer special pricing to preferred customers while displaying a standard price catalog to all other shoppers.
- Reward programs. Enable reward programs where catalog prices drop after a certain spending level is reached.
- Product sales. Offer sale items for a limited time.
Scenarios are created by defining the context within which a catalog is displays. Contexts can be a customer ID, a channel, or any other user-defined tag that can be passed to the APIs from the front-end shopper experiences.
'
version: 26.0508.7574130
x-version-timestamp: 2026-05-08 11:06:53+00:00
servers:
- url: https://euwest.api.elasticpath.com
description: EU West Production Server
- url: https://useast.api.elasticpath.com
description: US East Production Server
security:
- bearerAuth: []
tags:
- name: Administrator Latest Releases Catalog API
description: 'Use the Administrator Latest Releases Catalog View API to retrieve product, hierarchy and node information.
:::danger
The Administrator Latest Releases Catalog View API is for Administrator use only. Do not use these endpoints on your customer-facing frontends.
:::
Publishing a catalog creates a release of that catalog that you can use in an organization or in a specific store or other shopper experience. You can retrieve the hierarchies, nodes, and the `live` products associated with a catalog release. You can see which parent nodes a product is associated with. This is useful if want to improve how your shoppers search your store, for example.
Currently, published catalogs are limited to the current release and two releases prior to the current release.
'
paths:
/catalogs/{catalog_id}/releases/{release_id}/hierarchies:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get all Hierarchies
description: "Returns the hierarchies from a published catalog.\n\n:::note\n\nCurrently, published catalogs are limited to the current release and two releases prior to the current release.\n\n:::\n\n### Filtering\n\nThis endpoint supports filtering. For general syntax, see [Filtering](/guides/Getting-Started/filtering).\n\n| Operator | Description | Supported Attributes | Example |\n|:--- |:--- |:--- |:--- |\n| `Eq` | Checks if the values of two operands are equal. If they are, the condition is true. | `name`, `slug`| `filter=eq(name,some-name)` |\n| `In` | Checks if the values are included in the specified string. If they are, the condition is true. | `id` | `filter=in(id,some-id)` | \n\n### Building breadcrumbs in a storefront\n\nIn a catalog, you can use the nodes directly attached to a product to build breadcrumbs in your storefront. This eliminates the need for additional queries to fetch hierarchy or parent node details. Each node contains all the necessary information in `breadcrumbs` metadata, such as its own details and the details of its parent hierarchy/node(s), to construct the complete breadcrumb path without requiring additional queries.\n\nAn example is shown below:\n\n`filter=in(id,c83bfe55-0d87-4302-a86d-ab19e7e323f1,6003d7ef-84f3-49bb-a8bd-4cbfa203dcbb)`\n\n- Specify the node IDs directly attached to the product in the filter expression.\n- You can include as many node IDs as required.\n- It does not matter what order you specify the node IDs. The nodes are returned in the order they were last updated.\n"
operationId: getAllHierarchies
parameters:
- $ref: '#/components/parameters/accept-language'
- description: The catalog ID.
name: catalog_id
in: path
required: true
schema:
type: string
- description: The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.
name: release_id
in: path
required: true
schema:
type: string
- $ref: '#/components/parameters/filter-hierarchy'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/offset'
responses:
'200':
description: The hierarchies of a catalog.
content:
application/json:
schema:
$ref: '#/components/schemas/hierarchy-list-data'
default:
description: An unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/catalogs/{catalog_id}/releases/{release_id}/hierarchies/{hierarchy_id}:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get a Hierarchy
description: 'Returns the specified hierarchy from a published catalog.
:::note
Currently, published catalogs are limited to the current release and two releases prior to the current release.
:::
'
operationId: getHierarchy
parameters:
- $ref: '#/components/parameters/accept-language'
- description: The catalog ID.
name: catalog_id
in: path
required: true
schema:
type: string
- description: The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.
name: release_id
in: path
required: true
schema:
type: string
- description: The catalog hierarchy ID.
name: hierarchy_id
in: path
required: true
schema:
type: string
responses:
'200':
description: The catalog hierarchy.
content:
application/json:
schema:
$ref: '#/components/schemas/hierarchy-data'
default:
description: The unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/catalogs/{catalog_id}/releases/{release_id}/hierarchies/{hierarchy_id}/nodes:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get a Hierarchy's Nodes
description: "Returns all nodes for the specified hierarchy from a published catalog.\n\n:::note\n\nCurrently, published catalogs are limited to the current release and two releases prior to the current release.\n\n:::\n\nIn the `breadcrumbs` metadata, you can identify the parent nodes that a node is associated with. This is useful if you want to improve how your shoppers search your store, for example. See [Product and Node Associations in Breadcrumb Metadata](/guides/How-To/Catalogs/breadcrumbs).\n\n### Filtering\n\nThis endpoint supports filtering. For general syntax, see [Filtering](/guides/Getting-Started/filtering).\n\n| Operator | Description | Supported Attributes | Example |\n|:--- |:--- |:--- |:--- |\n| `Eq` | Checks if the values of two operands are equal. If they are, the condition is true. | `name`, `slug`| `filter=eq(name,some-name)` |\n| `In` | Checks if the values are included in the specified string. If they are, the condition is true. | `id` | `filter=in(id,some-id)` | \n\n### Building breadcrumbs in a storefront\n\nIn a catalog, you can use the nodes directly attached to a product to build breadcrumbs in your storefront. This eliminates the need for additional queries to fetch hierarchy or parent node details. Each node contains all the necessary information in `breadcrumbs` metadata, such as its own details and the details of its parent hierarchy/node(s), to construct the complete breadcrumb path without requiring additional queries.\n\nAn example is shown below:\n\n`filter=in(id,c83bfe55-0d87-4302-a86d-ab19e7e323f1,6003d7ef-84f3-49bb-a8bd-4cbfa203dcbb)`\n\n- Specify the node IDs directly attached to the product in the filter expression.\n- You can include as many node IDs as required.\n- It does not matter what order you specify the node IDs. The nodes are returned in the order they were last updated.\n"
operationId: getHierarchyNodes
parameters:
- description: The catalog ID.
name: catalog_id
in: path
required: true
schema:
type: string
- description: The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.
name: release_id
in: path
required: true
schema:
type: string
- description: The catalog hierarchy ID.
name: hierarchy_id
in: path
required: true
schema:
type: string
- $ref: '#/components/parameters/accept-language'
- $ref: '#/components/parameters/filter-node'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/offset'
responses:
'200':
description: The child nodes of a catalog hierarchy.
content:
application/json:
schema:
$ref: '#/components/schemas/node-list-data'
default:
description: The unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/catalogs/{catalog_id}/releases/{release_id}/hierarchies/{hierarchy_id}/children:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get a Hierarchy's Children
description: "Returns the parent nodes for the specified hierarchy from a published catalog.\n\n\n\n:::note\n\nCurrently, published catalogs are limited to the current release and two releases prior to the current release.\n\n:::\n\nIn the `breadcrumbs` metadata, you can identify the parent nodes that a node is associated with. This is useful if you want to improve how your shoppers search your store, for example. See [Product and Node Associations in Breadcrumb Metadata](/guides/How-To/Catalogs/breadcrumbs).\n\n### Filtering\n\nThis endpoint supports filtering. For general syntax, see [Filtering](/guides/Getting-Started/filtering).\n\n| Operator | Description | Supported Attributes | Example |\n|:--- |:--- |:--- |:--- |\n| `Eq` | Checks if the values of two operands are equal. If they are, the condition is true. | `name`, `slug`| `filter=eq(name,some-name)` |\n| `In` | Checks if the values are included in the specified string. If they are, the condition is true. | `id` | `filter=in(id,some-id)` | \n\n### Building breadcrumbs in a storefront\n\nIn a catalog, you can use the nodes directly attached to a product to build breadcrumbs in your storefront. This eliminates the need for additional queries to fetch hierarchy or parent node details. Each node contains all the necessary information in `breadcrumbs` metadata, such as its own details and the details of its parent hierarchy/node(s), to construct the complete breadcrumb path without requiring additional queries.\n\nAn example is shown below:\n\n`filter=in(id,c83bfe55-0d87-4302-a86d-ab19e7e323f1,6003d7ef-84f3-49bb-a8bd-4cbfa203dcbb)`\n\n- Specify the node IDs directly attached to the product in the filter expression.\n- You can include as many node IDs as required.\n- It does not matter what order you specify the node IDs. The nodes are returned in the order they were last updated.\n"
operationId: getHierarchyChildNodes
parameters:
- description: The catalog ID.
name: catalog_id
in: path
required: true
schema:
type: string
- description: The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.
name: release_id
in: path
required: true
schema:
type: string
- description: The catalog hierarchy ID.
name: hierarchy_id
in: path
required: true
schema:
type: string
- $ref: '#/components/parameters/accept-language'
- $ref: '#/components/parameters/filter-node'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/offset'
responses:
'200':
description: The child nodes of a catalog hierarchy.
content:
application/json:
schema:
$ref: '#/components/schemas/node-list-data'
default:
description: The unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/catalogs/{catalog_id}/releases/{release_id}/nodes:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get all Nodes
description: 'Returns the child nodes from a published catalog.
:::note
Currently, published catalogs are limited to the current release and two releases prior to the current release.
:::
You can see the parent nodes a node is associated with in the `breadcrumbs` metadata for each node. This is useful if you want to improve how your shoppers search your store, for example. See [Product and Node Associations in Breadcrumb Metadata](/guides/How-To/Catalogs/breadcrumbs).
In a catalog, you can use a filter to return a list of nodes in a hierarchy structure that a product belongs to. You can use this to build breadcrumbs in your storefront. See [Building breadcrumbs in a storefront](#building-breadcrumbs-in-a-storefront).
The response lists the products associated with the nodes. If products are [curated](/guides/How-To/Products/curating-products), they are displayed in `curated_products`. Product curation allows you to promote specific products within each of your hierarchies, enabling you to create unique product collections in your storefront.
- If you don''t provide any `curated_products`, products are listed by their `updated_at` time in descending order, with the most recently updated product first.
- If you configure `curated_products` for only a few products, the curated products are displayed first and the other products are displayed in the order of `updated_at` time.
- You can only curate 20 products or less. You cannot have more than 20 curated products.
- If a curated product is removed from a node, the product is also removed from the `curated_products` list.
- A product that is curated has the `"curated_product": true` attribute displayed.
### Filtering
This endpoint supports filtering. For general syntax, see [Filtering](/guides/Getting-Started/filtering). The following operators and attributes are available.
| Operator | Description | Attributes | Example |
| --- | --- | --- | --- |
| `Eq` | Checks if the values of two operands are equal. If they are, the condition is true. | `name`, `slug` | `filter=eq(name,some-name)` |
| `in` | Checks if the values are included in the specified string. If they are, the condition is true.
| `Id` | `filter=in(id,9214719b-17fe-4ea7-896c-d61e60fc0d05,e104d541-2c52-47fa-8a9a-c4382480d97c,65daaf68-ff2e-4632-8944-370de835967d)` |
### Building breadcrumbs in a storefront
In a catalog, you can use the nodes directly attached to a product to build breadcrumbs in your storefront. This eliminates the need for additional queries to fetch hierarchy or parent node details. Each node contains all the necessary information in `breadcrumbs` metadata, such as its own details and the details of its parent hierarchy/node(s), to construct the complete breadcrumb path without requiring additional queries.
An example is shown below:
`filter=in(id,c83bfe55-0d87-4302-a86d-ab19e7e323f1,6003d7ef-84f3-49bb-a8bd-4cbfa203dcbb)`
- Specify the node IDs directly attached to the product in the filter expression.
- You can include as many node IDs as required.
- It does not matter what order you specify the node IDs. The nodes are returned in the order they were last updated.
'
operationId: getAllNodes
parameters:
- description: The catalog ID.
name: catalog_id
in: path
required: true
schema:
type: string
- description: The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.
name: release_id
in: path
required: true
schema:
type: string
- $ref: '#/components/parameters/accept-language'
- $ref: '#/components/parameters/filter-node'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/offset'
responses:
'200':
description: The nodes of a catalog.
content:
application/json:
schema:
$ref: '#/components/schemas/node-list-data'
default:
description: An unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/catalogs/{catalog_id}/releases/{release_id}/nodes/{node_id}:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get a Node
description: 'Returns a node from a published catalog.
:::note
Currently, published catalogs are limited to the current release and two releases prior to the current release.
:::
You can see the parent nodes a node is associated with in the `breadcrumbs` metadata for each node. This is useful if you want to improve how your shoppers search your store, for example. See [Product and Node Associations in Breadcrumb Metadata](/guides/How-To/Catalogs/breadcrumbs).
The response lists the products associated with the nodes. If products are [curated](/guides/How-To/Products/curating-products), they are displayed in `curated_products`. Product curation allows you to promote specific products within each of your hierarchies, enabling you to create unique product collections in your storefront.
- If you don''t provide any `curated_products`, products are listed by their `updated_at` time in descending order, with the most recently updated product first.
- If you configure `curated_products` for only a few products, the curated products are displayed first and the other products are displayed in the order of `updated_at` time.
- You can only curate 20 products or less. You cannot have more than 20 curated products.
- If a curated product is removed from a node, the product is also removed from the `curated_products` list.
- A product that is curated has the `"curated_product": true` attribute displayed.
'
operationId: getNode
parameters:
- $ref: '#/components/parameters/accept-language'
- description: The catalog ID.
name: catalog_id
in: path
required: true
schema:
type: string
- description: The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.
name: release_id
in: path
required: true
schema:
type: string
- description: The catalog node ID.
name: node_id
in: path
required: true
schema:
type: string
responses:
'200':
description: The catalog node.
content:
application/json:
schema:
$ref: '#/components/schemas/node-data'
default:
description: The unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/catalogs/{catalog_id}/releases/{release_id}/nodes/{node_id}/relationships/children:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get a Node's Children
description: 'Returns the child nodes for a node from a published catalog.
:::note
Currently, published catalogs are limited to the current release and two releases prior to the current release.
:::
You can see the parent nodes a node is associated with in the `breadcrumbs` metadata for each node. This is useful if you want to improve how your shoppers search your store, for example. See [Product and Node Associations in Breadcrumb Metadata](/guides/How-To/Catalogs/breadcrumbs).
In a catalog, you can use a filter to return a list of nodes in a hierarchy structure that a product belongs to. You can use this to build breadcrumbs in your storefront. For more information, see [Building breadcrumbs in a storefront](#building-breadcrumbs-in-a-storefront).
The response lists the products associated with the nodes. If products are [curated](/guides/How-To/Products/curating-products), they are displayed in `curated_products`. Product curation allows you to promote specific products within each of your hierarchies, enabling you to create unique product collections in your storefront.
- If you don''t provide any `curated_products`, products are listed by their `updated_at` time in descending order, with the most recently updated product first.
- If you configure `curated_products` for only a few products, the curated products are displayed first and the other products are displayed in the order of `updated_at` time.
- You can only curate 20 products or less. You cannot have more than 20 curated products.
- If a curated product is removed from a node, the product is also removed from the `curated_products` list.
- A product that is curated has the `"curated_product": true` attribute displayed.
### Filtering
This endpoint supports filtering. For general syntax, see [Filtering](/guides/Getting-Started/filtering). The following operators and attributes are available.
| Operator | Description | Attributes | Example |
| --- | --- | --- | --- |
| `Eq` | Checks if the values of two operands are equal. If they are, the condition is true. | `name`, `slug` | `filter=eq(name,some-name)` |
| `in` | Checks if the values are included in the specified string. If they are, the condition is true.
| `Id` | `filter=in(id,9214719b-17fe-4ea7-896c-d61e60fc0d05,e104d541-2c52-47fa-8a9a-c4382480d97c,65daaf68-ff2e-4632-8944-370de835967d)` |
### Building breadcrumbs in a storefront
In a catalog, you can use the nodes directly attached to a product to build breadcrumbs in your storefront. This eliminates the need for additional queries to fetch hierarchy or parent node details. Each node contains all the necessary information in `breadcrumbs` metadata, such as its own details and the details of its parent hierarchy/node(s), to construct the complete breadcrumb path without requiring additional queries.
An example is shown below:
`filter=in(id,c83bfe55-0d87-4302-a86d-ab19e7e323f1,6003d7ef-84f3-49bb-a8bd-4cbfa203dcbb)`
- Specify the node IDs directly attached to the product in the filter expression.
- You can include as many node IDs as required.
- It does not matter what order you specify the node IDs. The nodes are returned in the order they were last updated.
'
operationId: getChildNodes
parameters:
- description: The catalog ID.
name: catalog_id
in: path
required: true
schema:
type: string
- description: The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.
name: release_id
in: path
required: true
schema:
type: string
- description: The catalog node ID.
name: node_id
in: path
required: true
schema:
type: string
- $ref: '#/components/parameters/accept-language'
- $ref: '#/components/parameters/filter-node'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/offset'
responses:
'200':
description: The child nodes of a catalog node.
content:
application/json:
schema:
$ref: '#/components/schemas/node-list-data'
default:
description: The unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/catalogs/{catalog_id}/releases/{release_id}/products:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get all Products
description: "Returns the products from a published catalog. Only the products in a `live` status are retrieved. Currently, published catalogs are limited to the current release and two releases prior to the current release.\n\nYou can see the parent nodes a product is associated with in the `bread_crumbs` and `bread_crumb_nodes` metadata for each product. This is useful if you want to improve how your shoppers search your store, for example. See [Product and Node Associations in Breadcrumb Metadata](/guides/How-To/Catalogs/breadcrumbs).\n\nThe `variations` object lists the variation IDs and variation option IDs and their corresponding product IDs that are generated when the variation and variation options are built with a product. The `variations` object can then be added to your catalogs. By default, variations and variation options are sorted randomly. You can use the `sort_order` attribute to sort the order of your variation and variation options in `variations`. Once a parent product is published in a catalog, the [Get a List of products in a catalog release](/docs/api/pxm/catalog/get-all-products) response displays the sorted variations and variation options. Variations and variation options are displayed in descending order according to their `sort_order` values.\n\n### Including Resources\n\nUsing the `include` parameter, you can retrieve top-level resources, such as, files or main image, bundle component products and product attributes, such as SKU or slug. \n\n| Parameter | Required | Description |\n| :---------------------|:---------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `component_products` | Optional | The component product data and key attribute data, such as SKU or slug, to return for component products in a product bundle. |\n| `main_image` | Optional | The main images associated with a product. |\n| `files` | Optional | Any files associated with a product. \n\nSee [**Including Resources**](/guides/Getting-Started/includes).\n\n### Filtering\n\nThis endpoint supports filtering. For general filtering syntax, see [Filtering](/guides/Getting-Started/filtering). The following operators and attributes are available when filtering on this endpoint.\n\n| Operator | Description | Supported Attributes | Example |\n|:---|:------------------------------------------------------------------------------------------------|:---------------------------------------------------------|:--- |\n| `Eq` | Checks if the values of two operands are equal. If they are, the condition is true. For `product_types`, you can only specify one product type. For example, `filter=eq(product_types,child)`. | `name`, `sku`, `slug`, `manufacturer_part_num`, `upc_ean`, `product_types`, `tags` | `filter=eq(name,some-name)` |\n| `In` | Checks if the values are included in the specified string. If they are, the condition is true. For `product_types`, you can specify more than one product type. For example, `filter=in(product_types,child,bundle)`. | `id`, `name`, `sku`, `slug`, `manufacturer_part_num`, `upc_ean`, `product_types`, `tags` | `filter=in(id,some-id)` |\n\n### Building breadcrumbs in a storefront\n\nIn a catalog, you can use the nodes directly attached to a product to build breadcrumbs in your storefront. This eliminates the need for additional queries to fetch hierarchy or parent node details. Each node contains all the necessary information in `breadcrumbs` metadata, such as its own details and the details of its parent hierarchy/node(s), to construct the complete breadcrumb path without requiring additional queries.\n\nAn example is shown below:\n\n`filter=in(id,c83bfe55-0d87-4302-a86d-ab19e7e323f1,6003d7ef-84f3-49bb-a8bd-4cbfa203dcbb)`\n\n- Specify the node IDs directly attached to the product in the filter expression.\n- You can include as many node IDs as required.\n- It does not matter what order you specify the node IDs. The nodes are returned in the order they were last updated.\n"
operationId: getAllProducts
parameters:
- $ref: '#/components/parameters/accept-language'
- $ref: '#/components/parameters/include'
- $ref: '#/components/parameters/filter-product'
- $ref: '#/components/parameters/pricebook-ids-for-price-segmentation-preview'
- $ref: '#/components/parameters/pricebook-ids-of-available-prices-to-show'
- description: The catalog ID.
name: catalog_id
in: path
required: true
schema:
type: string
- description: The unique identifier of a published release of the catalog or `latestPublished` for the most recently published version.
name: release_id
in: path
required: true
schema:
type: string
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/offset'
responses:
'200':
description: The products of a catalog.
content:
application/json:
schema:
$ref: '#/components/schemas/product-list-data'
default:
description: The unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/error-response'
/catalogs/{catalog_id}/releases/{release_id}/products/{product_id}:
get:
tags:
- Administrator Latest Releases Catalog API
summary: Get a Product
description: "Returns a product from a published catalog. The product must be in `live` status. Currently, published catalogs are limited to the current release and two releases prior to the current release.\n\n### Product and Node Associations in Breadcrumb Metadata\n\nYou can see the parent nodes a product is associated with in the `bread_crumbs` and `bread_crumb_nodes` metadata for each product. This is useful if you want to improve how your shoppers search your store, for example. See [Product and Node Associations in Breadcrumb Metadata](/guides/How-To/Catalogs/breadcrumbs).\n\n### Product Variations\n\nThe `variations` object lists the variation IDs and variation option IDs and their corresponding product IDs that are generated when the variation and variation options are built with a product. The `variations` object can then be added to your catalogs. By default, variations and variation options are sorted randomly. You can use the `sort_order`attribute to sort the order of your variation and variati
# --- truncated at 32 KB (122 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/elastic-path/refs/heads/main/openapi/elastic-path-administrator-latest-releases-catalog-api-api-openapi.yml