commerce-sdk-isomorphic 4.0.1 → 4.2.0

package/lib/index.cjs.d.ts

@@ -1384,6 +1384,7 @@ type removeShipmentFromBasketPathParameters = {
 type transferBasketQueryParameters = {
     siteId: string;
     overrideExisting?: boolean;
+    merge?: boolean;
     locale?: LocaleCode$0;
 };
 type transferBasketPathParameters = {
@@ -1524,7 +1525,9 @@ type ShopperBasketsParameters = ShopperBasketsPathParameters & BaseUriParameters
  * [Shopper Baskets](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-baskets:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-baskets/shopper-baskets-oas-v1-public.yaml)
+ 
+ # API Overview
  
  Use the Shopper Baskets API to create a basket in the B2C Commerce system and populate it with all the data required to ready the basket for checkout.
  
@@ -1957,6 +1960,7 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
             "siteId",
             "organizationId",
             "overrideExisting",
+            "merge",
             "locale"
         ];
         readonly transferBasketRequired: readonly [
@@ -3066,7 +3070,9 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
         };
     }>, rawResponse?: T): Promise<T extends true ? Response : Taxes>;
     /**
-     * Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
+     * ( DEPRECATED ) Instead of using this endpoint, we recommend using the `/baskets/actions/transfer` endpoint with the `merge=true` parameter, because the transfer endpoint offers greater customization by invoking a hook, allowing for adjustments if the default implementation does not process the merge as expected.
+     
+     Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
      
      The following information is merged:
      - custom attributes on the basket and on all copied records
@@ -3138,7 +3144,9 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
         };
     }>): Promise<Basket>;
     /**
-     * Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
+     * ( DEPRECATED ) Instead of using this endpoint, we recommend using the `/baskets/actions/transfer` endpoint with the `merge=true` parameter, because the transfer endpoint offers greater customization by invoking a hook, allowing for adjustments if the default implementation does not process the merge as expected.
+     
+     Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
      
      The following information is merged:
      - custom attributes on the basket and on all copied records
@@ -3545,12 +3553,16 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
     /**
      * Transfer the previous shopper's basket to the current shopper by updating the basket's owner. No other values change. You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token.
      
-     A success response contains the transferred basket.
+     This endpoint provides different methods for handling the scenario in which both a previous guest shopper and the current registered shopper have an active basket attached, and utilizes the `merge` parameter as follows:
+     - `true` (recommended): Triggers a merge hook for graceful handling and prevents 409 status returns. For more information, refer to the `merge` parameter documentation.
+     - `false`: Either overrides the basket of the current registered shopper or returns a 409 response, and allows you to choose between the options explained below.
      
-     If the current shopper has an active basket, and the `overrideExisting` request parameter is `false`, then the transfer request returns a BasketTransferException (HTTP status 409). You can proceed with one of these options:
+     If you call the endpoint with `merge=false` and the current shopper has an active basket, you have two options using the `overrideExisting` parameter. Setting it to `true` deletes the registered user's basket, while setting it to `false` returns a `BasketTransferException` (HTTP status 409), after which you can choose how to proceed:
      - Keep the current shopper's active basket.
-     - Merge the previous and current shoppers' baskets by calling the `baskets/merge` endpoint.
-     - Force the transfer by calling the `baskets/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+     - Merge the previous and current shoppers' baskets by calling the `baskets/actions/merge` endpoint.
+     - Force the transfer by calling the `baskets/actions/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+     
+     A successful response provides the transferred (and merged) current basket. However, if neither the previous nor current shopper had an active basket, a 204 (No Content) response is returned.
      *
      * If you would like to get a raw Response object use the other transferBasket function.
      *
@@ -3561,6 +3573,31 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
      * @param options.parameters.overrideExisting - If the current shopper has no active basket, this parameter is ignored. If the current shopper has an active basket, this parameter controls the behavior:
      - `false` (default): Return a BasketTransferException (HTTP status 409). The basket owner doesn't change.
      - `true`: Force the transfer by deleting the current shopper's active basket and making the current shopper the owner of the previous shopper's basket. Returns the transferred basket (HTTP status 200).
+     * @param options.parameters.merge - This parameter controls the behavior:
+     - `false` (default): Transfers the basket or returns a 409 response with the appropriate message (taking `overrideExisting` in consideration).
+     - `true`: (recommended): Executes the dw.order.mergeBasket hook if at least one basket exists.
+     
+     The hook dw.order.mergeBasket default implementation merges a source basket into the current basket. This behavior can be customized, as shown
+     in this [sample implementation](https://gist.github.com/sf-thomas-loesche/3446c7d71a97e559bf1caee96ae56d9f).
+     
+     There are four possible use cases:
+     
+     a) Guest basket and registered basket exist
+     The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+     dw.order.mergeBasket is called with the source basket (former registered shopper basket) and the transferred current basket (former guest basket).
+     
+     b) Guest basket exists but no registered basket exists
+     The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+     dw.order.mergeBasket is called without the source basket (null passed to the hook) and the transferred current basket (former guest basket).
+     
+     c) No guest basket exists but a registered basket exists
+     The registered basket is retained. The hook dw.order.mergeBasket is called with the retained current basket but without the source basket (null
+     passed to the hook).
+     
+     d) Neither basket exists
+     The hook dw.order.mergeBasket is not called.
+     
+     The API returns the current basket (after executing dw.order.mergeBasket).
      * @param options.parameters.locale - A descriptor for a geographical region by both a language and country code. By combining these two, regional differences in a language can be addressed, such as with the request header parameter `Accept-Language` following [RFC 2616](https://tools.ietf.org/html/rfc2616) & [RFC 1766](https://tools.ietf.org/html/rfc1766). This can also just refer to a language code, also RFC 2616/1766 compliant, as a default if there is no specific match for a country. Finally, can also be used to define default behavior if there is no locale specified.
      * @param options.headers - An object literal of key value pairs of the headers to be sent with this request.
      *
@@ -3571,6 +3608,7 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
             siteId: string;
             organizationId: string;
             overrideExisting?: boolean;
+            merge?: boolean;
             locale?: LocaleCode$0;
         } & QueryParameters, ConfigParameters>;
         headers?: {
@@ -3580,12 +3618,16 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
     /**
      * Transfer the previous shopper's basket to the current shopper by updating the basket's owner. No other values change. You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token.
      
-     A success response contains the transferred basket.
+     This endpoint provides different methods for handling the scenario in which both a previous guest shopper and the current registered shopper have an active basket attached, and utilizes the `merge` parameter as follows:
+     - `true` (recommended): Triggers a merge hook for graceful handling and prevents 409 status returns. For more information, refer to the `merge` parameter documentation.
+     - `false`: Either overrides the basket of the current registered shopper or returns a 409 response, and allows you to choose between the options explained below.
      
-     If the current shopper has an active basket, and the `overrideExisting` request parameter is `false`, then the transfer request returns a BasketTransferException (HTTP status 409). You can proceed with one of these options:
+     If you call the endpoint with `merge=false` and the current shopper has an active basket, you have two options using the `overrideExisting` parameter. Setting it to `true` deletes the registered user's basket, while setting it to `false` returns a `BasketTransferException` (HTTP status 409), after which you can choose how to proceed:
      - Keep the current shopper's active basket.
-     - Merge the previous and current shoppers' baskets by calling the `baskets/merge` endpoint.
-     - Force the transfer by calling the `baskets/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+     - Merge the previous and current shoppers' baskets by calling the `baskets/actions/merge` endpoint.
+     - Force the transfer by calling the `baskets/actions/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+     
+     A successful response provides the transferred (and merged) current basket. However, if neither the previous nor current shopper had an active basket, a 204 (No Content) response is returned.
      *
      * @param options - An object containing the options for this method.
      * @param options.parameters - An object containing the parameters for this method.
@@ -3594,6 +3636,31 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
      * @param options.parameters.overrideExisting - If the current shopper has no active basket, this parameter is ignored. If the current shopper has an active basket, this parameter controls the behavior:
      - `false` (default): Return a BasketTransferException (HTTP status 409). The basket owner doesn't change.
      - `true`: Force the transfer by deleting the current shopper's active basket and making the current shopper the owner of the previous shopper's basket. Returns the transferred basket (HTTP status 200).
+     * @param options.parameters.merge - This parameter controls the behavior:
+     - `false` (default): Transfers the basket or returns a 409 response with the appropriate message (taking `overrideExisting` in consideration).
+     - `true`: (recommended): Executes the dw.order.mergeBasket hook if at least one basket exists.
+     
+     The hook dw.order.mergeBasket default implementation merges a source basket into the current basket. This behavior can be customized, as shown
+     in this [sample implementation](https://gist.github.com/sf-thomas-loesche/3446c7d71a97e559bf1caee96ae56d9f).
+     
+     There are four possible use cases:
+     
+     a) Guest basket and registered basket exist
+     The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+     dw.order.mergeBasket is called with the source basket (former registered shopper basket) and the transferred current basket (former guest basket).
+     
+     b) Guest basket exists but no registered basket exists
+     The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+     dw.order.mergeBasket is called without the source basket (null passed to the hook) and the transferred current basket (former guest basket).
+     
+     c) No guest basket exists but a registered basket exists
+     The registered basket is retained. The hook dw.order.mergeBasket is called with the retained current basket but without the source basket (null
+     passed to the hook).
+     
+     d) Neither basket exists
+     The hook dw.order.mergeBasket is not called.
+     
+     The API returns the current basket (after executing dw.order.mergeBasket).
      * @param options.parameters.locale - A descriptor for a geographical region by both a language and country code. By combining these two, regional differences in a language can be addressed, such as with the request header parameter `Accept-Language` following [RFC 2616](https://tools.ietf.org/html/rfc2616) & [RFC 1766](https://tools.ietf.org/html/rfc1766). This can also just refer to a language code, also RFC 2616/1766 compliant, as a default if there is no specific match for a country. Finally, can also be used to define default behavior if there is no locale specified.
      * @param options.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.
@@ -3605,6 +3672,7 @@ declare class ShopperBaskets<ConfigParameters extends ShopperBasketsParameters &
             siteId: string;
             organizationId: string;
             overrideExisting?: boolean;
+            merge?: boolean;
             locale?: LocaleCode$0;
         } & QueryParameters, ConfigParameters>;
         headers?: {
@@ -5899,6 +5967,7 @@ declare namespace ShopperBasketsApiTypes {
     type transferBasketQueryParameters = {
         siteId: string;
         overrideExisting?: boolean;
+        merge?: boolean;
         locale?: LocaleCode$0;
     };
     type transferBasketPathParameters = {
@@ -6039,7 +6108,9 @@ declare namespace ShopperBasketsApiTypes {
      * [Shopper Baskets](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-baskets:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-baskets/shopper-baskets-oas-v1-public.yaml)
+     
+     # API Overview
      
      Use the Shopper Baskets API to create a basket in the B2C Commerce system and populate it with all the data required to ready the basket for checkout.
      
@@ -6472,6 +6543,7 @@ declare namespace ShopperBasketsApiTypes {
                 "siteId",
                 "organizationId",
                 "overrideExisting",
+                "merge",
                 "locale"
             ];
             readonly transferBasketRequired: readonly [
@@ -7581,7 +7653,9 @@ declare namespace ShopperBasketsApiTypes {
             };
         }>, rawResponse?: T): Promise<T extends true ? Response : Taxes>;
         /**
-         * Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
+         * ( DEPRECATED ) Instead of using this endpoint, we recommend using the `/baskets/actions/transfer` endpoint with the `merge=true` parameter, because the transfer endpoint offers greater customization by invoking a hook, allowing for adjustments if the default implementation does not process the merge as expected.
+         
+         Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
          
          The following information is merged:
          - custom attributes on the basket and on all copied records
@@ -7653,7 +7727,9 @@ declare namespace ShopperBasketsApiTypes {
             };
         }>): Promise<Basket>;
         /**
-         * Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
+         * ( DEPRECATED ) Instead of using this endpoint, we recommend using the `/baskets/actions/transfer` endpoint with the `merge=true` parameter, because the transfer endpoint offers greater customization by invoking a hook, allowing for adjustments if the default implementation does not process the merge as expected.
+         
+         Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
          
          The following information is merged:
          - custom attributes on the basket and on all copied records
@@ -8060,12 +8136,16 @@ declare namespace ShopperBasketsApiTypes {
         /**
          * Transfer the previous shopper's basket to the current shopper by updating the basket's owner. No other values change. You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token.
          
-         A success response contains the transferred basket.
+         This endpoint provides different methods for handling the scenario in which both a previous guest shopper and the current registered shopper have an active basket attached, and utilizes the `merge` parameter as follows:
+         - `true` (recommended): Triggers a merge hook for graceful handling and prevents 409 status returns. For more information, refer to the `merge` parameter documentation.
+         - `false`: Either overrides the basket of the current registered shopper or returns a 409 response, and allows you to choose between the options explained below.
          
-         If the current shopper has an active basket, and the `overrideExisting` request parameter is `false`, then the transfer request returns a BasketTransferException (HTTP status 409). You can proceed with one of these options:
+         If you call the endpoint with `merge=false` and the current shopper has an active basket, you have two options using the `overrideExisting` parameter. Setting it to `true` deletes the registered user's basket, while setting it to `false` returns a `BasketTransferException` (HTTP status 409), after which you can choose how to proceed:
          - Keep the current shopper's active basket.
-         - Merge the previous and current shoppers' baskets by calling the `baskets/merge` endpoint.
-         - Force the transfer by calling the `baskets/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+         - Merge the previous and current shoppers' baskets by calling the `baskets/actions/merge` endpoint.
+         - Force the transfer by calling the `baskets/actions/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+         
+         A successful response provides the transferred (and merged) current basket. However, if neither the previous nor current shopper had an active basket, a 204 (No Content) response is returned.
          *
          * If you would like to get a raw Response object use the other transferBasket function.
          *
@@ -8076,6 +8156,31 @@ declare namespace ShopperBasketsApiTypes {
          * @param options.parameters.overrideExisting - If the current shopper has no active basket, this parameter is ignored. If the current shopper has an active basket, this parameter controls the behavior:
          - `false` (default): Return a BasketTransferException (HTTP status 409). The basket owner doesn't change.
          - `true`: Force the transfer by deleting the current shopper's active basket and making the current shopper the owner of the previous shopper's basket. Returns the transferred basket (HTTP status 200).
+         * @param options.parameters.merge - This parameter controls the behavior:
+         - `false` (default): Transfers the basket or returns a 409 response with the appropriate message (taking `overrideExisting` in consideration).
+         - `true`: (recommended): Executes the dw.order.mergeBasket hook if at least one basket exists.
+         
+         The hook dw.order.mergeBasket default implementation merges a source basket into the current basket. This behavior can be customized, as shown
+         in this [sample implementation](https://gist.github.com/sf-thomas-loesche/3446c7d71a97e559bf1caee96ae56d9f).
+         
+         There are four possible use cases:
+         
+         a) Guest basket and registered basket exist
+         The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+         dw.order.mergeBasket is called with the source basket (former registered shopper basket) and the transferred current basket (former guest basket).
+         
+         b) Guest basket exists but no registered basket exists
+         The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+         dw.order.mergeBasket is called without the source basket (null passed to the hook) and the transferred current basket (former guest basket).
+         
+         c) No guest basket exists but a registered basket exists
+         The registered basket is retained. The hook dw.order.mergeBasket is called with the retained current basket but without the source basket (null
+         passed to the hook).
+         
+         d) Neither basket exists
+         The hook dw.order.mergeBasket is not called.
+         
+         The API returns the current basket (after executing dw.order.mergeBasket).
          * @param options.parameters.locale - A descriptor for a geographical region by both a language and country code. By combining these two, regional differences in a language can be addressed, such as with the request header parameter `Accept-Language` following [RFC 2616](https://tools.ietf.org/html/rfc2616) & [RFC 1766](https://tools.ietf.org/html/rfc1766). This can also just refer to a language code, also RFC 2616/1766 compliant, as a default if there is no specific match for a country. Finally, can also be used to define default behavior if there is no locale specified.
          * @param options.headers - An object literal of key value pairs of the headers to be sent with this request.
          *
@@ -8086,6 +8191,7 @@ declare namespace ShopperBasketsApiTypes {
                 siteId: string;
                 organizationId: string;
                 overrideExisting?: boolean;
+                merge?: boolean;
                 locale?: LocaleCode$0;
             } & QueryParameters, ConfigParameters>;
             headers?: {
@@ -8095,12 +8201,16 @@ declare namespace ShopperBasketsApiTypes {
         /**
          * Transfer the previous shopper's basket to the current shopper by updating the basket's owner. No other values change. You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token.
          
-         A success response contains the transferred basket.
+         This endpoint provides different methods for handling the scenario in which both a previous guest shopper and the current registered shopper have an active basket attached, and utilizes the `merge` parameter as follows:
+         - `true` (recommended): Triggers a merge hook for graceful handling and prevents 409 status returns. For more information, refer to the `merge` parameter documentation.
+         - `false`: Either overrides the basket of the current registered shopper or returns a 409 response, and allows you to choose between the options explained below.
          
-         If the current shopper has an active basket, and the `overrideExisting` request parameter is `false`, then the transfer request returns a BasketTransferException (HTTP status 409). You can proceed with one of these options:
+         If you call the endpoint with `merge=false` and the current shopper has an active basket, you have two options using the `overrideExisting` parameter. Setting it to `true` deletes the registered user's basket, while setting it to `false` returns a `BasketTransferException` (HTTP status 409), after which you can choose how to proceed:
          - Keep the current shopper's active basket.
-         - Merge the previous and current shoppers' baskets by calling the `baskets/merge` endpoint.
-         - Force the transfer by calling the `baskets/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+         - Merge the previous and current shoppers' baskets by calling the `baskets/actions/merge` endpoint.
+         - Force the transfer by calling the `baskets/actions/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+         
+         A successful response provides the transferred (and merged) current basket. However, if neither the previous nor current shopper had an active basket, a 204 (No Content) response is returned.
          *
          * @param options - An object containing the options for this method.
          * @param options.parameters - An object containing the parameters for this method.
@@ -8109,6 +8219,31 @@ declare namespace ShopperBasketsApiTypes {
          * @param options.parameters.overrideExisting - If the current shopper has no active basket, this parameter is ignored. If the current shopper has an active basket, this parameter controls the behavior:
          - `false` (default): Return a BasketTransferException (HTTP status 409). The basket owner doesn't change.
          - `true`: Force the transfer by deleting the current shopper's active basket and making the current shopper the owner of the previous shopper's basket. Returns the transferred basket (HTTP status 200).
+         * @param options.parameters.merge - This parameter controls the behavior:
+         - `false` (default): Transfers the basket or returns a 409 response with the appropriate message (taking `overrideExisting` in consideration).
+         - `true`: (recommended): Executes the dw.order.mergeBasket hook if at least one basket exists.
+         
+         The hook dw.order.mergeBasket default implementation merges a source basket into the current basket. This behavior can be customized, as shown
+         in this [sample implementation](https://gist.github.com/sf-thomas-loesche/3446c7d71a97e559bf1caee96ae56d9f).
+         
+         There are four possible use cases:
+         
+         a) Guest basket and registered basket exist
+         The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+         dw.order.mergeBasket is called with the source basket (former registered shopper basket) and the transferred current basket (former guest basket).
+         
+         b) Guest basket exists but no registered basket exists
+         The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+         dw.order.mergeBasket is called without the source basket (null passed to the hook) and the transferred current basket (former guest basket).
+         
+         c) No guest basket exists but a registered basket exists
+         The registered basket is retained. The hook dw.order.mergeBasket is called with the retained current basket but without the source basket (null
+         passed to the hook).
+         
+         d) Neither basket exists
+         The hook dw.order.mergeBasket is not called.
+         
+         The API returns the current basket (after executing dw.order.mergeBasket).
          * @param options.parameters.locale - A descriptor for a geographical region by both a language and country code. By combining these two, regional differences in a language can be addressed, such as with the request header parameter `Accept-Language` following [RFC 2616](https://tools.ietf.org/html/rfc2616) & [RFC 1766](https://tools.ietf.org/html/rfc1766). This can also just refer to a language code, also RFC 2616/1766 compliant, as a default if there is no specific match for a country. Finally, can also be used to define default behavior if there is no locale specified.
          * @param options.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.
@@ -8120,6 +8255,7 @@ declare namespace ShopperBasketsApiTypes {
                 siteId: string;
                 organizationId: string;
                 overrideExisting?: boolean;
+                merge?: boolean;
                 locale?: LocaleCode$0;
             } & QueryParameters, ConfigParameters>;
             headers?: {
@@ -11541,6 +11677,7 @@ type removeShipmentFromBasketPathParameters$0 = {
 type transferBasketQueryParameters$0 = {
     siteId: string;
     overrideExisting?: boolean;
+    merge?: boolean;
     locale?: LocaleCode$1;
 };
 type transferBasketPathParameters$0 = {
@@ -11681,7 +11818,9 @@ type ShopperBasketsParameters$0 = ShopperBasketsPathParameters$0 & BaseUriParame
  * [Shopper Baskets](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-baskets:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-baskets-v2/shopper-baskets-oas-v2-public.yaml)
+ 
+ # API Overview
  
  Shopper Baskets V2 provides all Shopper Basket V1 functionality and adds support for temporary baskets.
  Temporary baskets can perform calculations to generate totals, line items, promotions, and item availability without affecting the shopper’s storefront cart, and you can use those calculations for temporary basket checkout. You can also use a temporary basket for an immediate order request.
@@ -12129,6 +12268,7 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
             "siteId",
             "organizationId",
             "overrideExisting",
+            "merge",
             "locale"
         ];
         readonly transferBasketRequired: readonly [
@@ -13244,7 +13384,9 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
         };
     }>, rawResponse?: T): Promise<T extends true ? Response : Taxes$0>;
     /**
-     * Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
+     * ( DEPRECATED ) Instead of using this endpoint, we recommend using the `/baskets/actions/transfer` endpoint with the `merge=true` parameter, because the transfer endpoint offers greater customization by invoking a hook, allowing for adjustments if the default implementation does not process the merge as expected.
+     
+     Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
      
      The following information is merged:
      - custom attributes on the basket and on all copied records
@@ -13316,7 +13458,9 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
         };
     }>): Promise<Basket$0>;
     /**
-     * Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
+     * ( DEPRECATED ) Instead of using this endpoint, we recommend using the `/baskets/actions/transfer` endpoint with the `merge=true` parameter, because the transfer endpoint offers greater customization by invoking a hook, allowing for adjustments if the default implementation does not process the merge as expected.
+     
+     Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
      
      The following information is merged:
      - custom attributes on the basket and on all copied records
@@ -13723,12 +13867,16 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
     /**
      * Transfer the previous shopper's basket to the current shopper by updating the basket's owner. No other values change. You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token.
      
-     A success response contains the transferred basket.
+     This endpoint provides different methods for handling the scenario in which both a previous guest shopper and the current registered shopper have an active basket attached, and utilizes the `merge` parameter as follows:
+     - `true` (recommended): Triggers a merge hook for graceful handling and prevents 409 status returns. For more information, refer to the `merge` parameter documentation.
+     - `false`: Either overrides the basket of the current registered shopper or returns a 409 response, and allows you to choose between the options explained below.
      
-     If the current shopper has an active basket, and the `overrideExisting` request parameter is `false`, then the transfer request returns a BasketTransferException (HTTP status 409). You can proceed with one of these options:
+     If you call the endpoint with `merge=false` and the current shopper has an active basket, you have two options using the `overrideExisting` parameter. Setting it to `true` deletes the registered user's basket, while setting it to `false` returns a `BasketTransferException` (HTTP status 409), after which you can choose how to proceed:
      - Keep the current shopper's active basket.
-     - Merge the previous and current shoppers' baskets by calling the `baskets/merge` endpoint.
-     - Force the transfer by calling the `baskets/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+     - Merge the previous and current shoppers' baskets by calling the `baskets/actions/merge` endpoint.
+     - Force the transfer by calling the `baskets/actions/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+     
+     A successful response provides the transferred (and merged) current basket. However, if neither the previous nor current shopper had an active basket, a 204 (No Content) response is returned.
      *
      * If you would like to get a raw Response object use the other transferBasket function.
      *
@@ -13739,6 +13887,31 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
      * @param options.parameters.overrideExisting - If the current shopper has no active basket, this parameter is ignored. If the current shopper has an active basket, this parameter controls the behavior:
      - `false` (default): Return a BasketTransferException (HTTP status 409). The basket owner doesn't change.
      - `true`: Force the transfer by deleting the current shopper's active basket and making the current shopper the owner of the previous shopper's basket. Returns the transferred basket (HTTP status 200).
+     * @param options.parameters.merge - This parameter controls the behavior:
+     - `false` (default): Transfers the basket or returns a 409 response with the appropriate message (taking `overrideExisting` in consideration).
+     - `true`: (recommended): Executes the dw.order.mergeBasket hook if at least one basket exists.
+     
+     The hook dw.order.mergeBasket default implementation merges a source basket into the current basket. This behavior can be customized, as shown
+     in this [sample implementation](https://gist.github.com/sf-thomas-loesche/3446c7d71a97e559bf1caee96ae56d9f).
+     
+     There are four possible use cases:
+     
+     a) Guest basket and registered basket exist
+     The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+     dw.order.mergeBasket is called with the source basket (former registered shopper basket) and the transferred current basket (former guest basket).
+     
+     b) Guest basket exists but no registered basket exists
+     The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+     dw.order.mergeBasket is called without the source basket (null passed to the hook) and the transferred current basket (former guest basket).
+     
+     c) No guest basket exists but a registered basket exists
+     The registered basket is retained. The hook dw.order.mergeBasket is called with the retained current basket but without the source basket (null
+     passed to the hook).
+     
+     d) Neither basket exists
+     The hook dw.order.mergeBasket is not called.
+     
+     The API returns the current basket (after executing dw.order.mergeBasket).
      * @param options.parameters.locale - A descriptor for a geographical region by both a language and country code. By combining these two, regional differences in a language can be addressed, such as with the request header parameter `Accept-Language` following [RFC 2616](https://tools.ietf.org/html/rfc2616) & [RFC 1766](https://tools.ietf.org/html/rfc1766). This can also just refer to a language code, also RFC 2616/1766 compliant, as a default if there is no specific match for a country. Finally, can also be used to define default behavior if there is no locale specified.
      * @param options.headers - An object literal of key value pairs of the headers to be sent with this request.
      *
@@ -13749,6 +13922,7 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
             siteId: string;
             organizationId: string;
             overrideExisting?: boolean;
+            merge?: boolean;
             locale?: LocaleCode$1;
         } & QueryParameters, ConfigParameters>;
         headers?: {
@@ -13758,12 +13932,16 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
     /**
      * Transfer the previous shopper's basket to the current shopper by updating the basket's owner. No other values change. You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token.
      
-     A success response contains the transferred basket.
+     This endpoint provides different methods for handling the scenario in which both a previous guest shopper and the current registered shopper have an active basket attached, and utilizes the `merge` parameter as follows:
+     - `true` (recommended): Triggers a merge hook for graceful handling and prevents 409 status returns. For more information, refer to the `merge` parameter documentation.
+     - `false`: Either overrides the basket of the current registered shopper or returns a 409 response, and allows you to choose between the options explained below.
      
-     If the current shopper has an active basket, and the `overrideExisting` request parameter is `false`, then the transfer request returns a BasketTransferException (HTTP status 409). You can proceed with one of these options:
+     If you call the endpoint with `merge=false` and the current shopper has an active basket, you have two options using the `overrideExisting` parameter. Setting it to `true` deletes the registered user's basket, while setting it to `false` returns a `BasketTransferException` (HTTP status 409), after which you can choose how to proceed:
      - Keep the current shopper's active basket.
-     - Merge the previous and current shoppers' baskets by calling the `baskets/merge` endpoint.
-     - Force the transfer by calling the `baskets/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+     - Merge the previous and current shoppers' baskets by calling the `baskets/actions/merge` endpoint.
+     - Force the transfer by calling the `baskets/actions/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+     
+     A successful response provides the transferred (and merged) current basket. However, if neither the previous nor current shopper had an active basket, a 204 (No Content) response is returned.
      *
      * @param options - An object containing the options for this method.
      * @param options.parameters - An object containing the parameters for this method.
@@ -13772,6 +13950,31 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
      * @param options.parameters.overrideExisting - If the current shopper has no active basket, this parameter is ignored. If the current shopper has an active basket, this parameter controls the behavior:
      - `false` (default): Return a BasketTransferException (HTTP status 409). The basket owner doesn't change.
      - `true`: Force the transfer by deleting the current shopper's active basket and making the current shopper the owner of the previous shopper's basket. Returns the transferred basket (HTTP status 200).
+     * @param options.parameters.merge - This parameter controls the behavior:
+     - `false` (default): Transfers the basket or returns a 409 response with the appropriate message (taking `overrideExisting` in consideration).
+     - `true`: (recommended): Executes the dw.order.mergeBasket hook if at least one basket exists.
+     
+     The hook dw.order.mergeBasket default implementation merges a source basket into the current basket. This behavior can be customized, as shown
+     in this [sample implementation](https://gist.github.com/sf-thomas-loesche/3446c7d71a97e559bf1caee96ae56d9f).
+     
+     There are four possible use cases:
+     
+     a) Guest basket and registered basket exist
+     The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+     dw.order.mergeBasket is called with the source basket (former registered shopper basket) and the transferred current basket (former guest basket).
+     
+     b) Guest basket exists but no registered basket exists
+     The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+     dw.order.mergeBasket is called without the source basket (null passed to the hook) and the transferred current basket (former guest basket).
+     
+     c) No guest basket exists but a registered basket exists
+     The registered basket is retained. The hook dw.order.mergeBasket is called with the retained current basket but without the source basket (null
+     passed to the hook).
+     
+     d) Neither basket exists
+     The hook dw.order.mergeBasket is not called.
+     
+     The API returns the current basket (after executing dw.order.mergeBasket).
      * @param options.parameters.locale - A descriptor for a geographical region by both a language and country code. By combining these two, regional differences in a language can be addressed, such as with the request header parameter `Accept-Language` following [RFC 2616](https://tools.ietf.org/html/rfc2616) & [RFC 1766](https://tools.ietf.org/html/rfc1766). This can also just refer to a language code, also RFC 2616/1766 compliant, as a default if there is no specific match for a country. Finally, can also be used to define default behavior if there is no locale specified.
      * @param options.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.
@@ -13783,6 +13986,7 @@ declare class ShopperBasketsV2<ConfigParameters extends ShopperBasketsParameters
             siteId: string;
             organizationId: string;
             overrideExisting?: boolean;
+            merge?: boolean;
             locale?: LocaleCode$1;
         } & QueryParameters, ConfigParameters>;
         headers?: {
@@ -16141,6 +16345,7 @@ declare namespace ShopperBasketsV2ApiTypes {
     type transferBasketQueryParameters = {
         siteId: string;
         overrideExisting?: boolean;
+        merge?: boolean;
         locale?: LocaleCode$0;
     };
     type transferBasketPathParameters = {
@@ -16281,7 +16486,9 @@ declare namespace ShopperBasketsV2ApiTypes {
      * [Shopper Baskets](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-baskets:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-baskets-v2/shopper-baskets-oas-v2-public.yaml)
+     
+     # API Overview
      
      Shopper Baskets V2 provides all Shopper Basket V1 functionality and adds support for temporary baskets.
      Temporary baskets can perform calculations to generate totals, line items, promotions, and item availability without affecting the shopper’s storefront cart, and you can use those calculations for temporary basket checkout. You can also use a temporary basket for an immediate order request.
@@ -16729,6 +16936,7 @@ declare namespace ShopperBasketsV2ApiTypes {
                 "siteId",
                 "organizationId",
                 "overrideExisting",
+                "merge",
                 "locale"
             ];
             readonly transferBasketRequired: readonly [
@@ -17844,7 +18052,9 @@ declare namespace ShopperBasketsV2ApiTypes {
             };
         }>, rawResponse?: T): Promise<T extends true ? Response : Taxes>;
         /**
-         * Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
+         * ( DEPRECATED ) Instead of using this endpoint, we recommend using the `/baskets/actions/transfer` endpoint with the `merge=true` parameter, because the transfer endpoint offers greater customization by invoking a hook, allowing for adjustments if the default implementation does not process the merge as expected.
+         
+         Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
          
          The following information is merged:
          - custom attributes on the basket and on all copied records
@@ -17916,7 +18126,9 @@ declare namespace ShopperBasketsV2ApiTypes {
             };
         }>): Promise<Basket>;
         /**
-         * Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
+         * ( DEPRECATED ) Instead of using this endpoint, we recommend using the `/baskets/actions/transfer` endpoint with the `merge=true` parameter, because the transfer endpoint offers greater customization by invoking a hook, allowing for adjustments if the default implementation does not process the merge as expected.
+         
+         Merge data from the previous shopper's basket into the current shopper's active basket and delete the previous shopper's basket. This endpoint doesn't merge Personally Identifiable Information (PII). You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token. After the merge, all basket amounts are recalculated and totaled, including lookups for prices, taxes, shipping, and promotions, unless hooks are enabled.
          
          The following information is merged:
          - custom attributes on the basket and on all copied records
@@ -18323,12 +18535,16 @@ declare namespace ShopperBasketsV2ApiTypes {
         /**
          * Transfer the previous shopper's basket to the current shopper by updating the basket's owner. No other values change. You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token.
          
-         A success response contains the transferred basket.
+         This endpoint provides different methods for handling the scenario in which both a previous guest shopper and the current registered shopper have an active basket attached, and utilizes the `merge` parameter as follows:
+         - `true` (recommended): Triggers a merge hook for graceful handling and prevents 409 status returns. For more information, refer to the `merge` parameter documentation.
+         - `false`: Either overrides the basket of the current registered shopper or returns a 409 response, and allows you to choose between the options explained below.
          
-         If the current shopper has an active basket, and the `overrideExisting` request parameter is `false`, then the transfer request returns a BasketTransferException (HTTP status 409). You can proceed with one of these options:
+         If you call the endpoint with `merge=false` and the current shopper has an active basket, you have two options using the `overrideExisting` parameter. Setting it to `true` deletes the registered user's basket, while setting it to `false` returns a `BasketTransferException` (HTTP status 409), after which you can choose how to proceed:
          - Keep the current shopper's active basket.
-         - Merge the previous and current shoppers' baskets by calling the `baskets/merge` endpoint.
-         - Force the transfer by calling the `baskets/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+         - Merge the previous and current shoppers' baskets by calling the `baskets/actions/merge` endpoint.
+         - Force the transfer by calling the `baskets/actions/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+         
+         A successful response provides the transferred (and merged) current basket. However, if neither the previous nor current shopper had an active basket, a 204 (No Content) response is returned.
          *
          * If you would like to get a raw Response object use the other transferBasket function.
          *
@@ -18339,6 +18555,31 @@ declare namespace ShopperBasketsV2ApiTypes {
          * @param options.parameters.overrideExisting - If the current shopper has no active basket, this parameter is ignored. If the current shopper has an active basket, this parameter controls the behavior:
          - `false` (default): Return a BasketTransferException (HTTP status 409). The basket owner doesn't change.
          - `true`: Force the transfer by deleting the current shopper's active basket and making the current shopper the owner of the previous shopper's basket. Returns the transferred basket (HTTP status 200).
+         * @param options.parameters.merge - This parameter controls the behavior:
+         - `false` (default): Transfers the basket or returns a 409 response with the appropriate message (taking `overrideExisting` in consideration).
+         - `true`: (recommended): Executes the dw.order.mergeBasket hook if at least one basket exists.
+         
+         The hook dw.order.mergeBasket default implementation merges a source basket into the current basket. This behavior can be customized, as shown
+         in this [sample implementation](https://gist.github.com/sf-thomas-loesche/3446c7d71a97e559bf1caee96ae56d9f).
+         
+         There are four possible use cases:
+         
+         a) Guest basket and registered basket exist
+         The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+         dw.order.mergeBasket is called with the source basket (former registered shopper basket) and the transferred current basket (former guest basket).
+         
+         b) Guest basket exists but no registered basket exists
+         The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+         dw.order.mergeBasket is called without the source basket (null passed to the hook) and the transferred current basket (former guest basket).
+         
+         c) No guest basket exists but a registered basket exists
+         The registered basket is retained. The hook dw.order.mergeBasket is called with the retained current basket but without the source basket (null
+         passed to the hook).
+         
+         d) Neither basket exists
+         The hook dw.order.mergeBasket is not called.
+         
+         The API returns the current basket (after executing dw.order.mergeBasket).
          * @param options.parameters.locale - A descriptor for a geographical region by both a language and country code. By combining these two, regional differences in a language can be addressed, such as with the request header parameter `Accept-Language` following [RFC 2616](https://tools.ietf.org/html/rfc2616) & [RFC 1766](https://tools.ietf.org/html/rfc1766). This can also just refer to a language code, also RFC 2616/1766 compliant, as a default if there is no specific match for a country. Finally, can also be used to define default behavior if there is no locale specified.
          * @param options.headers - An object literal of key value pairs of the headers to be sent with this request.
          *
@@ -18349,6 +18590,7 @@ declare namespace ShopperBasketsV2ApiTypes {
                 siteId: string;
                 organizationId: string;
                 overrideExisting?: boolean;
+                merge?: boolean;
                 locale?: LocaleCode$0;
             } & QueryParameters, ConfigParameters>;
             headers?: {
@@ -18358,12 +18600,16 @@ declare namespace ShopperBasketsV2ApiTypes {
         /**
          * Transfer the previous shopper's basket to the current shopper by updating the basket's owner. No other values change. You must obtain the shopper authorization token via SLAS and you must provide the ‘guest usid‘ in both the ‘/oauth2/login‘ and ‘/oauth2/token‘ calls while fetching the registered user JWT token.
          
-         A success response contains the transferred basket.
+         This endpoint provides different methods for handling the scenario in which both a previous guest shopper and the current registered shopper have an active basket attached, and utilizes the `merge` parameter as follows:
+         - `true` (recommended): Triggers a merge hook for graceful handling and prevents 409 status returns. For more information, refer to the `merge` parameter documentation.
+         - `false`: Either overrides the basket of the current registered shopper or returns a 409 response, and allows you to choose between the options explained below.
          
-         If the current shopper has an active basket, and the `overrideExisting` request parameter is `false`, then the transfer request returns a BasketTransferException (HTTP status 409). You can proceed with one of these options:
+         If you call the endpoint with `merge=false` and the current shopper has an active basket, you have two options using the `overrideExisting` parameter. Setting it to `true` deletes the registered user's basket, while setting it to `false` returns a `BasketTransferException` (HTTP status 409), after which you can choose how to proceed:
          - Keep the current shopper's active basket.
-         - Merge the previous and current shoppers' baskets by calling the `baskets/merge` endpoint.
-         - Force the transfer by calling the `baskets/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+         - Merge the previous and current shoppers' baskets by calling the `baskets/actions/merge` endpoint.
+         - Force the transfer by calling the `baskets/actions/transfer` endpoint again, with the parameter `overrideExisting=true`. Forcing the transfer deletes the current shopper's active basket.
+         
+         A successful response provides the transferred (and merged) current basket. However, if neither the previous nor current shopper had an active basket, a 204 (No Content) response is returned.
          *
          * @param options - An object containing the options for this method.
          * @param options.parameters - An object containing the parameters for this method.
@@ -18372,6 +18618,31 @@ declare namespace ShopperBasketsV2ApiTypes {
          * @param options.parameters.overrideExisting - If the current shopper has no active basket, this parameter is ignored. If the current shopper has an active basket, this parameter controls the behavior:
          - `false` (default): Return a BasketTransferException (HTTP status 409). The basket owner doesn't change.
          - `true`: Force the transfer by deleting the current shopper's active basket and making the current shopper the owner of the previous shopper's basket. Returns the transferred basket (HTTP status 200).
+         * @param options.parameters.merge - This parameter controls the behavior:
+         - `false` (default): Transfers the basket or returns a 409 response with the appropriate message (taking `overrideExisting` in consideration).
+         - `true`: (recommended): Executes the dw.order.mergeBasket hook if at least one basket exists.
+         
+         The hook dw.order.mergeBasket default implementation merges a source basket into the current basket. This behavior can be customized, as shown
+         in this [sample implementation](https://gist.github.com/sf-thomas-loesche/3446c7d71a97e559bf1caee96ae56d9f).
+         
+         There are four possible use cases:
+         
+         a) Guest basket and registered basket exist
+         The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+         dw.order.mergeBasket is called with the source basket (former registered shopper basket) and the transferred current basket (former guest basket).
+         
+         b) Guest basket exists but no registered basket exists
+         The guest basket becomes the current basket for the registered shopper by updating the basket's owner (no personal data is removed). The hook
+         dw.order.mergeBasket is called without the source basket (null passed to the hook) and the transferred current basket (former guest basket).
+         
+         c) No guest basket exists but a registered basket exists
+         The registered basket is retained. The hook dw.order.mergeBasket is called with the retained current basket but without the source basket (null
+         passed to the hook).
+         
+         d) Neither basket exists
+         The hook dw.order.mergeBasket is not called.
+         
+         The API returns the current basket (after executing dw.order.mergeBasket).
          * @param options.parameters.locale - A descriptor for a geographical region by both a language and country code. By combining these two, regional differences in a language can be addressed, such as with the request header parameter `Accept-Language` following [RFC 2616](https://tools.ietf.org/html/rfc2616) & [RFC 1766](https://tools.ietf.org/html/rfc1766). This can also just refer to a language code, also RFC 2616/1766 compliant, as a default if there is no specific match for a country. Finally, can also be used to define default behavior if there is no locale specified.
          * @param options.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.
@@ -18383,6 +18654,7 @@ declare namespace ShopperBasketsV2ApiTypes {
                 siteId: string;
                 organizationId: string;
                 overrideExisting?: boolean;
+                merge?: boolean;
                 locale?: LocaleCode$0;
             } & QueryParameters, ConfigParameters>;
             headers?: {
@@ -20570,6 +20842,824 @@ declare namespace ShopperBasketsV2Types {
     type TaxItems = ShopperBasketsV2ModelTypes.TaxItems;
     type Taxes = ShopperBasketsV2ModelTypes.Taxes;
 }
+/**
+ * @type ModelConfiguration: Configuration object
+ *
+ * @property id: identifier
+ * - **Max Length:** 255
+ *
+ * @property value: value for identifier
+ * - **Max Length:** 255
+ *
+ * @property configurationType: type of configuration value
+ * - **Max Length:** 255
+ *
+ */
+type ModelConfiguration = {
+    id: string;
+    value: any | null;
+    configurationType?: string;
+} & {
+    [key: string]: any;
+};
+/**
+ * @type SiteConfiguration: Site Configuration object
+ *
+ * @property configurations: List configurations for the instance and site
+ *
+ */
+type SiteConfiguration = {
+    configurations: Array<ModelConfiguration>;
+} & {
+    [key: string]: any;
+};
+type getConfigurationsQueryParameters = {
+    siteId: string;
+};
+type getConfigurationsPathParameters = {
+    organizationId: string;
+};
+/**
+ * All path parameters that are used by at least one ShopperConfigurations method.
+ */
+type ShopperConfigurationsPathParameters = Partial<getConfigurationsPathParameters & {}>;
+/**
+ * All query parameters that are used by at least one ShopperConfigurations method.
+ */
+type ShopperConfigurationsQueryParameters = Partial<getConfigurationsQueryParameters & {}>;
+/**
+ * All parameters that are used by ShopperConfigurations.
+ */
+type ShopperConfigurationsParameters = ShopperConfigurationsPathParameters & BaseUriParameters & ShopperConfigurationsQueryParameters;
+/**
+ * [Shopper Configurations](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-configurations:Summary)
+ * ==================================
+ *
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-configurations/shopper-configurations-oas-v1-public.yaml)
+ 
+ # API Overview
+ In commerce, there is a need to provide information to the shopper facing application to allow for making decisions on execution.  This is highly cache-able data that rarely changes.
+ 
+ It encompasses toggles, preferences, and configuration that allow the application to be reactive to changes performed by the merchant, admin, or support engineer.
+ 
+ ## Use Cases
+ 1. What is the site name and site status (online / offline)
+ 2. What is the default and supported currencies
+ 3. What is the default and supported locales
+ 4. Which features are enabled
+ 
+ # Example
+ 
+ ```
+ {
+ "configurations":[
+ {
+ "configurationType":"siteConfiguration",
+ "id":"id",
+ "value":"TestWapi"
+ },
+ {
+ "configurationType":"siteConfiguration",
+ "id":"name",
+ "value":"Test WAPI"
+ },
+ {
+ "configurationType":"siteConfiguration",
+ "id":"status",
+ "value":"online"
+ },
+ {
+ "configurationType":"siteConfiguration",
+ "id":"timezone",
+ "value":"Etc/UTC"
+ },
+ {
+ "configurationType":"siteConfiguration",
+ "id":"timezoneOffset",
+ "value":0
+ },
+ {
+ "configurationType":"siteConfiguration",
+ "id":"defaultCurrency",
+ "value":"USD"
+ },
+ {
+ "configurationType":"siteConfiguration",
+ "id":"allowedCurrencies",
+ "value":[
+ "USD",
+ "EUR"
+ ]
+ },
+ {
+ "configurationType":"siteConfiguration",
+ "id":"defaultLocale",
+ "value":"default"
+ },
+ {
+ "configurationType":"siteConfiguration",
+ "id":"allowedLocales",
+ "value":[
+ {
+ "country":"",
+ "default":true,
+ "displayCountry":"",
+ "displayLanguage":"",
+ "displayName":"default",
+ "id":"default",
+ "iso3Country":"",
+ "iso3Language":"",
+ "language":"",
+ "name":"default"
+ },
+ {
+ "country":"DE",
+ "default":false,
+ "displayCountry":"Deutschland",
+ "displayLanguage":"Deutsch",
+ "displayName":"Deutsch (Deutschland)",
+ "id":"de-DE",
+ "iso3Country":"DEU",
+ "iso3Language":"deu",
+ "language":"de",
+ "name":"German (Germany)"
+ },
+ {
+ "country":"",
+ "default":false,
+ "displayCountry":"",
+ "displayLanguage":"Deutsch",
+ "displayName":"Deutsch",
+ "id":"de",
+ "iso3Country":"",
+ "iso3Language":"deu",
+ "language":"de",
+ "name":"German"
+ },
+ {
+ "country":"US",
+ "default":false,
+ "displayCountry":"United States",
+ "displayLanguage":"English",
+ "displayName":"English (United States)",
+ "id":"en-US",
+ "iso3Country":"USA",
+ "iso3Language":"eng",
+ "language":"en",
+ "name":"English (United States)"
+ },
+ {
+ "country":"CA",
+ "default":false,
+ "displayCountry":"Canada",
+ "displayLanguage":"English",
+ "displayName":"English (Canada)",
+ "id":"en-CA",
+ "iso3Country":"CAN",
+ "iso3Language":"eng",
+ "language":"en",
+ "name":"English (Canada)"
+ },
+ {
+ "country":"",
+ "default":false,
+ "displayCountry":"",
+ "displayLanguage":"English",
+ "displayName":"English",
+ "id":"en",
+ "iso3Country":"",
+ "iso3Language":"eng",
+ "language":"en",
+ "name":"English"
+ },
+ {
+ "country":"",
+ "default":false,
+ "displayCountry":"",
+ "displayLanguage":"español",
+ "displayName":"español",
+ "id":"es",
+ "iso3Country":"",
+ "iso3Language":"spa",
+ "language":"es",
+ "name":"Spanish"
+ }
+ ]
+ },
+ {
+ "configurationType":"globalConfiguration",
+ "id":"SalesforcePaymentsAllowed",
+ "value":true
+ },
+ {
+ "configurationType":"globalConfiguration",
+ "id":"gcp",
+ "value":"test-gcp-key"
+ }
+ ]
+ }
+ ```
+ 
+ ### Caching
+ 
+ Caching capabilities are available for the Shopper Configuration APIs. For details, see [Server-Side Web-Tier Caching.](https://developer.salesforce.com/docs/commerce/commerce-api/guide/server-side-web-tier-caching.html)*<br />
+ *
+ * Simple example:
+ *
+ * ```typescript
+ *   import { ShopperConfigurations } from "commerce-sdk-isomorphic";
+ *
+ *   const clientConfig = {
+ *     parameters: {
+ *       clientId: "XXXXXX",
+ *       organizationId: "XXXX",
+ *       shortCode: "XXX",
+ *       siteId: "XX"
+ *     }
+ *   };
+ *   const shopperConfigurationsClient = new ShopperConfigurations(clientConfig);
+ * ```
+ *
+ * <span style="font-size:.7em; display:block; text-align: right">
+ * API Version: 0.0.33<br />
+ * Last Updated: <br />
+ * </span>
+ *
+ *
+ */
+declare class ShopperConfigurations<ConfigParameters extends ShopperConfigurationsParameters & Record<string, unknown>> {
+    // baseUri is not required on ClientConfig, but we know that we provide one in the class constructor
+    clientConfig: ClientConfig<ConfigParameters> & {
+        baseUri: string;
+    };
+    static readonly defaultBaseUri = "https://{shortCode}.api.commercecloud.salesforce.com/configuration/shopper-configurations/v1";
+    static readonly apiPaths: {
+        getConfigurations: string;
+    };
+    constructor(config: ClientConfigInit<ConfigParameters>);
+    static readonly paramKeys: {
+        readonly getConfigurations: readonly [
+            "organizationId",
+            "siteId"
+        ];
+        readonly getConfigurationsRequired: readonly [
+            "organizationId",
+            "siteId"
+        ];
+    };
+    /**
+     * Retrieves configurations for the specified organization and site.
+     *
+     * If you would like to get a raw Response object use the other getConfigurations function.
+     *
+     * @param options - An object containing the options for this method.
+     * @param options.parameters - An object containing the parameters for this method.
+     * @param options.parameters.organizationId - An identifier for the organization the request is being made by
+     * @param options.parameters.siteId - The identifier of the site that a request is being made in the context of. Attributes might have site specific values, and some objects may only be assigned to specific sites.
+     * @param options.headers - An object literal of key value pairs of the headers to be sent with this request.
+     *
+     * @returns A promise of type SiteConfiguration.
+     */
+    getConfigurations(options?: RequireParametersUnlessAllAreOptional<{
+        parameters?: CompositeParameters<{
+            organizationId: string;
+            siteId: string;
+        } & QueryParameters, ConfigParameters>;
+        headers?: {
+            [key: string]: string;
+        };
+    }>): Promise<SiteConfiguration>;
+    /**
+     * Retrieves configurations for the specified organization and site.
+     *
+     * @param options - An object containing the options for this method.
+     * @param options.parameters - An object containing the parameters for this method.
+     * @param options.parameters.organizationId - An identifier for the organization the request is being made by
+     * @param options.parameters.siteId - The identifier of the site that a request is being made in the context of. Attributes might have site specific values, and some objects may only be assigned to specific sites.
+     * @param options.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.
+     *
+     * @returns A promise of type Response if rawResponse is true, a promise of type SiteConfiguration otherwise.
+     */
+    getConfigurations<T extends boolean>(options?: RequireParametersUnlessAllAreOptional<{
+        parameters?: CompositeParameters<{
+            organizationId: string;
+            siteId: string;
+        } & QueryParameters, ConfigParameters>;
+        headers?: {
+            [key: string]: string;
+        };
+    }>, rawResponse?: T): Promise<T extends true ? Response : SiteConfiguration>;
+}
+declare namespace ShopperConfigurationsApiTypes {
+    /*
+    * Copyright (c) 2023, Salesforce, Inc.
+    * All rights reserved.
+    * SPDX-License-Identifier: BSD-3-Clause
+    * For full license text, see the LICENSE file in the repo root or https://opensource.org/licenses/BSD-3-Clause
+    */
+    /**
+     * Makes a type easier to read.
+     */
+    type Prettify<T> = NonNullable<{
+        [K in keyof T]: T[K];
+    }>;
+    /**
+     * Generates the types required on a method, based on those provided in the config.
+     */
+    type CompositeParameters<MethodParameters extends Record<string, unknown>, ConfigParameters extends Record<string, unknown>> = Prettify<Omit<MethodParameters, keyof ConfigParameters> & Partial<MethodParameters>>;
+    /**
+     * If an object has a `parameters` property, and the `parameters` object has required properties,
+     * then the `parameters` property on the root object is marked as required.
+     */
+    type RequireParametersUnlessAllAreOptional<T extends {
+        parameters?: Record<string, unknown>;
+    }> = Record<string, never> extends NonNullable<T["parameters"]> ? T : Prettify<T & Required<Pick<T, "parameters">>>;
+    /**
+     * Template parameters used in the base URI of all API endpoints. `version` will default to `"v1"`
+     * if not specified.
+     */
+    interface BaseUriParameters {
+        shortCode: string;
+    }
+    type LocaleCode = {
+        [key: string]: any;
+    };
+    /**
+     * Generic interface for path parameters.
+     */
+    interface PathParameters {
+        [key: string]: string | number | boolean;
+    }
+    /**
+     * Generic interface for query parameters.
+     */
+    interface QueryParameters {
+        [key: string]: string | number | boolean | string[] | number[] | LocaleCode;
+    }
+    /**
+     * Generic interface for all parameter types.
+     */
+    type UrlParameters = PathParameters | QueryParameters;
+    /**
+     * Custom query parameter type with any string prefixed with `c_` as the key and the allowed
+     * types for query parameters for the value.
+     */
+    type CustomQueryParameters = {
+        [key in `c_${string}`]: string | number | boolean | string[] | number[];
+    };
+    /**
+     * Custom body request type with any string prefixed with `c_` as the key and the allowed
+     * types for the value.
+     */
+    type CustomRequestBody = {
+        [key in `c_${string}`]: string | number | boolean | string[] | number[] | {
+            [key: string]: unknown;
+        };
+    };
+    /**
+     * Alias for `RequestInit` from TypeScript's DOM lib, to more clearly differentiate
+     * it from the `RequestInit` provided by node-fetch.
+     */
+    type BrowserRequestInit = RequestInit;
+    /**
+     * Any properties supported in either the browser or node are accepted.
+     * Using the right properties in the right context is left to the user.
+     */
+    type FetchOptions = NodeRequestInit & BrowserRequestInit;
+    /**
+     * Base options that can be passed to the `ClientConfig` class.
+     */
+    interface ClientConfigInit<Params extends BaseUriParameters> {
+        baseUri?: string;
+        proxy?: string;
+        headers?: {
+            [key: string]: string;
+        };
+        parameters: Params;
+        fetchOptions?: FetchOptions;
+        transformRequest?: (data: unknown, headers: {
+            [key: string]: string;
+        }) => Required<FetchOptions>["body"];
+        throwOnBadResponse?: boolean;
+    }
+    type FetchFunction = (input: RequestInfo, init?: FetchOptions | undefined) => Promise<Response>;
+    /**
+     * Configuration parameters common to Commerce SDK clients
+     */
+    class ClientConfig<Params extends BaseUriParameters> implements ClientConfigInit<Params> {
+        baseUri?: string;
+        proxy?: string;
+        headers: {
+            [key: string]: string;
+        };
+        parameters: Params;
+        fetchOptions: FetchOptions;
+        transformRequest: NonNullable<ClientConfigInit<Params>["transformRequest"]>;
+        throwOnBadResponse: boolean;
+        constructor(config: ClientConfigInit<Params>);
+        static readonly defaults: Pick<Required<ClientConfigInit<never>>, "transformRequest">;
+    }
+    /**
+     * @type ErrorResponse:
+     *
+     * @property title: A short, human-readable summary of the problem type.  It will not change from occurrence to occurrence of the  problem, except for purposes of localization
+     * - **Max Length:** 256
+     *
+     * @property type: A URI reference [RFC3986] that identifies the problem type.  This specification encourages that, when dereferenced, it provide human-readable documentation for the problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When this member is not present, its value is assumed to be \"about:blank\". It accepts relative URIs; this means that they must be resolved relative to the document\'s base URI, as per [RFC3986], Section 5.
+     * - **Max Length:** 2048
+     *
+     * @property detail: A human-readable explanation specific to this occurrence of the problem.
+     *
+     * @property instance: A URI reference that identifies the specific occurrence of the problem.  It may or may not yield further information if dereferenced.  It accepts relative URIs; this means that they must be resolved relative to the document\'s base URI, as per [RFC3986], Section 5.
+     * - **Max Length:** 2048
+     *
+     */
+    type ErrorResponse = {
+        title: string;
+        type: string;
+        detail: string;
+        instance?: string;
+    } & {
+        [key: string]: any;
+    };
+    /**
+     * @type ModelConfiguration: Configuration object
+     *
+     * @property id: identifier
+     * - **Max Length:** 255
+     *
+     * @property value: value for identifier
+     * - **Max Length:** 255
+     *
+     * @property configurationType: type of configuration value
+     * - **Max Length:** 255
+     *
+     */
+    type ModelConfiguration = {
+        id: string;
+        value: any | null;
+        configurationType?: string;
+    } & {
+        [key: string]: any;
+    };
+    /**
+     * @type SiteConfiguration: Site Configuration object
+     *
+     * @property configurations: List configurations for the instance and site
+     *
+     */
+    type SiteConfiguration = {
+        configurations: Array<ModelConfiguration>;
+    } & {
+        [key: string]: any;
+    };
+    type getConfigurationsQueryParameters = {
+        siteId: string;
+    };
+    type getConfigurationsPathParameters = {
+        organizationId: string;
+    };
+    /**
+     * All path parameters that are used by at least one ShopperConfigurations method.
+     */
+    type ShopperConfigurationsPathParameters = Partial<getConfigurationsPathParameters & {}>;
+    /**
+     * All query parameters that are used by at least one ShopperConfigurations method.
+     */
+    type ShopperConfigurationsQueryParameters = Partial<getConfigurationsQueryParameters & {}>;
+    /**
+     * All parameters that are used by ShopperConfigurations.
+     */
+    type ShopperConfigurationsParameters = ShopperConfigurationsPathParameters & BaseUriParameters & ShopperConfigurationsQueryParameters;
+    /**
+     * [Shopper Configurations](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-configurations:Summary)
+     * ==================================
+     *
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-configurations/shopper-configurations-oas-v1-public.yaml)
+     
+     # API Overview
+     In commerce, there is a need to provide information to the shopper facing application to allow for making decisions on execution.  This is highly cache-able data that rarely changes.
+     
+     It encompasses toggles, preferences, and configuration that allow the application to be reactive to changes performed by the merchant, admin, or support engineer.
+     
+     ## Use Cases
+     1. What is the site name and site status (online / offline)
+     2. What is the default and supported currencies
+     3. What is the default and supported locales
+     4. Which features are enabled
+     
+     # Example
+     
+     ```
+     {
+     "configurations":[
+     {
+     "configurationType":"siteConfiguration",
+     "id":"id",
+     "value":"TestWapi"
+     },
+     {
+     "configurationType":"siteConfiguration",
+     "id":"name",
+     "value":"Test WAPI"
+     },
+     {
+     "configurationType":"siteConfiguration",
+     "id":"status",
+     "value":"online"
+     },
+     {
+     "configurationType":"siteConfiguration",
+     "id":"timezone",
+     "value":"Etc/UTC"
+     },
+     {
+     "configurationType":"siteConfiguration",
+     "id":"timezoneOffset",
+     "value":0
+     },
+     {
+     "configurationType":"siteConfiguration",
+     "id":"defaultCurrency",
+     "value":"USD"
+     },
+     {
+     "configurationType":"siteConfiguration",
+     "id":"allowedCurrencies",
+     "value":[
+     "USD",
+     "EUR"
+     ]
+     },
+     {
+     "configurationType":"siteConfiguration",
+     "id":"defaultLocale",
+     "value":"default"
+     },
+     {
+     "configurationType":"siteConfiguration",
+     "id":"allowedLocales",
+     "value":[
+     {
+     "country":"",
+     "default":true,
+     "displayCountry":"",
+     "displayLanguage":"",
+     "displayName":"default",
+     "id":"default",
+     "iso3Country":"",
+     "iso3Language":"",
+     "language":"",
+     "name":"default"
+     },
+     {
+     "country":"DE",
+     "default":false,
+     "displayCountry":"Deutschland",
+     "displayLanguage":"Deutsch",
+     "displayName":"Deutsch (Deutschland)",
+     "id":"de-DE",
+     "iso3Country":"DEU",
+     "iso3Language":"deu",
+     "language":"de",
+     "name":"German (Germany)"
+     },
+     {
+     "country":"",
+     "default":false,
+     "displayCountry":"",
+     "displayLanguage":"Deutsch",
+     "displayName":"Deutsch",
+     "id":"de",
+     "iso3Country":"",
+     "iso3Language":"deu",
+     "language":"de",
+     "name":"German"
+     },
+     {
+     "country":"US",
+     "default":false,
+     "displayCountry":"United States",
+     "displayLanguage":"English",
+     "displayName":"English (United States)",
+     "id":"en-US",
+     "iso3Country":"USA",
+     "iso3Language":"eng",
+     "language":"en",
+     "name":"English (United States)"
+     },
+     {
+     "country":"CA",
+     "default":false,
+     "displayCountry":"Canada",
+     "displayLanguage":"English",
+     "displayName":"English (Canada)",
+     "id":"en-CA",
+     "iso3Country":"CAN",
+     "iso3Language":"eng",
+     "language":"en",
+     "name":"English (Canada)"
+     },
+     {
+     "country":"",
+     "default":false,
+     "displayCountry":"",
+     "displayLanguage":"English",
+     "displayName":"English",
+     "id":"en",
+     "iso3Country":"",
+     "iso3Language":"eng",
+     "language":"en",
+     "name":"English"
+     },
+     {
+     "country":"",
+     "default":false,
+     "displayCountry":"",
+     "displayLanguage":"español",
+     "displayName":"español",
+     "id":"es",
+     "iso3Country":"",
+     "iso3Language":"spa",
+     "language":"es",
+     "name":"Spanish"
+     }
+     ]
+     },
+     {
+     "configurationType":"globalConfiguration",
+     "id":"SalesforcePaymentsAllowed",
+     "value":true
+     },
+     {
+     "configurationType":"globalConfiguration",
+     "id":"gcp",
+     "value":"test-gcp-key"
+     }
+     ]
+     }
+     ```
+     
+     ### Caching
+     
+     Caching capabilities are available for the Shopper Configuration APIs. For details, see [Server-Side Web-Tier Caching.](https://developer.salesforce.com/docs/commerce/commerce-api/guide/server-side-web-tier-caching.html)*<br />
+     *
+     * Simple example:
+     *
+     * ```typescript
+     *   import { ShopperConfigurations } from "commerce-sdk-isomorphic";
+     *
+     *   const clientConfig = {
+     *     parameters: {
+     *       clientId: "XXXXXX",
+     *       organizationId: "XXXX",
+     *       shortCode: "XXX",
+     *       siteId: "XX"
+     *     }
+     *   };
+     *   const shopperConfigurationsClient = new ShopperConfigurations(clientConfig);
+     * ```
+     *
+     * <span style="font-size:.7em; display:block; text-align: right">
+     * API Version: 0.0.33<br />
+     * Last Updated: <br />
+     * </span>
+     *
+     *
+     */
+    class ShopperConfigurations<ConfigParameters extends ShopperConfigurationsParameters & Record<string, unknown>> {
+        // baseUri is not required on ClientConfig, but we know that we provide one in the class constructor
+        clientConfig: ClientConfig<ConfigParameters> & {
+            baseUri: string;
+        };
+        static readonly defaultBaseUri = "https://{shortCode}.api.commercecloud.salesforce.com/configuration/shopper-configurations/v1";
+        static readonly apiPaths: {
+            getConfigurations: string;
+        };
+        constructor(config: ClientConfigInit<ConfigParameters>);
+        static readonly paramKeys: {
+            readonly getConfigurations: readonly [
+                "organizationId",
+                "siteId"
+            ];
+            readonly getConfigurationsRequired: readonly [
+                "organizationId",
+                "siteId"
+            ];
+        };
+        /**
+         * Retrieves configurations for the specified organization and site.
+         *
+         * If you would like to get a raw Response object use the other getConfigurations function.
+         *
+         * @param options - An object containing the options for this method.
+         * @param options.parameters - An object containing the parameters for this method.
+         * @param options.parameters.organizationId - An identifier for the organization the request is being made by
+         * @param options.parameters.siteId - The identifier of the site that a request is being made in the context of. Attributes might have site specific values, and some objects may only be assigned to specific sites.
+         * @param options.headers - An object literal of key value pairs of the headers to be sent with this request.
+         *
+         * @returns A promise of type SiteConfiguration.
+         */
+        getConfigurations(options?: RequireParametersUnlessAllAreOptional<{
+            parameters?: CompositeParameters<{
+                organizationId: string;
+                siteId: string;
+            } & QueryParameters, ConfigParameters>;
+            headers?: {
+                [key: string]: string;
+            };
+        }>): Promise<SiteConfiguration>;
+        /**
+         * Retrieves configurations for the specified organization and site.
+         *
+         * @param options - An object containing the options for this method.
+         * @param options.parameters - An object containing the parameters for this method.
+         * @param options.parameters.organizationId - An identifier for the organization the request is being made by
+         * @param options.parameters.siteId - The identifier of the site that a request is being made in the context of. Attributes might have site specific values, and some objects may only be assigned to specific sites.
+         * @param options.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.
+         *
+         * @returns A promise of type Response if rawResponse is true, a promise of type SiteConfiguration otherwise.
+         */
+        getConfigurations<T extends boolean>(options?: RequireParametersUnlessAllAreOptional<{
+            parameters?: CompositeParameters<{
+                organizationId: string;
+                siteId: string;
+            } & QueryParameters, ConfigParameters>;
+            headers?: {
+                [key: string]: string;
+            };
+        }>, rawResponse?: T): Promise<T extends true ? Response : SiteConfiguration>;
+    }
+}
+declare namespace ShopperConfigurationsModelTypes {
+    /**
+     * @type ErrorResponse:
+     *
+     * @property title: A short, human-readable summary of the problem type.  It will not change from occurrence to occurrence of the  problem, except for purposes of localization
+     * - **Max Length:** 256
+     *
+     * @property type: A URI reference [RFC3986] that identifies the problem type.  This specification encourages that, when dereferenced, it provide human-readable documentation for the problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When this member is not present, its value is assumed to be \"about:blank\". It accepts relative URIs; this means that they must be resolved relative to the document\'s base URI, as per [RFC3986], Section 5.
+     * - **Max Length:** 2048
+     *
+     * @property detail: A human-readable explanation specific to this occurrence of the problem.
+     *
+     * @property instance: A URI reference that identifies the specific occurrence of the problem.  It may or may not yield further information if dereferenced.  It accepts relative URIs; this means that they must be resolved relative to the document\'s base URI, as per [RFC3986], Section 5.
+     * - **Max Length:** 2048
+     *
+     */
+    type ErrorResponse = {
+        title: string;
+        type: string;
+        detail: string;
+        instance?: string;
+    } & {
+        [key: string]: any;
+    };
+    /**
+     * @type ModelConfiguration: Configuration object
+     *
+     * @property id: identifier
+     * - **Max Length:** 255
+     *
+     * @property value: value for identifier
+     * - **Max Length:** 255
+     *
+     * @property configurationType: type of configuration value
+     * - **Max Length:** 255
+     *
+     */
+    type ModelConfiguration = {
+        id: string;
+        value: any | null;
+        configurationType?: string;
+    } & {
+        [key: string]: any;
+    };
+    /**
+     * @type SiteConfiguration: Site Configuration object
+     *
+     * @property configurations: List configurations for the instance and site
+     *
+     */
+    type SiteConfiguration = {
+        configurations: Array<ModelConfiguration>;
+    } & {
+        [key: string]: any;
+    };
+}
+declare namespace ShopperConfigurationsTypes {
+    // API types
+    type ShopperConfigurationsPathParameters = ShopperConfigurationsApiTypes.ShopperConfigurationsPathParameters;
+    type ShopperConfigurationsQueryParameters = ShopperConfigurationsApiTypes.ShopperConfigurationsQueryParameters;
+    type getConfigurationsQueryParameters = ShopperConfigurationsApiTypes.getConfigurationsQueryParameters;
+    type getConfigurationsPathParameters = ShopperConfigurationsApiTypes.getConfigurationsPathParameters;
+    // Model types
+    type ErrorResponse = ShopperConfigurationsModelTypes.ErrorResponse;
+    type ModelConfiguration = ShopperConfigurationsModelTypes.ModelConfiguration;
+    type SiteConfiguration = ShopperConfigurationsModelTypes.SiteConfiguration;
+}
 /**
  * The consent status of the subscription as supplied or recorded by this system
  */
