rebilly-js-sdk 62.181.0 → 62.182.1

package/CHANGELOG.md

@@ -1,5 +1,5 @@
-## 62.181.0 (2026-09-28)
+## 62.182.1 (2026-09-29)
 
-### Features
+### 🧱 Updated Dependencies
 
-- **api-metadata, rebilly-js-sdk:** Update resources based on latest api definitions ([#27368](https://github.com/Rebilly/rebilly/pull/27368))
+- Updated eslint-config to 4.30.3

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

@@ -12233,7 +12233,7 @@ export interface coreComponents {
        *
        * This is used in conjunction with the service period anchor to calculate
        * the time at which the invoice is issued. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       issueTimeShift?: {
         /** Sequential order of the billing time relative to the start of the service period. */
@@ -12248,9 +12248,9 @@ export interface coreComponents {
       /**
        * Calculation instruction of the invoice due time.
        *
-       * This is used in conjunction with the billing anchor to calculate when
+       * This is used in conjunction with the service period anchor to calculate when
        * an invoice is due for payment. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        *
        * The sequential order of due time shift is always after the due date.
        */
@@ -12495,7 +12495,7 @@ export interface coreComponents {
        * Use invoice time shift to adjust the invoice issue and due date when billing must occur before the service period changes.
        * For example, rent must be paid in advance,
        * so the invoice must be in advance of the billing date.
-       * For more information, see [Service period anchor, and billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       invoiceTimeShift?: coreComponents["schemas"]["InvoiceTimeShift"];
       createdTime?: coreComponents["schemas"]["CreatedTime"];
@@ -13626,16 +13626,6 @@ export interface coreComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: coreComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same recurring period length.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: coreComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -14628,15 +14618,15 @@ export interface coreComponents {
        * Amount of time between the pause end time and the renewal time in ISO-8601 durations format.
        * By default, this value is computed as the time between the pause and the renewal.
        *
-       * Example: A $30 per month subscription on a 30-day month is paused on day 20 of the order.
+       * Example: A $30 per month order on a 30-day month is paused on day 20.
        * There are 10 unused days on the order.
        * Therefore, the order renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the order uses a billing anchor,
+       * If a subscription item in the order uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: coreComponents["schemas"]["CreatedTime"];
@@ -14928,11 +14918,11 @@ export interface coreComponents {
        * There are 10 unused days on the subscription.
        * Therefore, the subscription renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the subscription uses a billing anchor,
+       * If the subscription uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: coreComponents["schemas"]["CreatedTime"];
@@ -26497,17 +26487,6 @@ export interface coreComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: coreComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same same recurring period length,
-       * this property enables the customer to subscribe to different plans.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: coreComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -51752,7 +51731,7 @@ export interface storefrontComponents {
        *
        * This is used in conjunction with the service period anchor to calculate
        * the time at which the invoice is issued. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       issueTimeShift?: {
         /** Sequential order of the billing time relative to the start of the service period. */
@@ -51767,9 +51746,9 @@ export interface storefrontComponents {
       /**
        * Calculation instruction of the invoice due time.
        *
-       * This is used in conjunction with the billing anchor to calculate when
+       * This is used in conjunction with the service period anchor to calculate when
        * an invoice is due for payment. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        *
        * The sequential order of due time shift is always after the due date.
        */
@@ -52014,7 +51993,7 @@ export interface storefrontComponents {
        * Use invoice time shift to adjust the invoice issue and due date when billing must occur before the service period changes.
        * For example, rent must be paid in advance,
        * so the invoice must be in advance of the billing date.
-       * For more information, see [Service period anchor, and billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       invoiceTimeShift?: storefrontComponents["schemas"]["InvoiceTimeShift"];
       createdTime?: storefrontComponents["schemas"]["CreatedTime"];
@@ -53145,16 +53124,6 @@ export interface storefrontComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: storefrontComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same recurring period length.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: storefrontComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -54147,15 +54116,15 @@ export interface storefrontComponents {
        * Amount of time between the pause end time and the renewal time in ISO-8601 durations format.
        * By default, this value is computed as the time between the pause and the renewal.
        *
-       * Example: A $30 per month subscription on a 30-day month is paused on day 20 of the order.
+       * Example: A $30 per month order on a 30-day month is paused on day 20.
        * There are 10 unused days on the order.
        * Therefore, the order renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the order uses a billing anchor,
+       * If a subscription item in the order uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: storefrontComponents["schemas"]["CreatedTime"];
@@ -54447,11 +54416,11 @@ export interface storefrontComponents {
        * There are 10 unused days on the subscription.
        * Therefore, the subscription renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the subscription uses a billing anchor,
+       * If the subscription uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: storefrontComponents["schemas"]["CreatedTime"];
@@ -66016,17 +65985,6 @@ export interface storefrontComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: storefrontComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same same recurring period length,
-       * this property enables the customer to subscribe to different plans.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: storefrontComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -78404,7 +78362,7 @@ export interface reportsComponents {
        *
        * This is used in conjunction with the service period anchor to calculate
        * the time at which the invoice is issued. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       issueTimeShift?: {
         /** Sequential order of the billing time relative to the start of the service period. */
@@ -78419,9 +78377,9 @@ export interface reportsComponents {
       /**
        * Calculation instruction of the invoice due time.
        *
-       * This is used in conjunction with the billing anchor to calculate when
+       * This is used in conjunction with the service period anchor to calculate when
        * an invoice is due for payment. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        *
        * The sequential order of due time shift is always after the due date.
        */
@@ -78666,7 +78624,7 @@ export interface reportsComponents {
        * Use invoice time shift to adjust the invoice issue and due date when billing must occur before the service period changes.
        * For example, rent must be paid in advance,
        * so the invoice must be in advance of the billing date.
-       * For more information, see [Service period anchor, and billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       invoiceTimeShift?: reportsComponents["schemas"]["InvoiceTimeShift"];
       createdTime?: reportsComponents["schemas"]["CreatedTime"];
@@ -79797,16 +79755,6 @@ export interface reportsComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: reportsComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same recurring period length.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: reportsComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -80799,15 +80747,15 @@ export interface reportsComponents {
        * Amount of time between the pause end time and the renewal time in ISO-8601 durations format.
        * By default, this value is computed as the time between the pause and the renewal.
        *
-       * Example: A $30 per month subscription on a 30-day month is paused on day 20 of the order.
+       * Example: A $30 per month order on a 30-day month is paused on day 20.
        * There are 10 unused days on the order.
        * Therefore, the order renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the order uses a billing anchor,
+       * If a subscription item in the order uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: reportsComponents["schemas"]["CreatedTime"];
@@ -81099,11 +81047,11 @@ export interface reportsComponents {
        * There are 10 unused days on the subscription.
        * Therefore, the subscription renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the subscription uses a billing anchor,
+       * If the subscription uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: reportsComponents["schemas"]["CreatedTime"];
@@ -92668,17 +92616,6 @@ export interface reportsComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: reportsComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same same recurring period length,
-       * this property enables the customer to subscribe to different plans.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: reportsComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,

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

@@ -12233,7 +12233,7 @@ export interface coreComponents {
        *
        * This is used in conjunction with the service period anchor to calculate
        * the time at which the invoice is issued. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       issueTimeShift?: {
         /** Sequential order of the billing time relative to the start of the service period. */
@@ -12248,9 +12248,9 @@ export interface coreComponents {
       /**
        * Calculation instruction of the invoice due time.
        *
-       * This is used in conjunction with the billing anchor to calculate when
+       * This is used in conjunction with the service period anchor to calculate when
        * an invoice is due for payment. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        *
        * The sequential order of due time shift is always after the due date.
        */
@@ -12495,7 +12495,7 @@ export interface coreComponents {
        * Use invoice time shift to adjust the invoice issue and due date when billing must occur before the service period changes.
        * For example, rent must be paid in advance,
        * so the invoice must be in advance of the billing date.
-       * For more information, see [Service period anchor, and billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       invoiceTimeShift?: coreComponents["schemas"]["InvoiceTimeShift"];
       createdTime?: coreComponents["schemas"]["CreatedTime"];
@@ -13626,16 +13626,6 @@ export interface coreComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: coreComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same recurring period length.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: coreComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -14628,15 +14618,15 @@ export interface coreComponents {
        * Amount of time between the pause end time and the renewal time in ISO-8601 durations format.
        * By default, this value is computed as the time between the pause and the renewal.
        *
-       * Example: A $30 per month subscription on a 30-day month is paused on day 20 of the order.
+       * Example: A $30 per month order on a 30-day month is paused on day 20.
        * There are 10 unused days on the order.
        * Therefore, the order renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the order uses a billing anchor,
+       * If a subscription item in the order uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: coreComponents["schemas"]["CreatedTime"];
@@ -14928,11 +14918,11 @@ export interface coreComponents {
        * There are 10 unused days on the subscription.
        * Therefore, the subscription renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the subscription uses a billing anchor,
+       * If the subscription uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: coreComponents["schemas"]["CreatedTime"];
@@ -26497,17 +26487,6 @@ export interface coreComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: coreComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same same recurring period length,
-       * this property enables the customer to subscribe to different plans.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: coreComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -51752,7 +51731,7 @@ export interface storefrontComponents {
        *
        * This is used in conjunction with the service period anchor to calculate
        * the time at which the invoice is issued. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       issueTimeShift?: {
         /** Sequential order of the billing time relative to the start of the service period. */
@@ -51767,9 +51746,9 @@ export interface storefrontComponents {
       /**
        * Calculation instruction of the invoice due time.
        *
-       * This is used in conjunction with the billing anchor to calculate when
+       * This is used in conjunction with the service period anchor to calculate when
        * an invoice is due for payment. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        *
        * The sequential order of due time shift is always after the due date.
        */
@@ -52014,7 +51993,7 @@ export interface storefrontComponents {
        * Use invoice time shift to adjust the invoice issue and due date when billing must occur before the service period changes.
        * For example, rent must be paid in advance,
        * so the invoice must be in advance of the billing date.
-       * For more information, see [Service period anchor, and billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       invoiceTimeShift?: storefrontComponents["schemas"]["InvoiceTimeShift"];
       createdTime?: storefrontComponents["schemas"]["CreatedTime"];
@@ -53145,16 +53124,6 @@ export interface storefrontComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: storefrontComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same recurring period length.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: storefrontComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -54147,15 +54116,15 @@ export interface storefrontComponents {
        * Amount of time between the pause end time and the renewal time in ISO-8601 durations format.
        * By default, this value is computed as the time between the pause and the renewal.
        *
-       * Example: A $30 per month subscription on a 30-day month is paused on day 20 of the order.
+       * Example: A $30 per month order on a 30-day month is paused on day 20.
        * There are 10 unused days on the order.
        * Therefore, the order renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the order uses a billing anchor,
+       * If a subscription item in the order uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: storefrontComponents["schemas"]["CreatedTime"];
@@ -54447,11 +54416,11 @@ export interface storefrontComponents {
        * There are 10 unused days on the subscription.
        * Therefore, the subscription renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the subscription uses a billing anchor,
+       * If the subscription uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: storefrontComponents["schemas"]["CreatedTime"];
@@ -66016,17 +65985,6 @@ export interface storefrontComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: storefrontComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same same recurring period length,
-       * this property enables the customer to subscribe to different plans.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: storefrontComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -78404,7 +78362,7 @@ export interface reportsComponents {
        *
        * This is used in conjunction with the service period anchor to calculate
        * the time at which the invoice is issued. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       issueTimeShift?: {
         /** Sequential order of the billing time relative to the start of the service period. */
@@ -78419,9 +78377,9 @@ export interface reportsComponents {
       /**
        * Calculation instruction of the invoice due time.
        *
-       * This is used in conjunction with the billing anchor to calculate when
+       * This is used in conjunction with the service period anchor to calculate when
        * an invoice is due for payment. For more information, see
-       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        *
        * The sequential order of due time shift is always after the due date.
        */
@@ -78666,7 +78624,7 @@ export interface reportsComponents {
        * Use invoice time shift to adjust the invoice issue and due date when billing must occur before the service period changes.
        * For example, rent must be paid in advance,
        * so the invoice must be in advance of the billing date.
-       * For more information, see [Service period anchor, and billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       invoiceTimeShift?: reportsComponents["schemas"]["InvoiceTimeShift"];
       createdTime?: reportsComponents["schemas"]["CreatedTime"];
@@ -79797,16 +79755,6 @@ export interface reportsComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: reportsComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same recurring period length.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: reportsComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,
@@ -80799,15 +80747,15 @@ export interface reportsComponents {
        * Amount of time between the pause end time and the renewal time in ISO-8601 durations format.
        * By default, this value is computed as the time between the pause and the renewal.
        *
-       * Example: A $30 per month subscription on a 30-day month is paused on day 20 of the order.
+       * Example: A $30 per month order on a 30-day month is paused on day 20.
        * There are 10 unused days on the order.
        * Therefore, the order renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the order uses a billing anchor,
+       * If a subscription item in the order uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: reportsComponents["schemas"]["CreatedTime"];
@@ -81099,11 +81047,11 @@ export interface reportsComponents {
        * There are 10 unused days on the subscription.
        * Therefore, the subscription renews in 10 days after it is resumed.
        * The upcoming invoice does not change the amount for the invoiced period, it remains at $30.
-       * If the subscription uses a billing anchor,
+       * If the subscription uses a service period anchor,
        * the renewal time after a pause shift behaves as though the renewal time is moved forward by an [Order API operation](https://www.rebilly.com/catalog/all/orders),
-       * and the billing anchor is ignored for that period.
+       * and the service period anchor is ignored for that period.
        *
-       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/concepts/#service-period-anchor-and-billing-timing-and-invoice-time-shift).
+       * For more information, see [Service period anchor, billing timing, and invoice time shift](https://www.rebilly.com/docs/dev-docs/subscriptions#service-period-anchor-billing-timing-and-invoice-time-shift).
        */
       timeRemaining?: string | null;
       createdTime?: reportsComponents["schemas"]["CreatedTime"];
@@ -92668,17 +92616,6 @@ export interface reportsComponents {
        * this property enables the customer to subscribe to different plans.
        */
       invoiceTimeShift?: reportsComponents["schemas"]["InvoiceTimeShift"];
-      /**
-       * Recurring interval to override plan settings.
-       * To use plan settings, set this value to `null`.
-       *
-       * To use multiple plans in one subscription,
-       * all plans must have the same same recurring period length,
-       * this property enables the customer to subscribe to different plans.
-       */
-      recurringInterval?: {
-        periodAnchorInstruction?: reportsComponents["schemas"]["ServicePeriodAnchorInstruction"];
-      } | null;
       /**
        * Specifies if payment attempts are made automatically.
        * If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at `paymentInstrumentId`,