Improved Layered Navigation/Shop By Brand API
API functionality for Improved Layered Navigation and Shop By Brand is added by its submodule Improved Layered Navigation Pages (shop-by-page).
Amasty\ShopbyPage\Api\PageRepositoryInterface - class for pages:
- POST /V1/amasty_shopbypage/page, method="save" - create a page;
- PUT /V1/amasty_shopbypage/page/:pageId, method="save" - edit a page;
- DELETE /V1/amasty_shopbypage/page/:pageId, method="deleteById" - delete a page;
- GET /V1/amasty_shopbypage/page, method="get" - get a specifc page;
- GET /V1/amasty_shopbypage/page/list, method="getList" - get a list of all pages.
Related Articles
Improved Layered Navigation | GraphQL methods
The Improved Layered Navigation extension doesn't have its own GraphQL requests. Instead, it extends the default Magento requests by introducing supplementary details. You can get additional information stored by the Improved Layered Navigation ...
How to resolve the "Please select brand attribute in Stores → Configuration → Amasty Extensions → Improved Layered Navigation: Brands." frontend error?
The message “Please select brand attribute in Stores → Configuration → Amasty Extensions → Improved Layered Navigation: Brands” appearing on your All Brands Page indicates that additional configuration is required to display the brands on the ...
Shop by Brand | GraphQL methods
Queries ambrandlist (imageWidth: Int, imageHeight: Int, showCount: Boolean, displayZero: Boolean) description: show brands without products ambrandslider (imageWidth: Int, imageHeight: Int, sortBy: String, displayZero: Boolean) description: show ...
How to disable Improved Layered Navigation on a specific store?
For multistore installations, this option is not covered. Although the settings for the Improved Layered Navigation module can be configured individually for each store view, the module cannot be disabled on a store view basis.
What Amasty extensions support API?
Each Amasty extension that has API support, includes the etc/webapi.xml file. The webapi.xml file contains API configurations with the list of available API requests. For example, a request from the Custom Form module interface: 1 - endpoint URL; 2 - ...