rebilly-js-sdk 62.141.1 → 62.142.0

package/CHANGELOG.md

@@ -1 +1,6 @@
-## [62.141.1](https://github.com/Rebilly/rebilly/compare/rebilly-js-sdk-v62.141.0...rebilly-js-sdk-v62.141.1) (2026-07-10)
+## [62.142.0](https://github.com/Rebilly/rebilly/compare/rebilly-js-sdk-v62.141.1...rebilly-js-sdk-v62.142.0) (2026-07-10)
+
+
+### Features
+
+* **api-metadata, rebilly-js-sdk:** Update resources based on latest api definitions ([#23471](https://github.com/Rebilly/rebilly/issues/23471)) ([adee1ff](https://github.com/Rebilly/rebilly/commit/adee1ff2d30478c923fc8fed19aefb5a3a0ebabe))

package/dist/rebilly-js-sdk.d.cts

@@ -22563,7 +22563,13 @@ export interface coreComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: coreComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: coreComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -28490,10 +28496,12 @@ export interface coreComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -61104,7 +61112,13 @@ export interface storefrontComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: storefrontComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: storefrontComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -67031,10 +67045,12 @@ export interface storefrontComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -87080,7 +87096,13 @@ export interface reportsComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: reportsComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: reportsComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -93007,10 +93029,12 @@ export interface reportsComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -98563,7 +98587,7 @@ declare module "resources/customers-resource" {
         }): rebilly.GetCustomerCreditBalanceResponsePromise;
         downloadComplianceScreeningReport({ id }: {
             id: any;
-        }): rebilly.GetCustomerComplianceScreeningReportResponsePromise;
+        }): any;
     };
 }
 declare module "resources/deposit-custom-property-sets-resource" {
@@ -100496,7 +100520,7 @@ declare module "resources/api-instance" {
             }): rebilly.GetCustomerCreditBalanceResponsePromise;
             downloadComplianceScreeningReport({ id }: {
                 id: any;
-            }): rebilly.GetCustomerComplianceScreeningReportResponsePromise;
+            }): any;
         };
         depositCustomPropertySets: {
             getAll({ limit, offset, filter, sort }?: rebilly.GetDepositCustomPropertySetCollectionRequest): rebilly.GetDepositCustomPropertySetCollectionResponsePromise;

package/dist/rebilly-js-sdk.d.mts

@@ -22563,7 +22563,13 @@ export interface coreComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: coreComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: coreComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -28490,10 +28496,12 @@ export interface coreComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -61104,7 +61112,13 @@ export interface storefrontComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: storefrontComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: storefrontComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -67031,10 +67045,12 @@ export interface storefrontComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -87080,7 +87096,13 @@ export interface reportsComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: reportsComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: reportsComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -93007,10 +93029,12 @@ export interface reportsComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -98563,7 +98587,7 @@ declare module "resources/customers-resource" {
         }): rebilly.GetCustomerCreditBalanceResponsePromise;
         downloadComplianceScreeningReport({ id }: {
             id: any;
-        }): rebilly.GetCustomerComplianceScreeningReportResponsePromise;
+        }): any;
     };
 }
 declare module "resources/deposit-custom-property-sets-resource" {
@@ -100496,7 +100520,7 @@ declare module "resources/api-instance" {
             }): rebilly.GetCustomerCreditBalanceResponsePromise;
             downloadComplianceScreeningReport({ id }: {
                 id: any;
-            }): rebilly.GetCustomerComplianceScreeningReportResponsePromise;
+            }): any;
         };
         depositCustomPropertySets: {
             getAll({ limit, offset, filter, sort }?: rebilly.GetDepositCustomPropertySetCollectionRequest): rebilly.GetDepositCustomPropertySetCollectionResponsePromise;

package/dist/rebilly-js-sdk.d.ts

@@ -22563,7 +22563,13 @@ export interface coreComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: coreComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: coreComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -28490,10 +28496,12 @@ export interface coreComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -61104,7 +61112,13 @@ export interface storefrontComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: storefrontComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: storefrontComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -67031,10 +67045,12 @@ export interface storefrontComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -87080,7 +87096,13 @@ export interface reportsComponents {
         | "canceled"
         | "split"
         | "merged";
-      /** Specifies whether the payout request is blocked or unblocked. */
+      /**
+       * Specifies whether the payout request is blocked or unblocked.
+       *
+       * When blocked, the payout request cannot transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
+       * Allocation creation, allocation processing, and cancellation of pending allocations are also prevented.
+       * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
+       */
       blocked?: boolean;
       blockReason?: reportsComponents["schemas"]["PayoutRequestBlockReason"] | null;
       splitReason?: reportsComponents["schemas"]["PayoutRequestSplitReason"] | null;
@@ -93007,10 +93029,12 @@ export interface reportsComponents {
            * `pending`, `ready`, `approved`, or `in-progress`.
            *
            * When a payout request is blocked, it cannot:
-           * - Move to the next status in the workflow.
-           *   For example: `pending` → `ready` → `approved` → `in-progress`.
+           * - Transition to `ready`, `approved`, `in-progress`, `merged`, `split`, or `canceled`.
            * - Have allocations created.
-           * - Have allocations processed.
+           * - Start allocation processing.
+           * - Cancel pending allocations.
+           *
+           * A blocked payout request can still transition to the `fulfilled` status if allocation processing starts before the payout request is blocked.
            */
           blocked?: boolean;
           blockReason?:
@@ -98563,7 +98587,7 @@ declare module "resources/customers-resource" {
         }): rebilly.GetCustomerCreditBalanceResponsePromise;
         downloadComplianceScreeningReport({ id }: {
             id: any;
-        }): rebilly.GetCustomerComplianceScreeningReportResponsePromise;
+        }): any;
     };
 }
 declare module "resources/deposit-custom-property-sets-resource" {
@@ -100496,7 +100520,7 @@ declare module "resources/api-instance" {
             }): rebilly.GetCustomerCreditBalanceResponsePromise;
             downloadComplianceScreeningReport({ id }: {
                 id: any;
-            }): rebilly.GetCustomerComplianceScreeningReportResponsePromise;
+            }): any;
         };
         depositCustomPropertySets: {
             getAll({ limit, offset, filter, sort }?: rebilly.GetDepositCustomPropertySetCollectionRequest): rebilly.GetDepositCustomPropertySetCollectionResponsePromise;