[nightly] generate types against bigcommerce/docs@7fe0389

src/generated/category-trees_catalog.v3.ts

@@ -29,7 +29,7 @@ export interface paths {
      * - 16,000 categories per store limit.
      * - 1,000 categories per product limit.
      * - 50 characters category name length.
-     * - 8 levels of category depth limit.
+     * - 8 levels of child categories depth limit.
      * - 65,535 characters category description length limit.
      *
      * Creating a category requires:
@@ -63,7 +63,7 @@ export interface paths {
      * This single endpoint updates and creates category trees. If a tree object contains an ID, it is processed as an update operation using that ID. If you do not provide an ID, a new tree is created. The category tree `name` field is required to create trees, but is not required on the update.
      *
      * **Usage Notes**
-     * * `channel_id` is required to create a category tree. You can assign one `channel_id` to one category tree.
+     * * Channel ID in the `channels` field is required to create a category tree. You can only assign a category tree to one channel.
      */
     put: operations["upsertCategoryTrees"];
     /**
@@ -590,7 +590,7 @@ export interface operations {
    * - 16,000 categories per store limit.
    * - 1,000 categories per product limit.
    * - 50 characters category name length.
-   * - 8 levels of category depth limit.
+   * - 8 levels of child categories depth limit.
    * - 65,535 characters category description length limit.
    *
    * Creating a category requires:
@@ -707,7 +707,7 @@ export interface operations {
    * This single endpoint updates and creates category trees. If a tree object contains an ID, it is processed as an update operation using that ID. If you do not provide an ID, a new tree is created. The category tree `name` field is required to create trees, but is not required on the update.
    *
    * **Usage Notes**
-   * * `channel_id` is required to create a category tree. You can assign one `channel_id` to one category tree.
+   * * Channel ID in the `channels` field is required to create a category tree. You can only assign a category tree to one channel.
    */
   upsertCategoryTrees: {
     parameters: {

src/generated/checkouts.v3.ts

@@ -1025,6 +1025,8 @@ export interface components {
       order_confirmation_use_custom_checkout_script?: boolean;
       custom_order_confirmation_script_url?: string;
       custom_checkout_supports_uco_settings?: boolean;
+      custom_checkout_sri_hash?: string;
+      custom_order_confirmation_sri_hash?: string;
     };
     /** Checkouts settings request */
     CheckoutsSettingsRequest: {
@@ -1036,6 +1038,10 @@ export interface components {
       custom_order_confirmation_script_url?: string;
       /** @description Boolean value that specifies whether this checkout supports Optimized One-Page Checkout settings. */
       custom_checkout_supports_uco_settings?: boolean;
+      /** @description The Subresource Integrity (SRI) hash for the custom checkout script URL. */
+      custom_checkout_sri_hash?: string;
+      /** @description The Subresource Integrity (SRI) hash for the custom order confirmation script URL. */
+      custom_order_confirmation_sri_hash?: string;
     };
     /** Pickup Option */
     PickupOption: {

src/generated/orders.v2.oas2.ts

@@ -1445,7 +1445,7 @@ export interface components {
        */
       base_wrapping_cost?: string;
       /**
-       * @description Shows where the order originated. The channel_id will default to 1.
+       * @description Shows where the order originated. The channel_id defaults to 1. The value must match the ID of a valid and enabled channel. If the ID refers to a non-existing or disconnected channel, the POST and PUT `/v2/orders` endpoints return a validation error.
        * @example 1
        */
       channel_id?: number;
@@ -2088,7 +2088,7 @@ export interface components {
       base_wrapping_cost?: string;
       billing_address?: components["schemas"]["billingAddress_Put"];
       /**
-       * @description Shows where the order originated. The channel_id will default to 1.
+       * @description Shows where the order originated. The channel_id defaults to 1. The value must match the ID of a valid and enabled channel. If the ID refers to a non-existing or disconnected channel, the POST and PUT `/v2/orders` endpoints return a validation error.
        * @example 1
        */
       channel_id?: number;