commerce-sdk-isomorphic 2.1.0 → 3.1.0

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # CHANGELOG
 
+## v3.1.0
+
+### Enhancements
+- Update SLAS helpers to support DNT parameter [#167](https://github.com/SalesforceCommerceCloud/commerce-sdk-isomorphic/pull/167)
+
+## v3.0.0
+
+### :warning: Planned API Changes :warning: 
+
+#### Shopper Context
+
+Starting July 31st 2024, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025. You can read more about the planned change [here](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-context?meta=Summary) in the notes section.
+
+#### Shopper Login (SLAS)
+
+SLAS will soon require new tenants to pass `channel_id` as an argument for retrieving guest access tokens. You can read more about the planned change [here](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html#guest-tokens).
+
+Please be aware that existing tenants are on a temporary allow list and will see no immediate disruption to service.  We do ask that all users seek to adhere to the `channel_id` requirement before the end of August to enhance your security posture before the holiday peak season.
+
+In practice, we recommend:
+
+- For customers using the SLAS helpers with a public client, it is recommended to upgrade to at least `v1.8.0` of the `commerce-sdk-isomorphic`.
+- For customers using the SLAS helpers with a private client, it is recommended to upgrade to `v3.0.0` of the `commerce-sdk-isomorphic`.
+
+### Enchancements
+
+- Update SLAS helper function `loginGuestUserPrivate` to require `channel_id` through `clientConfig.parameters.siteId` [#165](https://github.com/SalesforceCommerceCloud/commerce-sdk-isomorphic/pull/165)
+
 ## v2.1.0
 
 ### Enhancements

package/README.md

@@ -1,13 +1,32 @@
 # commerce-sdk-isomorphic
 
-The Salesforce Commerce SDK (Isomorphic) allows easy interaction with the B2C Commerce platform’s Shopper APIs on the Node.js runtime and works both in browsers and Node applications. For a Node-based SDK that can access the Admin APIs in addition to the Shopper APIs, see the main [Commerce SDK](https://github.com/SalesforceCommerceCloud/commerce-sdk). 
+This SDK provides a Browser & Node.js JavaScript client for calling [B2C Commerce Shopper APIs](https://developer.salesforce.com/docs/commerce/commerce-api/overview).
+
+_For a Node.js only SDK that can also access Admin APIs checkout [Commerce SDK](https://github.com/SalesforceCommerceCloud/commerce-sdk)._
+
+## :warning: Planned API Changes :warning:
+
+### Shopper Context
+
+Starting July 31st 2024, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025. You can read more about the planned change [here](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-context?meta=Summary) in the notes section.
+
+### Shopper Login (SLAS)
+
+SLAS will soon require new tenants to pass `channel_id` as an argument for retrieving guest access tokens. You can read more about the planned change [here](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html#guest-tokens).
+
+Please be aware that existing tenants are on a temporary allow list and will see no immediate disruption to service.  We do ask that all users seek to adhere to the `channel_id` requirement before the end of August to enhance your security posture before the holiday peak season.
+
+In practice, we recommend:
+
+- For customers using the SLAS helpers with a public client, it is recommended to upgrade to at least `v1.8.0` of the `commerce-sdk-isomorphic`.
+- For customers using the SLAS helpers with a private client, it is recommended to upgrade to `v3.0.0` of the `commerce-sdk-isomorphic`.
 
 ## Getting Started
 
 ### Requirements
 
 - Node `^12.x`, `^14.x`, `^16.x`, `^18.x`
-
+- The SDK requires B2C Commerce API (SCAPI) to be configured. For more info see [Getting started with SCAPI](https://developer.salesforce.com/docs/commerce/commerce-api/guide/get-started.html).
 
 ### Installation
 
@@ -17,55 +36,25 @@ npm install commerce-sdk-isomorphic
 
 ### Usage
 
-> **Note:** These are required parameters.
-
-| Parameter      | Description                                                                |
-| -------------- | :------------------------------------------------------------------------- |
-| clientId       | ID of the client account created with Salesforce Commerce.                 |
-| organizationId | The unique identifier for your Salesforce identity.                        |
-| shortCode      | Region-specific merchant ID.                                               |
-| siteId         | Name of the site to access data from, for example, RefArch or SiteGenesis. |
-
-
-### Configure the Isomorphic SDK
-
-
 ```javascript
-/**
- * Configure required parameters
- *
- * To learn more about the parameters please refer to https://developer.salesforce.com/docs/commerce/commerce-api/guide/get-started.html
- */
 import {helpers, ShopperLogin, ShopperSearch} from 'commerce-sdk-isomorphic';
 
-// Create a configuration to use when creating API clients
 const config = {
-  proxy: 'https://localhost:3000', // Routes API calls through a proxy when set
-  headers: {},
+  // SCAPI does not support CORS, so client side requests must use a reverse proxy.
+  proxy: 'https://localhost:3000',
   parameters: {
     clientId: '<your-client-id>',
     organizationId: '<your-org-id>',
     shortCode: '<your-short-code>',
     siteId: '<your-site-id>',
   },
-  throwOnBadResponse: true,
 };
 
-const shopperLogin = new ShopperLogin(config);
-// Execute Public Client OAuth with PKCE to acquire guest tokens
-const {access_token, refresh_token} = await helpers.loginGuestUser(
-  shopperLogin,
-  {redirectURI: `${config.proxy}/callback`} // Callback URL must be configured in SLAS Admin
+const {access_token} = await helpers.loginGuestUser(
+  new ShopperLogin(config),
+  {redirectURI: `${config.proxy}/callback`}
 );
 
-// Execute Private Client OAuth with PKCE to acquire guest tokens
-// ***WARNING*** Be cautious about using this function in the browser as you may end up exposing your client secret
-// only use it when you know your slas client secret is secured
-// const {access_token, refresh_token} = await helpers.loginGuestUserPrivate(
-//   shopperLogin,
-//   {}, {clientSecret: '<your-slas-client-secret>'}
-// );
-
 const shopperSearch = new ShopperSearch({
   ...config,
   headers: {authorization: `Bearer ${access_token}`},
@@ -76,59 +65,33 @@ const searchResult = await shopperSearch.productSearch({
 });
 ```
 
-#### CORS
-
-The Salesforce Commerce API (SCAPI) does not support CORS, so a proxy must be used to be able to use the SDK.
-
-### Advanced Options
+#### Fetch Options
 
-Commerce SDK Isomorphic supports Fetch API options for [node-fetch](https://github.com/node-fetch/node-fetch/1#api) on server and [whatwg-fetch](https://github.github.io/fetch/) on browser with a simple configuration.
-This sample code shows how to configure HTTP timeout and agent options.
+You can configure how the SDK makes requests using the `fetchOptions` parameter. It is passed to [node-fetch](https://github.com/node-fetch/node-fetch/1#api) on the server and [whatwg-fetch](https://github.github.io/fetch/) on browser.
 
 ```javascript
-/**
- * Configure advanced timeout and agent parameters
- *
- * To learn more about the parameters please refer to the [Salesforce Developer Center](https://developer.salesforce.com/docs/commerce/commerce-api).
- */
-// Create a configuration to use when creating API clients
-const https = require('https');
+const https = require("https");
 
 const config = {
-  proxy: 'https://localhost:3000',
-  headers: {},
-  parameters: {
-    clientId: '<your-client-id>',
-    organizationId: '<your-org-id>',
-    shortCode: '<your-short-code>',
-    siteId: '<your-site-id>',
-  },
   fetchOptions: {
-    timeout: 2000, //request times out after 2 seconds
-    agent: new https.agent({
-      // a custom http agent
-      keepAlive: true,
-    }),
+    // By default, requests made using the SDK do not include cookies.
+    credentials: "include",
+    timeout: 2000,
+    agent: new https.agent({ keepAlive: true }),
   },
 };
 ```
 
-### Additional Config Settings
-
-_headers:_ A collection of key/value string pairs representing additional headers to include with API requests.
-
-_throwOnBadResponse:_ Default value is false. When set to true, the SDK throws an Error on responses with statuses that are not 2xx or 304.
+For more info, refer to the [documentation site](https://salesforcecommercecloud.github.io/commerce-sdk-isomorphic/).
 
-### Public/Private Client Shopper Login (SLAS) helpers
+#### Additional Config Settings
 
-A collection of helper functions are available in this SDK to simplify [Public/Private Client Shopper Login OAuth flows](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-login:Summary). See sample code above for guest login.
-
-**⚠️ WARNING ⚠️**
-Users should be extremely cautious about using the SLAS private client helper functions in the browser as it can expose your client secret. Ensure that your client secret is secured before running the function client side.
+* `headers`: Headers to include with API requests.
+* `throwOnBadResponse`: When `true`, the SDK throws an `Error` on responses whose status is not 2xx or 304.
 
 ### Custom Query Parameters
 
-With the introduction of [hooks for Commerce APIs](https://developer.salesforce.com/docs/commerce/commerce-api/guide/extensibility_via_hooks.html), customers can pass custom query parameters through the SDK to be used in their custom hook. Custom query parameters must begin with `c_`:
+You can pass custom query parameters through the SDK to be used in [B2C Commerce API Hooks](https://developer.salesforce.com/docs/commerce/commerce-api/guide/extensibility_via_hooks.html). Custom query parameters must begin with `c_`:
 
 ```javascript
 const searchResult = await shopperSearch.productSearch({
@@ -139,19 +102,17 @@ const searchResult = await shopperSearch.productSearch({
 });
 ```
 
-Invalid query parameters that are not a part of the API and do not follow the `c_` custom query parameter convention will be filtered from the request and a warning will be displayed.
+Invalid query parameters that are not a part of the API and do not follow the `c_` custom query parameter convention are filtered from the request with a warning.
 
 ### Custom APIs
 
-The SDK supports calling [custom APIs](https://developer.salesforce.com/docs/commerce/commerce-api/guide/custom-apis.html) with a helper function, `callCustomEndpoint`.
-
-Example usage:
+The SDK supports calling [B2C Commerce Custom APIs](https://developer.salesforce.com/docs/commerce/commerce-api/guide/custom-apis.html) with a helper function, `callCustomEndpoint`:
 
 ```javascript
-import pkg from 'commerce-sdk-isomorphic';
+import pkg from "commerce-sdk-isomorphic";
 const { helpers } = pkg;
 
-const clientConfigExample = {
+const clientConfig = {
   parameters: {
     clientId: "<your-client-id>",
     organizationId: "<your-org-id>",
@@ -161,63 +122,54 @@ const clientConfigExample = {
   // If not provided, it'll use the default production URI:
   // 'https://{shortCode}.api.commercecloud.salesforce.com/custom/{apiName}/{apiVersion}'
   // path parameters should be wrapped in curly braces like the default production URI
-  baseUri: "<your-base-uri>"
+  baseUri: "<your-base-uri>",
 };
 
 // Required params: apiName, endpointPath, shortCode, organizaitonId
 // Required path params can be passed into:
 // options.customApiPathParameters or clientConfig.parameters
-const customApiArgs = { 
-  apiName: 'loyalty-info',
-  apiVersion: 'v1', // defaults to v1 if not provided
-  endpointPath: 'customers'
-}
+const customApiPathParameters = {
+  apiName: "loyalty-info",
+  apiVersion: "v1", // defaults to v1 if not provided
+  endpointPath: "customers",
+};
 
-const accessToken = '<INSERT ACCESS TOKEN HERE>';
+const accessToken = "<INSERT ACCESS TOKEN HERE>";
 
-let getResponse = await helpers.callCustomEndpoint({
+await helpers.callCustomEndpoint({
   options: {
-    method: 'GET',
+    method: "GET",
     parameters: {
-      queryParameter: 'queryParameter1',
+      queryParameter: "queryParameter1",
     },
     headers: {
       // Content-Type is defaulted to application/json if not provided
-      'Content-Type': 'application/json',
-      authorization: `Bearer ${access_token}`
+      "Content-Type": "application/json",
+      authorization: `Bearer ${accessToken}`,
     },
-    customApiPathParameters: customApiArgs
-  }, 
-  clientConfig: clientConfigExample,
-  // Flag to retrieve raw response or data from helper function
-  rawResponse: false, 
-})
-
-let postResponse = await helpers.callCustomEndpoint({
+    customApiPathParameters,
+  },
+  clientConfig,
+});
+
+await helpers.callCustomEndpoint({
   options: {
-    method: 'POST',
+    method: "POST",
     parameters: {
-      queryParameter: 'queryParameter1',
+      queryParameter: "queryParameter1",
     },
     headers: {
-      authorization: `Bearer ${access_token}`
+      authorization: `Bearer ${accessToken}`,
     },
-    customApiPathParameters: customApiArgs,
-    body: JSON.stringify({ data: 'data' })
-  }, 
-  clientConfig: clientConfigExample,
-  // Flag to retrieve raw response or data from helper function
-  rawResponse: false, 
-})
-
-console.log('get response: ', getResponse)
-console.log('post response: ', postResponse)
+    customApiPathParameters,
+    body: JSON.stringify({ data: "data" }),
+  },
+  clientConfig,
+});
 ```
 
 For more documentation about this helper function, please refer to the [commerce-sdk-isomorphic docs](https://salesforcecommercecloud.github.io/commerce-sdk-isomorphic/modules/helpers.html).
 
-For more information about custom APIs, please refer to the [Salesforce Developer Docs](https://developer.salesforce.com/docs/commerce/commerce-api/guide/custom-apis.html)
-
 ## License Information
 
 The Commerce SDK Isomorphic is licensed under BSD-3-Clause license. See the [license](./LICENSE.txt) for details.

package/lib/index.cjs.d.ts

@@ -8551,7 +8551,7 @@ type ShopperContextsParameters = ShopperContextsPathParameters & BaseUriParamete
  * ```
  *
  * <span style="font-size:.7em; display:block; text-align: right">
- * API Version: 0.0.28<br />
+ * API Version: 0.0.29<br />
  * Last Updated: <br />
  * </span>
  *
@@ -8606,6 +8606,8 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
     };
     /**
      * Gets the shopper's context based on the shopperJWT.
+     
+     With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
      *
      * If you would like to get a raw Response object use the other getShopperContext function.
      *
@@ -8613,7 +8615,7 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
      * @param parameters - An object containing the parameters for this method.
      * @param organizationId -
      * @param usid - The Shopper's unique identifier. It is a required parameter and is part of the response from the Guest or Registered User Shopper Login (SLAS) API call.
-     * @param siteId - The identifier of the site to which the request is being sent. With B2C Commerce release 24.5, all new implementations of Shopper Context require the `siteId` query parameter to be passed. Existing customers with Shopper Context implementations should start including `siteId` going forward. Starting July 31 2024, `siteId` will be required for all customers, and a bad request response code will be returned for requests without a `siteId`.
+     * @param siteId - The identifier of the site to which the request is being sent. With B2C Commerce release 24.5, all new implementations of Shopper Context require the `siteId` query parameter to be passed. Existing customers with Shopper Context implementations should start including `siteId` going forward. Starting January 2025, `siteId` will be required for all customers, and a bad request response code will be returned for requests without a `siteId`.
      * @param headers - An object literal of key value pairs of the headers to be
      * sent with this request.
      *
@@ -8634,12 +8636,14 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
     }>): Promise<ShopperContext>;
     /**
      * Gets the shopper's context based on the shopperJWT.
+     
+     With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
      *
      * @param options - An object containing the options for this method.
      * @param parameters - An object containing the parameters for this method.
      * @param organizationId -
      * @param usid - The Shopper's unique identifier. It is a required parameter and is part of the response from the Guest or Registered User Shopper Login (SLAS) API call.
-     * @param siteId - The identifier of the site to which the request is being sent. With B2C Commerce release 24.5, all new implementations of Shopper Context require the `siteId` query parameter to be passed. Existing customers with Shopper Context implementations should start including `siteId` going forward. Starting July 31 2024, `siteId` will be required for all customers, and a bad request response code will be returned for requests without a `siteId`.
+     * @param siteId - The identifier of the site to which the request is being sent. With B2C Commerce release 24.5, all new implementations of Shopper Context require the `siteId` query parameter to be passed. Existing customers with Shopper Context implementations should start including `siteId` going forward. Starting January 2025, `siteId` will be required for all customers, and a bad request response code will be returned for requests without a `siteId`.
      * @param headers - An object literal of key value pairs of the headers to be
      * sent with this request.
      * @param rawResponse - Set to true to return entire Response object instead of DTO.
@@ -8660,6 +8664,8 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
     }>, rawResponse?: T): Promise<T extends true ? Response : ShopperContext>;
     /**
      * Creates the shopper's context based on shopperJWT.
+     
+     With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
      *
      * If you would like to get a raw Response object use the other createShopperContext function.
      *
@@ -8698,6 +8704,8 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
     }>): Promise<void | void>;
     /**
      * Creates the shopper's context based on shopperJWT.
+     
+     With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
      *
      * @param options - An object containing the options for this method.
      * @param parameters - An object containing the parameters for this method.
@@ -8734,6 +8742,8 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
     }>, rawResponse?: T): Promise<T extends true ? Response : void | void>;
     /**
      * Gets the shopper's context based on the shopperJWT.
+     
+     With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
      *
      * If you would like to get a raw Response object use the other deleteShopperContext function.
      *
@@ -8762,6 +8772,8 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
     }>): Promise<void>;
     /**
      * Gets the shopper's context based on the shopperJWT.
+     
+     With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
      *
      * @param options - An object containing the options for this method.
      * @param parameters - An object containing the parameters for this method.
@@ -8788,6 +8800,8 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
     }>, rawResponse?: T): Promise<T extends true ? Response : void>;
     /**
      * Updates the shopper's context based on the Shopper JWT. If the shopper context exists, it's updated with the patch body. If a `custom qualifier/assignment qualifer` or an `effectiveDateTime` or a `sourceCode` or a `customerGroupIds` is already present in the existing shopper context, its value is replaced by the corresponding value from the patch body. If a `custom qualifers'` or a `assignment qualifiers'` value is set to `null`, it's deleted from existing shopper context. If `effectiveDateTime` or `sourceCode` value is set to an empty string (\"\"), it's deleted from existing shopper context. If `effectiveDateTime` or `sourceCode` value is set to `null`, it's ignored. If an `effectiveDateTime` or `sourceCode` or `custom/assignment qualifiiers'` value is new, it's added to the existing Shopper context. If `customerGroupIds` is set to empty array `[]` the existing value in shopper context is deleted.
+     
+     With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
      *
      * If you would like to get a raw Response object use the other updateShopperContext function.
      *
@@ -8826,6 +8840,8 @@ declare class ShopperContexts<ConfigParameters extends ShopperContextsParameters
     }>): Promise<ShopperContext>;
     /**
      * Updates the shopper's context based on the Shopper JWT. If the shopper context exists, it's updated with the patch body. If a `custom qualifier/assignment qualifer` or an `effectiveDateTime` or a `sourceCode` or a `customerGroupIds` is already present in the existing shopper context, its value is replaced by the corresponding value from the patch body. If a `custom qualifers'` or a `assignment qualifiers'` value is set to `null`, it's deleted from existing shopper context. If `effectiveDateTime` or `sourceCode` value is set to an empty string (\"\"), it's deleted from existing shopper context. If `effectiveDateTime` or `sourceCode` value is set to `null`, it's ignored. If an `effectiveDateTime` or `sourceCode` or `custom/assignment qualifiiers'` value is new, it's added to the existing Shopper context. If `customerGroupIds` is set to empty array `[]` the existing value in shopper context is deleted.
+     
+     With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
      *
      * @param options - An object containing the options for this method.
      * @param parameters - An object containing the parameters for this method.
@@ -9278,7 +9294,7 @@ declare namespace ShopperContextsTypes {
      * ```
      *
      * <span style="font-size:.7em; display:block; text-align: right">
-     * API Version: 0.0.28<br />
+     * API Version: 0.0.29<br />
      * Last Updated: <br />
      * </span>
      *
@@ -9333,6 +9349,8 @@ declare namespace ShopperContextsTypes {
         };
         /**
          * Gets the shopper's context based on the shopperJWT.
+         
+         With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
          *
          * If you would like to get a raw Response object use the other getShopperContext function.
          *
@@ -9340,7 +9358,7 @@ declare namespace ShopperContextsTypes {
          * @param parameters - An object containing the parameters for this method.
          * @param organizationId -
          * @param usid - The Shopper's unique identifier. It is a required parameter and is part of the response from the Guest or Registered User Shopper Login (SLAS) API call.
-         * @param siteId - The identifier of the site to which the request is being sent. With B2C Commerce release 24.5, all new implementations of Shopper Context require the `siteId` query parameter to be passed. Existing customers with Shopper Context implementations should start including `siteId` going forward. Starting July 31 2024, `siteId` will be required for all customers, and a bad request response code will be returned for requests without a `siteId`.
+         * @param siteId - The identifier of the site to which the request is being sent. With B2C Commerce release 24.5, all new implementations of Shopper Context require the `siteId` query parameter to be passed. Existing customers with Shopper Context implementations should start including `siteId` going forward. Starting January 2025, `siteId` will be required for all customers, and a bad request response code will be returned for requests without a `siteId`.
          * @param headers - An object literal of key value pairs of the headers to be
          * sent with this request.
          *
@@ -9361,12 +9379,14 @@ declare namespace ShopperContextsTypes {
         }>): Promise<ShopperContext>;
         /**
          * Gets the shopper's context based on the shopperJWT.
+         
+         With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
          *
          * @param options - An object containing the options for this method.
          * @param parameters - An object containing the parameters for this method.
          * @param organizationId -
          * @param usid - The Shopper's unique identifier. It is a required parameter and is part of the response from the Guest or Registered User Shopper Login (SLAS) API call.
-         * @param siteId - The identifier of the site to which the request is being sent. With B2C Commerce release 24.5, all new implementations of Shopper Context require the `siteId` query parameter to be passed. Existing customers with Shopper Context implementations should start including `siteId` going forward. Starting July 31 2024, `siteId` will be required for all customers, and a bad request response code will be returned for requests without a `siteId`.
+         * @param siteId - The identifier of the site to which the request is being sent. With B2C Commerce release 24.5, all new implementations of Shopper Context require the `siteId` query parameter to be passed. Existing customers with Shopper Context implementations should start including `siteId` going forward. Starting January 2025, `siteId` will be required for all customers, and a bad request response code will be returned for requests without a `siteId`.
          * @param headers - An object literal of key value pairs of the headers to be
          * sent with this request.
          * @param rawResponse - Set to true to return entire Response object instead of DTO.
@@ -9387,6 +9407,8 @@ declare namespace ShopperContextsTypes {
         }>, rawResponse?: T): Promise<T extends true ? Response : ShopperContext>;
         /**
          * Creates the shopper's context based on shopperJWT.
+         
+         With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
          *
          * If you would like to get a raw Response object use the other createShopperContext function.
          *
@@ -9425,6 +9447,8 @@ declare namespace ShopperContextsTypes {
         }>): Promise<void | void>;
         /**
          * Creates the shopper's context based on shopperJWT.
+         
+         With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
          *
          * @param options - An object containing the options for this method.
          * @param parameters - An object containing the parameters for this method.
@@ -9461,6 +9485,8 @@ declare namespace ShopperContextsTypes {
         }>, rawResponse?: T): Promise<T extends true ? Response : void | void>;
         /**
          * Gets the shopper's context based on the shopperJWT.
+         
+         With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
          *
          * If you would like to get a raw Response object use the other deleteShopperContext function.
          *
@@ -9489,6 +9515,8 @@ declare namespace ShopperContextsTypes {
         }>): Promise<void>;
         /**
          * Gets the shopper's context based on the shopperJWT.
+         
+         With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
          *
          * @param options - An object containing the options for this method.
          * @param parameters - An object containing the parameters for this method.
@@ -9515,6 +9543,8 @@ declare namespace ShopperContextsTypes {
         }>, rawResponse?: T): Promise<T extends true ? Response : void>;
         /**
          * Updates the shopper's context based on the Shopper JWT. If the shopper context exists, it's updated with the patch body. If a `custom qualifier/assignment qualifer` or an `effectiveDateTime` or a `sourceCode` or a `customerGroupIds` is already present in the existing shopper context, its value is replaced by the corresponding value from the patch body. If a `custom qualifers'` or a `assignment qualifiers'` value is set to `null`, it's deleted from existing shopper context. If `effectiveDateTime` or `sourceCode` value is set to an empty string (\"\"), it's deleted from existing shopper context. If `effectiveDateTime` or `sourceCode` value is set to `null`, it's ignored. If an `effectiveDateTime` or `sourceCode` or `custom/assignment qualifiiers'` value is new, it's added to the existing Shopper context. If `customerGroupIds` is set to empty array `[]` the existing value in shopper context is deleted.
+         
+         With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
          *
          * If you would like to get a raw Response object use the other updateShopperContext function.
          *
@@ -9553,6 +9583,8 @@ declare namespace ShopperContextsTypes {
         }>): Promise<ShopperContext>;
         /**
          * Updates the shopper's context based on the Shopper JWT. If the shopper context exists, it's updated with the patch body. If a `custom qualifier/assignment qualifer` or an `effectiveDateTime` or a `sourceCode` or a `customerGroupIds` is already present in the existing shopper context, its value is replaced by the corresponding value from the patch body. If a `custom qualifers'` or a `assignment qualifiers'` value is set to `null`, it's deleted from existing shopper context. If `effectiveDateTime` or `sourceCode` value is set to an empty string (\"\"), it's deleted from existing shopper context. If `effectiveDateTime` or `sourceCode` value is set to `null`, it's ignored. If an `effectiveDateTime` or `sourceCode` or `custom/assignment qualifiiers'` value is new, it's added to the existing Shopper context. If `customerGroupIds` is set to empty array `[]` the existing value in shopper context is deleted.
+         
+         With B2C Commerce release 24.5, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025.
          *
          * @param options - An object containing the options for this method.
          * @param parameters - An object containing the parameters for this method.
@@ -18229,8 +18261,6 @@ type GiftCertificate = {
 };
 type GiftCertificateRequest = {
     giftCertificateCode: string;
-} & {
-    [key: string]: any;
 };
 type RangeFilter$4 = {
     [key: string]: any;
@@ -18374,7 +18404,7 @@ type ShopperGiftCertificatesParameters = ShopperGiftCertificatesPathParameters &
  * ```
  *
  * <span style="font-size:.7em; display:block; text-align: right">
- * API Version: 1.0.16<br />
+ * API Version: 1.0.17<br />
  * Last Updated: <br />
  * </span>
  *
@@ -18560,8 +18590,6 @@ declare namespace ShopperGiftCertificatesTypes {
     };
     type GiftCertificateRequest = {
         giftCertificateCode: string;
-    } & {
-        [key: string]: any;
     };
     type ErrorResponse = {
         type: string;
@@ -18860,7 +18888,7 @@ declare namespace ShopperGiftCertificatesTypes {
      * ```
      *
      * <span style="font-size:.7em; display:block; text-align: right">
-     * API Version: 1.0.16<br />
+     * API Version: 1.0.17<br />
      * Last Updated: <br />
      * </span>
      *
@@ -26810,8 +26838,6 @@ type PromotionResult = {
     limit: number;
     data: Array<Promotion>;
     total: number;
-} & {
-    [key: string]: any;
 };
 type RangeFilter$8 = {
     [key: string]: any;
@@ -26961,7 +26987,7 @@ type ShopperPromotionsParameters = ShopperPromotionsPathParameters & BaseUriPara
  * ```
  *
  * <span style="font-size:.7em; display:block; text-align: right">
- * API Version: 1.0.26<br />
+ * API Version: 1.0.27<br />
  * Last Updated: <br />
  * </span>
  *
@@ -27240,8 +27266,6 @@ declare namespace ShopperPromotionsTypes {
         limit: number;
         data: Array<Promotion>;
         total: number;
-    } & {
-        [key: string]: any;
     };
     type Error = {
         type: string;
@@ -27546,7 +27570,7 @@ declare namespace ShopperPromotionsTypes {
      * ```
      *
      * <span style="font-size:.7em; display:block; text-align: right">
-     * API Version: 1.0.26<br />
+     * API Version: 1.0.27<br />
      * Last Updated: <br />
      * </span>
      *
@@ -32950,6 +32974,7 @@ declare namespace helpers {
      * @param credentials.clientSecret - secret associated with client ID
      * @param parameters - parameters to pass in the API calls.
      * @param parameters.usid? - Unique Shopper Identifier to enable personalization.
+     * @param parameters.dnt? - Optional parameter to enable Do Not Track (DNT) for the user.
      * @returns TokenResponse
      */
     function loginGuestUserPrivate(slasClient: ShopperLogin<{
@@ -32959,6 +32984,7 @@ declare namespace helpers {
         siteId: string;
     }>, parameters: {
         usid?: string;
+        dnt?: boolean;
     }, credentials: {
         clientSecret: string;
     }): Promise<TokenResponse>;
@@ -32968,6 +32994,7 @@ declare namespace helpers {
      * @param parameters - parameters to pass in the API calls.
      * @param parameters.redirectURI - Per OAuth standard, a valid app route. Must be listed in your SLAS configuration. On server, this will not be actually called. On browser, this will be called, but ignored.
      * @param parameters.usid? - Unique Shopper Identifier to enable personalization.
+     * @param parameters.dnt? - Optional parameter to enable Do Not Track (DNT) for the user.
      * @returns TokenResponse
      */
     function loginGuestUser(slasClient: ShopperLogin<{
@@ -32978,6 +33005,7 @@ declare namespace helpers {
     }>, parameters: {
         redirectURI: string;
         usid?: string;
+        dnt?: boolean;
     }): Promise<TokenResponse>;
     /**
      * A single function to execute the ShopperLogin Public Client Registered User B2C Login with proof key for code exchange flow as described in the [API documentation](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-login:Summary).
@@ -32990,6 +33018,7 @@ declare namespace helpers {
      * @param parameters - parameters to pass in the API calls.
      * @param parameters.redirectURI - Per OAuth standard, a valid app route. Must be listed in your SLAS configuration. On server, this will not be actually called. On browser, this will be called, but ignored.
      * @param parameters.usid? - Unique Shopper Identifier to enable personalization.
+     * @param parameters.dnt? - Optional parameter to enable Do Not Track (DNT) for the user.
      * @returns TokenResponse
      */
     function loginRegisteredUserB2C(slasClient: ShopperLogin<{
@@ -33004,6 +33033,7 @@ declare namespace helpers {
     }, parameters: {
         redirectURI: string;
         usid?: string;
+        dnt?: boolean;
     }): Promise<TokenResponse>;
     /**
      * Exchange a refresh token for a new access token.
@@ -33022,6 +33052,7 @@ declare namespace helpers {
         siteId: string;
     }>, parameters: {
         refreshToken: string;
+        dnt?: boolean;
     }, credentials?: {
         clientSecret?: string;
     }): Promise<TokenResponse>;