@@ -20697,9 +21787,9 @@ type ShopperConsentsParameters = ShopperConsentsPathParameters & BaseUriParamete
  * [Shopper Consents](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-consents:Summary)
  * ==================================
  *
- * *# Shopper Consent
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-consents/shopper-consents-oas-v1-public.yaml)
  
- ## API Overview
+ # API Overview
  
  The Shopper Consent API offers a centralized method for managing shopper consent. With this API, shoppers can view and update subscription preferences for marketing communications across various channels. This API controls how and where shoppers receive marketing messages while ensuring compliance with privacy regulations.
  
@@ -21201,9 +22291,9 @@ declare namespace ShopperConsentsApiTypes {
      * [Shopper Consents](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-consents:Summary)
      * ==================================
      *
-     * *# Shopper Consent
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-consents/shopper-consents-oas-v1-public.yaml)
      
-     ## API Overview
+     # API Overview
      
      The Shopper Consent API offers a centralized method for managing shopper consent. With this API, shoppers can view and update subscription preferences for marketing communications across various channels. This API controls how and where shoppers receive marketing messages while ensuring compliance with privacy regulations.
      
@@ -21638,6 +22728,8 @@ type ShopperContextGeoLocation = {
  *
  * @property geoLocation:
  *
+ * @property couponCodes: Array of coupon codes to be saved in the shopper context. Set the coupon codes to evaluate promotions that can be triggered by these codes.
+ *
  */
 type ShopperContext = {
     effectiveDateTime?: string | null;
@@ -21651,6 +22743,7 @@ type ShopperContext = {
     };
     clientIp?: string;
     geoLocation?: ShopperContextGeoLocation;
+    couponCodes?: Array<string>;
 } & {
     [key: string]: any;
 };
@@ -21700,7 +22793,9 @@ type ShopperContextParameters = ShopperContextPathParameters & BaseUriParameters
  * [Shopper Context](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-context:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-context/shopper-context-oas-v1-public.yaml)
+ 
+ # API Overview
  
  With the Shopper Context API, you can set any context information as a key/value pair and use it to retrieve personalized promotions, payment methods, and shipping methods. The context information that is set is evaluated against the customer group definitions to determine a customer group (shopper segment), and is then used to activate the experiences that are associated with a particular segment, such as promotions.
  
@@ -22286,6 +23381,8 @@ declare namespace ShopperContextsApiTypes {
      *
      * @property geoLocation:
      *
+     * @property couponCodes: Array of coupon codes to be saved in the shopper context. Set the coupon codes to evaluate promotions that can be triggered by these codes.
+     *
      */
     type ShopperContext = {
         effectiveDateTime?: string | null;
@@ -22299,6 +23396,7 @@ declare namespace ShopperContextsApiTypes {
         };
         clientIp?: string;
         geoLocation?: ShopperContextGeoLocation;
+        couponCodes?: Array<string>;
     } & {
         [key: string]: any;
     };
@@ -22348,7 +23446,9 @@ declare namespace ShopperContextsApiTypes {
      * [Shopper Context](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-context:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-context/shopper-context-oas-v1-public.yaml)
+     
+     # API Overview
      
      With the Shopper Context API, you can set any context information as a key/value pair and use it to retrieve personalized promotions, payment methods, and shipping methods. The context information that is set is evaluated against the customer group definitions to determine a customer group (shopper segment), and is then used to activate the experiences that are associated with a particular segment, such as promotions.
      
@@ -22827,6 +23927,8 @@ declare namespace ShopperContextsModelTypes {
      *
      * @property geoLocation:
      *
+     * @property couponCodes: Array of coupon codes to be saved in the shopper context. Set the coupon codes to evaluate promotions that can be triggered by these codes.
+     *
      */
     type ShopperContext = {
         effectiveDateTime?: string | null;
@@ -22840,6 +23942,7 @@ declare namespace ShopperContextsModelTypes {
         };
         clientIp?: string;
         geoLocation?: ShopperContextGeoLocation;
+        couponCodes?: Array<string>;
     } & {
         [key: string]: any;
     };
@@ -25504,7 +26607,9 @@ type ShopperCustomersParameters = ShopperCustomersPathParameters & BaseUriParame
  * [Shopper Customers](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-customers:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-customers/shopper-customers-oas-v1-public.yaml)
+ 
+ # API Overview
  
  The Shopper Customers API enables you to develop functionality that lets customers log in, and manage their profiles and product lists. Profile management includes ability for shoppers to add or modify addresses and payment methods, and add or modify products to wishlists or favorites. Commerce Cloud provides a rich set of Authentication APIs that include logging in guest shoppers, registered shoppers, agents on behalf of customers and a trusted system authentication on behalf of customers. In all authentication scenarios involving customers, a JSON Web Token (JWT) is generated in Commerce Cloud. Using the JWT, customers can access other Shopper API resources like Orders and Baskets. The application must refresh the JWT every 30 minutes to save the shopper activity (for example, retain products in a shopper's cart) for prolonged periods of time.
  
@@ -30290,7 +31395,9 @@ declare namespace ShopperCustomersApiTypes {
      * [Shopper Customers](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-customers:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-customers/shopper-customers-oas-v1-public.yaml)
+     
+     # API Overview
      
      The Shopper Customers API enables you to develop functionality that lets customers log in, and manage their profiles and product lists. Profile management includes ability for shoppers to add or modify addresses and payment methods, and add or modify products to wishlists or favorites. Commerce Cloud provides a rich set of Authentication APIs that include logging in guest shoppers, registered shoppers, agents on behalf of customers and a trusted system authentication on behalf of customers. In all authentication scenarios involving customers, a JSON Web Token (JWT) is generated in Commerce Cloud. Using the JWT, customers can access other Shopper API resources like Orders and Baskets. The application must refresh the JWT every 30 minutes to save the shopper activity (for example, retain products in a shopper's cart) for prolonged periods of time.
      
@@ -35036,7 +36143,10 @@ type ShopperExperienceParameters = ShopperExperiencePathParameters & BaseUriPara
  * [Shopper Experience](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-experience:Summary)
  * ==================================
  *
- * *Use the Shopper Experience API to look up page information for pages that are created in Page Designer.
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-experience/shopper-experience-oas-v1-public.yaml)
+ 
+ # API Overview
+ Use the Shopper Experience API to look up page information for pages that are created in Page Designer.
  
  Responses include the following:
  
@@ -35552,7 +36662,10 @@ declare namespace ShopperExperienceApiTypes {
      * [Shopper Experience](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-experience:Summary)
      * ==================================
      *
-     * *Use the Shopper Experience API to look up page information for pages that are created in Page Designer.
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-experience/shopper-experience-oas-v1-public.yaml)
+     
+     # API Overview
+     Use the Shopper Experience API to look up page information for pages that are created in Page Designer.
      
      Responses include the following:
      
@@ -36017,6 +37130,7 @@ type ShopperGiftCertificatesParameters = ShopperGiftCertificatesPathParameters &
  * ==================================
  *
  * *# API Overview
+ [Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-gift-certificates/shopper-gift-certificates-oas-v1-public.yaml)
  
  Use the Shopper Gift Certificates API to obtain gift certificate details.
  
@@ -36339,6 +37453,7 @@ declare namespace ShopperGiftCertificatesApiTypes {
      * ==================================
      *
      * *# API Overview
+     [Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-gift-certificates/shopper-gift-certificates-oas-v1-public.yaml)
      
      Use the Shopper Gift Certificates API to obtain gift certificate details.
      
@@ -36595,6 +37710,12 @@ type TokenType = "Bearer";
  * @property idp_access_token: This is the access token that is returned from the IDP. The IDP access token is returned to be able to make calls into the IDP outside of SLAS.
  * - **Max Length:** 8192
  *
+ * @property idp_refresh_token: This is the refresh token that is returned from the IDP. The IDP refresh token is returned to be able to make calls into the IDP outside of SLAS.
+ * - **Max Length:** 128
+ *
+ * @property dnt: Do not track
+ * - **Max Length:** 5
+ *
  */
 type TokenResponse = {
     access_token: string;
@@ -36607,6 +37728,8 @@ type TokenResponse = {
     customer_id: string;
     enc_user_id: string;
     idp_access_token: string;
+    idp_refresh_token?: string;
+    dnt?: string;
 } & {
     [key: string]: any;
 };
@@ -36684,6 +37807,7 @@ type getPasswordLessAccessTokenBodyType = {
     pwdless_login_token: string;
     client_id?: string;
     code_verifier?: string;
+    login_id?: string;
 };
 type getPasswordResetTokenQueryParameters = {};
 type getPasswordResetTokenPathParameters = {
@@ -36823,7 +37947,9 @@ type ShopperLoginParameters = ShopperLoginPathParameters & BaseUriParameters & S
  * [Shopper Login](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-login:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-login/shopper-login-oas-v1-public.yaml)
+ 
+ # API Overview
  
  The Shopper Login and API Access Service (SLAS) enables secure access to Commerce Cloud’s Shopper APIs for a wide range of headless commerce applications.
  
@@ -36959,7 +38085,8 @@ declare class ShopperLogin<ConfigParameters extends ShopperLoginParameters & Rec
             "hint",
             "pwdless_login_token",
             "client_id",
-            "code_verifier"
+            "code_verifier",
+            "login_id"
         ];
         readonly getPasswordLessAccessTokenRequired: readonly [
             "organizationId",
@@ -37533,6 +38660,7 @@ declare class ShopperLogin<ConfigParameters extends ShopperLoginParameters & Rec
      * @param options.body.pwdless_login_token - Passwordless login token that was created from the user ID.
      * @param options.body.client_id - The public client ID.
      * @param options.body.code_verifier - PKCE code verifier. Created by the client.  The `code_challenge` is created by SHA256 hashing the `code_verifier` and Base64 encoding the resulting hash.  The `code_verifier` should be a high entropy cryptographically random string with a minimum of 43 characters and a maximum of 128 characters.
+     * @param options.body.login_id - The ID used by the shopper for password token request. When provided, login_id must exactly match the ID used during passwordless login. ex. If passwordless login used `samantha.sampleson@example.com`, but the passwordless login token request provides `sam.sampleson@example.com`, the request fails due to mismatch.
      *
      * @returns A promise of type TokenResponse.
      */
@@ -37558,6 +38686,7 @@ declare class ShopperLogin<ConfigParameters extends ShopperLoginParameters & Rec
      * @param options.body.pwdless_login_token - Passwordless login token that was created from the user ID.
      * @param options.body.client_id - The public client ID.
      * @param options.body.code_verifier - PKCE code verifier. Created by the client.  The `code_challenge` is created by SHA256 hashing the `code_verifier` and Base64 encoding the resulting hash.  The `code_verifier` should be a high entropy cryptographically random string with a minimum of 43 characters and a maximum of 128 characters.
+     * @param options.body.login_id - The ID used by the shopper for password token request. When provided, login_id must exactly match the ID used during passwordless login. ex. If passwordless login used `samantha.sampleson@example.com`, but the passwordless login token request provides `sam.sampleson@example.com`, the request fails due to mismatch.
      * @param rawResponse - Set to true to return entire Response object instead of DTO.
      *
      * @returns A promise of type Response if rawResponse is true, a promise of type TokenResponse otherwise.
@@ -38094,7 +39223,9 @@ declare class ShopperLogin<ConfigParameters extends ShopperLoginParameters & Rec
      * @param options.parameters.client_id - The SLAS public client ID or SLAS private client ID for use with trusted-agent requests. When using a private client ID a PKCE code challenge is not required.
      * @param options.parameters.refresh_token - Refresh token that was given during the access token request.
      * @param options.parameters.channel_id - The `channel_id` parameter must be provided if the shopper authenticated using the `login` endpoint with B2C Commerce.
-     * @param options.parameters.hint - `hint=all-sessions` logs out all sessions of the shopper and invalidates all active refresh tokens for the shopper.
+     * @param options.parameters.hint - `hint=all-sessions` logs out all sessions and invalidates all refresh tokens for a shopper with the same SLAS user ID.
+     This only works within the same session type. Sessions created through different authentication methods (/authorize vs. Trusted System On Behalf) are treated as separate sessions. To invalidate tokens with different SLAS User IDs, you must make explicit logout calls with each token.
+     A shopper authenticated via both /authorize and TSOB has two separate sessions. You will need two logout calls (one per token) to fully log them out.
      
      If this query parameter is not provided, the default behavior is to log out only the current session that matches the refresh token in the request.
      
@@ -38128,7 +39259,9 @@ declare class ShopperLogin<ConfigParameters extends ShopperLoginParameters & Rec
      * @param options.parameters.client_id - The SLAS public client ID or SLAS private client ID for use with trusted-agent requests. When using a private client ID a PKCE code challenge is not required.
      * @param options.parameters.refresh_token - Refresh token that was given during the access token request.
      * @param options.parameters.channel_id - The `channel_id` parameter must be provided if the shopper authenticated using the `login` endpoint with B2C Commerce.
-     * @param options.parameters.hint - `hint=all-sessions` logs out all sessions of the shopper and invalidates all active refresh tokens for the shopper.
+     * @param options.parameters.hint - `hint=all-sessions` logs out all sessions and invalidates all refresh tokens for a shopper with the same SLAS user ID.
+     This only works within the same session type. Sessions created through different authentication methods (/authorize vs. Trusted System On Behalf) are treated as separate sessions. To invalidate tokens with different SLAS User IDs, you must make explicit logout calls with each token.
+     A shopper authenticated via both /authorize and TSOB has two separate sessions. You will need two logout calls (one per token) to fully log them out.
      
      If this query parameter is not provided, the default behavior is to log out only the current session that matches the refresh token in the request.
      
@@ -38427,6 +39560,12 @@ declare namespace ShopperLoginApiTypes {
      * @property idp_access_token: This is the access token that is returned from the IDP. The IDP access token is returned to be able to make calls into the IDP outside of SLAS.
      * - **Max Length:** 8192
      *
+     * @property idp_refresh_token: This is the refresh token that is returned from the IDP. The IDP refresh token is returned to be able to make calls into the IDP outside of SLAS.
+     * - **Max Length:** 128
+     *
+     * @property dnt: Do not track
+     * - **Max Length:** 5
+     *
      */
     type TokenResponse = {
         access_token: string;
@@ -38439,6 +39578,8 @@ declare namespace ShopperLoginApiTypes {
         customer_id: string;
         enc_user_id: string;
         idp_access_token: string;
+        idp_refresh_token?: string;
+        dnt?: string;
     } & {
         [key: string]: any;
     };
@@ -38526,6 +39667,7 @@ declare namespace ShopperLoginApiTypes {
         pwdless_login_token: string;
         client_id?: string;
         code_verifier?: string;
+        login_id?: string;
     };
     type getPasswordResetTokenQueryParameters = {};
     type getPasswordResetTokenPathParameters = {
@@ -38665,7 +39807,9 @@ declare namespace ShopperLoginApiTypes {
      * [Shopper Login](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-login:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-login/shopper-login-oas-v1-public.yaml)
+     
+     # API Overview
      
      The Shopper Login and API Access Service (SLAS) enables secure access to Commerce Cloud’s Shopper APIs for a wide range of headless commerce applications.
      
@@ -38801,7 +39945,8 @@ declare namespace ShopperLoginApiTypes {
                 "hint",
                 "pwdless_login_token",
                 "client_id",
-                "code_verifier"
+                "code_verifier",
+                "login_id"
             ];
             readonly getPasswordLessAccessTokenRequired: readonly [
                 "organizationId",
@@ -39375,6 +40520,7 @@ declare namespace ShopperLoginApiTypes {
          * @param options.body.pwdless_login_token - Passwordless login token that was created from the user ID.
          * @param options.body.client_id - The public client ID.
          * @param options.body.code_verifier - PKCE code verifier. Created by the client.  The `code_challenge` is created by SHA256 hashing the `code_verifier` and Base64 encoding the resulting hash.  The `code_verifier` should be a high entropy cryptographically random string with a minimum of 43 characters and a maximum of 128 characters.
+         * @param options.body.login_id - The ID used by the shopper for password token request. When provided, login_id must exactly match the ID used during passwordless login. ex. If passwordless login used `samantha.sampleson@example.com`, but the passwordless login token request provides `sam.sampleson@example.com`, the request fails due to mismatch.
          *
          * @returns A promise of type TokenResponse.
          */
@@ -39400,6 +40546,7 @@ declare namespace ShopperLoginApiTypes {
          * @param options.body.pwdless_login_token - Passwordless login token that was created from the user ID.
          * @param options.body.client_id - The public client ID.
          * @param options.body.code_verifier - PKCE code verifier. Created by the client.  The `code_challenge` is created by SHA256 hashing the `code_verifier` and Base64 encoding the resulting hash.  The `code_verifier` should be a high entropy cryptographically random string with a minimum of 43 characters and a maximum of 128 characters.
+         * @param options.body.login_id - The ID used by the shopper for password token request. When provided, login_id must exactly match the ID used during passwordless login. ex. If passwordless login used `samantha.sampleson@example.com`, but the passwordless login token request provides `sam.sampleson@example.com`, the request fails due to mismatch.
          * @param rawResponse - Set to true to return entire Response object instead of DTO.
          *
          * @returns A promise of type Response if rawResponse is true, a promise of type TokenResponse otherwise.
@@ -39936,7 +41083,9 @@ declare namespace ShopperLoginApiTypes {
          * @param options.parameters.client_id - The SLAS public client ID or SLAS private client ID for use with trusted-agent requests. When using a private client ID a PKCE code challenge is not required.
          * @param options.parameters.refresh_token - Refresh token that was given during the access token request.
          * @param options.parameters.channel_id - The `channel_id` parameter must be provided if the shopper authenticated using the `login` endpoint with B2C Commerce.
-         * @param options.parameters.hint - `hint=all-sessions` logs out all sessions of the shopper and invalidates all active refresh tokens for the shopper.
+         * @param options.parameters.hint - `hint=all-sessions` logs out all sessions and invalidates all refresh tokens for a shopper with the same SLAS user ID.
+         This only works within the same session type. Sessions created through different authentication methods (/authorize vs. Trusted System On Behalf) are treated as separate sessions. To invalidate tokens with different SLAS User IDs, you must make explicit logout calls with each token.
+         A shopper authenticated via both /authorize and TSOB has two separate sessions. You will need two logout calls (one per token) to fully log them out.
          
          If this query parameter is not provided, the default behavior is to log out only the current session that matches the refresh token in the request.
          
@@ -39970,7 +41119,9 @@ declare namespace ShopperLoginApiTypes {
          * @param options.parameters.client_id - The SLAS public client ID or SLAS private client ID for use with trusted-agent requests. When using a private client ID a PKCE code challenge is not required.
          * @param options.parameters.refresh_token - Refresh token that was given during the access token request.
          * @param options.parameters.channel_id - The `channel_id` parameter must be provided if the shopper authenticated using the `login` endpoint with B2C Commerce.
-         * @param options.parameters.hint - `hint=all-sessions` logs out all sessions of the shopper and invalidates all active refresh tokens for the shopper.
+         * @param options.parameters.hint - `hint=all-sessions` logs out all sessions and invalidates all refresh tokens for a shopper with the same SLAS user ID.
+         This only works within the same session type. Sessions created through different authentication methods (/authorize vs. Trusted System On Behalf) are treated as separate sessions. To invalidate tokens with different SLAS User IDs, you must make explicit logout calls with each token.
+         A shopper authenticated via both /authorize and TSOB has two separate sessions. You will need two logout calls (one per token) to fully log them out.
          
          If this query parameter is not provided, the default behavior is to log out only the current session that matches the refresh token in the request.
          
@@ -40162,6 +41313,12 @@ declare namespace ShopperLoginModelTypes {
      * @property idp_access_token: This is the access token that is returned from the IDP. The IDP access token is returned to be able to make calls into the IDP outside of SLAS.
      * - **Max Length:** 8192
      *
+     * @property idp_refresh_token: This is the refresh token that is returned from the IDP. The IDP refresh token is returned to be able to make calls into the IDP outside of SLAS.
+     * - **Max Length:** 128
+     *
+     * @property dnt: Do not track
+     * - **Max Length:** 5
+     *
      */
     type TokenResponse = {
         access_token: string;
@@ -40174,6 +41331,8 @@ declare namespace ShopperLoginModelTypes {
         customer_id: string;
         enc_user_id: string;
         idp_access_token: string;
+        idp_refresh_token?: string;
+        dnt?: string;
     } & {
         [key: string]: any;
     };
@@ -41536,6 +42695,7 @@ type ShopperOrdersParameters = ShopperOrdersPathParameters & BaseUriParameters &
  * ==================================
  *
  * *# API Overview
+ [Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-orders/shopper-orders-oas-v1-public.yaml)
  
  The Shopper Orders API enables you to:
  
@@ -43584,6 +44744,7 @@ declare namespace ShopperOrdersApiTypes {
      * ==================================
      *
      * *# API Overview
+     [Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-orders/shopper-orders-oas-v1-public.yaml)
      
      The Shopper Orders API enables you to:
      
@@ -46262,7 +47423,9 @@ type ShopperProductsParameters = ShopperProductsPathParameters & BaseUriParamete
  * [Shopper Products](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-products:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-products/shopper-products-oas-v1-public.yaml)
+ 
+ # API Overview
  
  The Shopper Products API enables you to access product details for products that are online, merchandised to a particular site catalog, and ready to be sold. You can use these product details to merchandise the product on other ecommerce channels. To set up category navigation paths on other commerce apps or storefronts, you can use the Categories API.
  
@@ -47625,7 +48788,9 @@ declare namespace ShopperProductsApiTypes {
      * [Shopper Products](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-products:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-products/shopper-products-oas-v1-public.yaml)
+     
+     # API Overview
      
      The Shopper Products API enables you to access product details for products that are online, merchandised to a particular site catalog, and ready to be sold. You can use these product details to merchandise the product on other ecommerce channels. To set up category navigation paths on other commerce apps or storefronts, you can use the Categories API.
      
@@ -48958,6 +50123,7 @@ type ShopperPromotionsParameters = ShopperPromotionsPathParameters & BaseUriPara
  * ==================================
  *
  * *# API Overview
+ [Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-promotions/shopper-promotions-oas-v1-public.yaml)
  
  Retrieve information about active promotions within the context of a shopper and a site. You can use this API to retrieve promotions that you configured in the commerce platform by searching for specific promotion IDs or by searching for promotions associated with a campaign.
  
@@ -49409,6 +50575,7 @@ declare namespace ShopperPromotionsApiTypes {
      * ==================================
      *
      * *# API Overview
+     [Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-promotions/shopper-promotions-oas-v1-public.yaml)
      
      Retrieve information about active promotions within the context of a shopper and a site. You can use this API to retrieve promotions that you configured in the commerce platform by searching for specific promotion IDs or by searching for promotions associated with a campaign.
      
@@ -50469,7 +51636,9 @@ type ShopperSearchParameters = ShopperSearchPathParameters & BaseUriParameters &
  * [Shopper Search](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-search:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-search/shopper-search-oas-v1-public.yaml)
+ 
+ # API Overview
  
  Use the Shopper Search API for search functionality that lets shoppers search for products using keywords and refinement. The search results can be products or suggestions based on the endpoint you choose in the API.
  
@@ -50728,11 +51897,13 @@ declare class ShopperSearch<ConfigParameters extends ShopperSearchParameters & R
      * @param options.parameters - An object containing the parameters for this method.
      * @param options.parameters.organizationId - An identifier for the organization the request is being made by
      * @param options.parameters.siteId - The identifier of the site that a request is being made in the context of. Attributes might have site specific values, and some objects may only be assigned to specific sites.
-     * @param options.parameters.select - The property selector declaring which fields are included into the response payload. You can specify a single field name, a comma-separated list of names or work with wildcards. You can also specify array operations and filter expressions. The actual selector value must be enclosed within parentheses.
+     * @param options.parameters.select -
      * @param options.parameters.q - The query phrase to search for. For example to search for a product "shirt", type q=shirt.
-     * @param options.parameters.refine - Parameter that represents a refinement attribute or values pair. Refinement attribute ID and values are separated by '='. Multiple values are supported by a subset of refinement attributes and can be provided by separating them using a pipe (URL encoded = \"|\") i.e. refine=c_refinementColor=red|green|blue. Value ranges can be specified like this: refine=price=(100..500) .
-     Multiple refine parameters can be provided by using the refine as the key i.e refine=price=(0..10)&refine=c_refinementColor=green. The refinements can be a collection of custom defined attributes IDs
-     and the system defined attributes IDs but the search can only accept a total of 9 refinements at a time.
+     * @param options.parameters.refine - Parameter that represents a refinement attribute or values pair. Refinement attribute ID and values are separated by '='.<br>
+     Multiple values are supported by a subset of refinement attributes and can be provided by separating them using a pipe (URL encoded = \"|\"), for example: refine=c_refinementColor=red|green|blue.<br>
+     Value ranges can be specified like this: refine=price=(100..500).<br>
+     Multiple refine parameters can be provided by using the refine as the key, for example: refine=price=(0..10)&refine=c_refinementColor=green.<br>
+     The refinements can be a collection of custom defined attributes IDs and the system defined attributes IDs but the search can only accept a total of 9 refinements at a time.<br>
      
      The following system refinement attribute ids are supported:<br>
      `cgid`: Allows refinement per single category ID. Multiple category ids are not supported.
@@ -50754,7 +51925,6 @@ declare class ShopperSearch<ConfigParameters extends ShopperSearchParameters & R
      * @param options.parameters.expand - A comma-separated list with allowed values - `availability`, `images`, `prices`, `represented_products`, `variations`, `promotions`, `custom_properties`.
      By default, the expand parameter includes `availability, images, prices, represented_products, variations`.
      Use none to disable all expand options.
-     **The page_meta_tags expand value is optional and is available B2C Commerce version 25.2.**"
      * @param options.parameters.allImages - When the `images` expand parameter is used with this flag, the response includes the `imageGroups property`, which contains an image model.
      If this flag is true, the full image model is returned. If false, only matching images are included.
      If no flag is passed, the `imageGroups` property is omitted from the response.
@@ -50798,11 +51968,13 @@ declare class ShopperSearch<ConfigParameters extends ShopperSearchParameters & R
      * @param options.parameters - An object containing the parameters for this method.
      * @param options.parameters.organizationId - An identifier for the organization the request is being made by
      * @param options.parameters.siteId - The identifier of the site that a request is being made in the context of. Attributes might have site specific values, and some objects may only be assigned to specific sites.
-     * @param options.parameters.select - The property selector declaring which fields are included into the response payload. You can specify a single field name, a comma-separated list of names or work with wildcards. You can also specify array operations and filter expressions. The actual selector value must be enclosed within parentheses.
+     * @param options.parameters.select -
      * @param options.parameters.q - The query phrase to search for. For example to search for a product "shirt", type q=shirt.
-     * @param options.parameters.refine - Parameter that represents a refinement attribute or values pair. Refinement attribute ID and values are separated by '='. Multiple values are supported by a subset of refinement attributes and can be provided by separating them using a pipe (URL encoded = \"|\") i.e. refine=c_refinementColor=red|green|blue. Value ranges can be specified like this: refine=price=(100..500) .
-     Multiple refine parameters can be provided by using the refine as the key i.e refine=price=(0..10)&refine=c_refinementColor=green. The refinements can be a collection of custom defined attributes IDs
-     and the system defined attributes IDs but the search can only accept a total of 9 refinements at a time.
+     * @param options.parameters.refine - Parameter that represents a refinement attribute or values pair. Refinement attribute ID and values are separated by '='.<br>
+     Multiple values are supported by a subset of refinement attributes and can be provided by separating them using a pipe (URL encoded = \"|\"), for example: refine=c_refinementColor=red|green|blue.<br>
+     Value ranges can be specified like this: refine=price=(100..500).<br>
+     Multiple refine parameters can be provided by using the refine as the key, for example: refine=price=(0..10)&refine=c_refinementColor=green.<br>
+     The refinements can be a collection of custom defined attributes IDs and the system defined attributes IDs but the search can only accept a total of 9 refinements at a time.<br>
      
      The following system refinement attribute ids are supported:<br>
      `cgid`: Allows refinement per single category ID. Multiple category ids are not supported.
@@ -50824,7 +51996,6 @@ declare class ShopperSearch<ConfigParameters extends ShopperSearchParameters & R
      * @param options.parameters.expand - A comma-separated list with allowed values - `availability`, `images`, `prices`, `represented_products`, `variations`, `promotions`, `custom_properties`.
      By default, the expand parameter includes `availability, images, prices, represented_products, variations`.
      Use none to disable all expand options.
-     **The page_meta_tags expand value is optional and is available B2C Commerce version 25.2.**"
      * @param options.parameters.allImages - When the `images` expand parameter is used with this flag, the response includes the `imageGroups property`, which contains an image model.
      If this flag is true, the full image model is returned. If false, only matching images are included.
      If no flag is passed, the `imageGroups` property is omitted from the response.
@@ -51758,7 +52929,9 @@ declare namespace ShopperSearchApiTypes {
      * [Shopper Search](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-search:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-search/shopper-search-oas-v1-public.yaml)
+     
+     # API Overview
      
      Use the Shopper Search API for search functionality that lets shoppers search for products using keywords and refinement. The search results can be products or suggestions based on the endpoint you choose in the API.
      
@@ -52017,11 +53190,13 @@ declare namespace ShopperSearchApiTypes {
          * @param options.parameters - An object containing the parameters for this method.
          * @param options.parameters.organizationId - An identifier for the organization the request is being made by
          * @param options.parameters.siteId - The identifier of the site that a request is being made in the context of. Attributes might have site specific values, and some objects may only be assigned to specific sites.
-         * @param options.parameters.select - The property selector declaring which fields are included into the response payload. You can specify a single field name, a comma-separated list of names or work with wildcards. You can also specify array operations and filter expressions. The actual selector value must be enclosed within parentheses.
+         * @param options.parameters.select -
          * @param options.parameters.q - The query phrase to search for. For example to search for a product "shirt", type q=shirt.
-         * @param options.parameters.refine - Parameter that represents a refinement attribute or values pair. Refinement attribute ID and values are separated by '='. Multiple values are supported by a subset of refinement attributes and can be provided by separating them using a pipe (URL encoded = \"|\") i.e. refine=c_refinementColor=red|green|blue. Value ranges can be specified like this: refine=price=(100..500) .
-         Multiple refine parameters can be provided by using the refine as the key i.e refine=price=(0..10)&refine=c_refinementColor=green. The refinements can be a collection of custom defined attributes IDs
-         and the system defined attributes IDs but the search can only accept a total of 9 refinements at a time.
+         * @param options.parameters.refine - Parameter that represents a refinement attribute or values pair. Refinement attribute ID and values are separated by '='.<br>
+         Multiple values are supported by a subset of refinement attributes and can be provided by separating them using a pipe (URL encoded = \"|\"), for example: refine=c_refinementColor=red|green|blue.<br>
+         Value ranges can be specified like this: refine=price=(100..500).<br>
+         Multiple refine parameters can be provided by using the refine as the key, for example: refine=price=(0..10)&refine=c_refinementColor=green.<br>
+         The refinements can be a collection of custom defined attributes IDs and the system defined attributes IDs but the search can only accept a total of 9 refinements at a time.<br>
          
          The following system refinement attribute ids are supported:<br>
          `cgid`: Allows refinement per single category ID. Multiple category ids are not supported.
@@ -52043,7 +53218,6 @@ declare namespace ShopperSearchApiTypes {
          * @param options.parameters.expand - A comma-separated list with allowed values - `availability`, `images`, `prices`, `represented_products`, `variations`, `promotions`, `custom_properties`.
          By default, the expand parameter includes `availability, images, prices, represented_products, variations`.
          Use none to disable all expand options.
-         **The page_meta_tags expand value is optional and is available B2C Commerce version 25.2.**"
          * @param options.parameters.allImages - When the `images` expand parameter is used with this flag, the response includes the `imageGroups property`, which contains an image model.
          If this flag is true, the full image model is returned. If false, only matching images are included.
          If no flag is passed, the `imageGroups` property is omitted from the response.
@@ -52087,11 +53261,13 @@ declare namespace ShopperSearchApiTypes {
          * @param options.parameters - An object containing the parameters for this method.
          * @param options.parameters.organizationId - An identifier for the organization the request is being made by
          * @param options.parameters.siteId - The identifier of the site that a request is being made in the context of. Attributes might have site specific values, and some objects may only be assigned to specific sites.
-         * @param options.parameters.select - The property selector declaring which fields are included into the response payload. You can specify a single field name, a comma-separated list of names or work with wildcards. You can also specify array operations and filter expressions. The actual selector value must be enclosed within parentheses.
+         * @param options.parameters.select -
          * @param options.parameters.q - The query phrase to search for. For example to search for a product "shirt", type q=shirt.
-         * @param options.parameters.refine - Parameter that represents a refinement attribute or values pair. Refinement attribute ID and values are separated by '='. Multiple values are supported by a subset of refinement attributes and can be provided by separating them using a pipe (URL encoded = \"|\") i.e. refine=c_refinementColor=red|green|blue. Value ranges can be specified like this: refine=price=(100..500) .
-         Multiple refine parameters can be provided by using the refine as the key i.e refine=price=(0..10)&refine=c_refinementColor=green. The refinements can be a collection of custom defined attributes IDs
-         and the system defined attributes IDs but the search can only accept a total of 9 refinements at a time.
+         * @param options.parameters.refine - Parameter that represents a refinement attribute or values pair. Refinement attribute ID and values are separated by '='.<br>
+         Multiple values are supported by a subset of refinement attributes and can be provided by separating them using a pipe (URL encoded = \"|\"), for example: refine=c_refinementColor=red|green|blue.<br>
+         Value ranges can be specified like this: refine=price=(100..500).<br>
+         Multiple refine parameters can be provided by using the refine as the key, for example: refine=price=(0..10)&refine=c_refinementColor=green.<br>
+         The refinements can be a collection of custom defined attributes IDs and the system defined attributes IDs but the search can only accept a total of 9 refinements at a time.<br>
          
          The following system refinement attribute ids are supported:<br>
          `cgid`: Allows refinement per single category ID. Multiple category ids are not supported.
@@ -52113,7 +53289,6 @@ declare namespace ShopperSearchApiTypes {
          * @param options.parameters.expand - A comma-separated list with allowed values - `availability`, `images`, `prices`, `represented_products`, `variations`, `promotions`, `custom_properties`.
          By default, the expand parameter includes `availability, images, prices, represented_products, variations`.
          Use none to disable all expand options.
-         **The page_meta_tags expand value is optional and is available B2C Commerce version 25.2.**"
          * @param options.parameters.allImages - When the `images` expand parameter is used with this flag, the response includes the `imageGroups property`, which contains an image model.
          If this flag is true, the full image model is returned. If false, only matching images are included.
          If no flag is passed, the `imageGroups` property is omitted from the response.
@@ -53021,7 +54196,9 @@ type ShopperSEOParameters = ShopperSEOPathParameters & BaseUriParameters & Shopp
  * [Shopper SEO](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-seo:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-seo/shopper-seo-oas-v1-public.yaml)
+ 
+ # API Overview
  
  The Shopper SEO API Provides access to SEO-related information, such as URL mapping information.
  
@@ -53365,7 +54542,9 @@ declare namespace ShopperSEOApiTypes {
      * [Shopper SEO](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-seo:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-seo/shopper-seo-oas-v1-public.yaml)
+     
+     # API Overview
      
      The Shopper SEO API Provides access to SEO-related information, such as URL mapping information.
      
@@ -53758,7 +54937,9 @@ type ShopperStoresParameters = ShopperStoresPathParameters & BaseUriParameters &
  * [Shopper Stores](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-stores:Summary)
  * ==================================
  *
- * *# API Overview
+ * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-stores/shopper-stores-oas-v1-public.yaml)
+ 
+ # API Overview
  
  Provides access to stores via search or ID lookup.
  
@@ -54308,7 +55489,9 @@ declare namespace ShopperStoresApiTypes {
      * [Shopper Stores](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-stores:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-stores/shopper-stores-oas-v1-public.yaml)
+     
+     # API Overview
      
      Provides access to stores via search or ID lookup.
      
@@ -54956,6 +56139,12 @@ declare namespace helpers {
      * @property idp_access_token: This is the access token that is returned from the IDP. The IDP access token is returned to be able to make calls into the IDP outside of SLAS.
      * - **Max Length:** 8192
      *
+     * @property idp_refresh_token: This is the refresh token that is returned from the IDP. The IDP refresh token is returned to be able to make calls into the IDP outside of SLAS.
+     * - **Max Length:** 128
+     *
+     * @property dnt: Do not track
+     * - **Max Length:** 5
+     *
      */
     type TokenResponse = {
         access_token: string;
@@ -54968,6 +56157,8 @@ declare namespace helpers {
         customer_id: string;
         enc_user_id: string;
         idp_access_token: string;
+        idp_refresh_token?: string;
+        dnt?: string;
     } & {
         [key: string]: any;
     };
@@ -55055,6 +56246,7 @@ declare namespace helpers {
         pwdless_login_token: string;
         client_id?: string;
         code_verifier?: string;
+        login_id?: string;
     };
     type getPasswordResetTokenQueryParameters = {};
     type getPasswordResetTokenPathParameters = {
@@ -55194,7 +56386,9 @@ declare namespace helpers {
      * [Shopper Login](https://developer.salesforce.com/docs/commerce/commerce-api/references?meta=shopper-login:Summary)
      * ==================================
      *
-     * *# API Overview
+     * *[Download API specification](https://developer.salesforce.com/static/commercecloud/commerce-api/shopper-login/shopper-login-oas-v1-public.yaml)
+     
+     # API Overview
      
      The Shopper Login and API Access Service (SLAS) enables secure access to Commerce Cloud’s Shopper APIs for a wide range of headless commerce applications.
      
@@ -55330,7 +56524,8 @@ declare namespace helpers {
                 "hint",
                 "pwdless_login_token",
                 "client_id",
-                "code_verifier"
+                "code_verifier",
+                "login_id"
             ];
             readonly getPasswordLessAccessTokenRequired: readonly [
                 "organizationId",
@@ -55904,6 +57099,7 @@ declare namespace helpers {
          * @param options.body.pwdless_login_token - Passwordless login token that was created from the user ID.
          * @param options.body.client_id - The public client ID.
          * @param options.body.code_verifier - PKCE code verifier. Created by the client.  The `code_challenge` is created by SHA256 hashing the `code_verifier` and Base64 encoding the resulting hash.  The `code_verifier` should be a high entropy cryptographically random string with a minimum of 43 characters and a maximum of 128 characters.
+         * @param options.body.login_id - The ID used by the shopper for password token request. When provided, login_id must exactly match the ID used during passwordless login. ex. If passwordless login used `samantha.sampleson@example.com`, but the passwordless login token request provides `sam.sampleson@example.com`, the request fails due to mismatch.
          *
          * @returns A promise of type TokenResponse.
          */
@@ -55929,6 +57125,7 @@ declare namespace helpers {
          * @param options.body.pwdless_login_token - Passwordless login token that was created from the user ID.
          * @param options.body.client_id - The public client ID.
          * @param options.body.code_verifier - PKCE code verifier. Created by the client.  The `code_challenge` is created by SHA256 hashing the `code_verifier` and Base64 encoding the resulting hash.  The `code_verifier` should be a high entropy cryptographically random string with a minimum of 43 characters and a maximum of 128 characters.
+         * @param options.body.login_id - The ID used by the shopper for password token request. When provided, login_id must exactly match the ID used during passwordless login. ex. If passwordless login used `samantha.sampleson@example.com`, but the passwordless login token request provides `sam.sampleson@example.com`, the request fails due to mismatch.
          * @param rawResponse - Set to true to return entire Response object instead of DTO.
          *
          * @returns A promise of type Response if rawResponse is true, a promise of type TokenResponse otherwise.
@@ -56465,7 +57662,9 @@ declare namespace helpers {
          * @param options.parameters.client_id - The SLAS public client ID or SLAS private client ID for use with trusted-agent requests. When using a private client ID a PKCE code challenge is not required.
          * @param options.parameters.refresh_token - Refresh token that was given during the access token request.
          * @param options.parameters.channel_id - The `channel_id` parameter must be provided if the shopper authenticated using the `login` endpoint with B2C Commerce.
-         * @param options.parameters.hint - `hint=all-sessions` logs out all sessions of the shopper and invalidates all active refresh tokens for the shopper.
+         * @param options.parameters.hint - `hint=all-sessions` logs out all sessions and invalidates all refresh tokens for a shopper with the same SLAS user ID.
+         This only works within the same session type. Sessions created through different authentication methods (/authorize vs. Trusted System On Behalf) are treated as separate sessions. To invalidate tokens with different SLAS User IDs, you must make explicit logout calls with each token.
+         A shopper authenticated via both /authorize and TSOB has two separate sessions. You will need two logout calls (one per token) to fully log them out.
          
          If this query parameter is not provided, the default behavior is to log out only the current session that matches the refresh token in the request.
          
@@ -56499,7 +57698,9 @@ declare namespace helpers {
          * @param options.parameters.client_id - The SLAS public client ID or SLAS private client ID for use with trusted-agent requests. When using a private client ID a PKCE code challenge is not required.
          * @param options.parameters.refresh_token - Refresh token that was given during the access token request.
          * @param options.parameters.channel_id - The `channel_id` parameter must be provided if the shopper authenticated using the `login` endpoint with B2C Commerce.
-         * @param options.parameters.hint - `hint=all-sessions` logs out all sessions of the shopper and invalidates all active refresh tokens for the shopper.
+         * @param options.parameters.hint - `hint=all-sessions` logs out all sessions and invalidates all refresh tokens for a shopper with the same SLAS user ID.
+         This only works within the same session type. Sessions created through different authentication methods (/authorize vs. Trusted System On Behalf) are treated as separate sessions. To invalidate tokens with different SLAS User IDs, you must make explicit logout calls with each token.
+         A shopper authenticated via both /authorize and TSOB has two separate sessions. You will need two logout calls (one per token) to fully log them out.
          
          If this query parameter is not provided, the default behavior is to log out only the current session that matches the refresh token in the request.
          
@@ -57011,5 +58212,5 @@ declare namespace helpers {
      */
     const encodeSCAPISpecialCharacters: (str: string) => string;
 }
-export { ShopperBaskets, ShopperBasketsV2, ShopperConsents, ShopperContexts, ShopperCustomers, ShopperExperience, ShopperGiftCertificates, ShopperLogin, ShopperOrders, ShopperProducts, ShopperPromotions, ShopperSearch, ShopperSEO, ShopperStores, ClientConfig, TemplateURL, helpers };
-export type { ShopperBasketsTypes, ShopperBasketsV2Types, ShopperConsentsTypes, ShopperContextsTypes, ShopperCustomersTypes, ShopperExperienceTypes, ShopperGiftCertificatesTypes, ShopperLoginTypes, ShopperOrdersTypes, ShopperProductsTypes, ShopperPromotionsTypes, ShopperSearchTypes, ShopperSEOTypes, ShopperStoresTypes, ClientConfigInit, FetchFunction, FetchOptions };
+export { ShopperBaskets, ShopperBasketsV2, ShopperConfigurations, ShopperConsents, ShopperContexts, ShopperCustomers, ShopperExperience, ShopperGiftCertificates, ShopperLogin, ShopperOrders, ShopperProducts, ShopperPromotions, ShopperSearch, ShopperSEO, ShopperStores, ClientConfig, TemplateURL, helpers };
+export type { ShopperBasketsTypes, ShopperBasketsV2Types, ShopperConfigurationsTypes, ShopperConsentsTypes, ShopperContextsTypes, ShopperCustomersTypes, ShopperExperienceTypes, ShopperGiftCertificatesTypes, ShopperLoginTypes, ShopperOrdersTypes, ShopperProductsTypes, ShopperPromotionsTypes, ShopperSearchTypes, ShopperSEOTypes, ShopperStoresTypes, ClientConfigInit, FetchFunction, FetchOptions };