Get a Page Designer page based on a single page ID. The results will apply the visibility rules for the page's components, such as personalization or scheduled visibility.
Important*: Currently, the Shopper Experience API can’t be used when the storefront password protection feature is enabled.
Important*: Because this resource uses the GET method, you must not pass sensitive data (payment card information, for example) and must not perform any transactional processes within the server-side scripts that are run for the page and components.
If you would like to get a raw Response object use the other getPage function.
Get a Page Designer page based on a single page ID. The results will apply the visibility rules for the page's components, such as personalization or scheduled visibility.
Important*: Currently, the Shopper Experience API can’t be used when the storefront password protection feature is enabled.
Important*: Because this resource uses the GET method, you must not pass sensitive data (payment card information, for example) and must not perform any transactional processes within the server-side scripts that are run for the page and components.
Get Page Designer pages. The results will apply the visibility rules for each page's components, such as personalization or scheduled visibility.
Either categoryId or productId must be given in addition to aspectTypeId. Because only a single page-to-product and page-to-category assignment per aspect type can be authored today, the returned result contains one element at most.
Important*: Currently, the Shopper Experience API can’t be used when the storefront password protection feature is enabled.
Important*: Because this resource uses the GET method, you must not pass sensitive data (payment card information, for example) and must not perform any transactional processes within the server-side scripts that are run for the page and components.
If you would like to get a raw Response object use the other getPages function.
Get Page Designer pages. The results will apply the visibility rules for each page's components, such as personalization or scheduled visibility.
Either categoryId or productId must be given in addition to aspectTypeId. Because only a single page-to-product and page-to-category assignment per aspect type can be authored today, the returned result contains one element at most.
Important*: Currently, the Shopper Experience API can’t be used when the storefront password protection feature is enabled.
Important*: Because this resource uses the GET method, you must not pass sensitive data (payment card information, for example) and must not perform any transactional processes within the server-side scripts that are run for the page and components.
Shopper Experience
**
Example with shopper auth
API Version: 1.0.4import { Experience, ClientConfig, Customer, slasHelpers } from "commerce-sdk"; // or const { Experience, ClientConfig, Customer, slasHelpers } = require("commerce-sdk"); const clientConfig: ClientConfig = { parameters: { clientId: "XXXXXX", organizationId: "XXXX", shortCode: "XXX", siteId: "XX" } }; // must be registered in SLAS. On server, redirectURI is never called const redirectURI = "http://localhost:3000/callback"; const slasClient = new Customer.ShopperLogin(clientConfig); token = await slasHelpers.loginGuestUser(slasClient, { redirectURI }); clientConfig.headers['authorization'] = `Bearer ${token.access_token}`; const shopperExperienceClient = new Experience.ShopperExperience(clientConfig);
Last Updated: