lago-javascript-client 1.50.0 → 1.52.0

package/esm/openapi/webhooks.d.ts

@@ -1488,7 +1488,11 @@ export interface paths {
          */
         put: operations["updateInvoice"];
         post?: never;
-        delete?: never;
+        /**
+         * Delete a draft invoice
+         * @description This endpoint is used for permanently deleting a `draft` invoice. Deleting a draft invoice removes it entirely: it never becomes accounts receivable, consumes no invoice number, and disappears from every list, export, and analytics surface. Only invoices in the `draft` status can be deleted; for a `finalized` invoice, void it instead.
+         */
+        delete: operations["deleteInvoice"];
         options?: never;
         head?: never;
         patch?: never;
@@ -3634,6 +3638,26 @@ export interface webhooks {
         patch?: never;
         trace?: never;
     };
+    invoice_ready_to_finalize: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * A draft invoice is ready to be finalized
+         * @description A draft invoice is ready to be finalized (taxes are resolved). Sent when the draft invoice is created if no tax provider call is pending, or once the tax provider has returned taxes for the draft invoice.
+         */
+        post: operations["invoiceReadyToFinalize"];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     invoice_voided: {
         parameters: {
             query?: never;
@@ -3654,6 +3678,26 @@ export interface webhooks {
         patch?: never;
         trace?: never;
     };
+    invoice_deleted: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * A draft invoice has been deleted
+         * @description A draft invoice has been deleted
+         */
+        post: operations["invoiceDeleted"];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     invoice_payment_dispute_lost: {
         parameters: {
             query?: never;
@@ -6988,6 +7032,55 @@ export interface components {
             shipping_address?: components["schemas"]["Address"];
             metadata?: components["schemas"]["CustomerMetadata"][];
         };
+        /** @description Configuration specific to the accounting and tax integrations. This object contains settings and parameters necessary for syncing documents and payments. */
+        IntegrationCustomer: {
+            /**
+             * Format: uuid
+             * @description A unique identifier for the integration customer object in the Lago application.
+             * @example 1a901a90-1a90-1a90-1a90-1a901a901a90
+             */
+            lago_id: string;
+            /**
+             * @description The integration type used for accounting and tax syncs.
+             *     Accepted values: `netsuite, anrok`.
+             * @example netsuite
+             * @enum {string}
+             */
+            type: "netsuite" | "anrok" | "xero" | "hubspot" | "salesforce";
+            /**
+             * @description Unique code used to identify an integration connection.
+             * @example netsuite-eu-1
+             */
+            integration_code: string;
+            /**
+             * @description The customer ID within the integration's system. If this field is not provided, Lago has the option to create a new customer record within the integration's system on behalf of the customer.
+             * @example cus_12345
+             */
+            external_customer_id: string;
+            /**
+             * @description Set this field to `true` if you want to create a customer record in the integration's system. This option is applicable only when the `external_customer_id` is null and the `sync_with_provider` field is set to `true`. By default, the value is set to `false`
+             * @example true
+             */
+            sync_with_provider?: boolean | null;
+            /**
+             * @description This optional field is needed only when working with `netsuite` connection.
+             * @example 2
+             */
+            subsidiary_id?: string;
+            /**
+             * @description This optional field is present only when working with `hubspot` connection.
+             * @example contacts
+             */
+            targeted_object?: string | null;
+            /**
+             * @description This optional field is present only when working with `hubspot` connection.
+             * @example dinesh@piedpiper.test
+             */
+            email?: string | null;
+        };
+        CustomerObject: components["schemas"]["CustomerBaseObject"] & {
+            integration_customers?: components["schemas"]["IntegrationCustomer"][];
+        };
         /**
          * @description Custom metadata stored as key-value pairs.
          *     Keys are strings (max 100 characters), values can be strings (max 255 characters) or null.
@@ -7049,6 +7142,11 @@ export interface components {
              * @example LAG-1234
              */
             invoice_number: string;
+            /**
+             * @description The purchase order number of the invoice the credit note belongs to.
+             * @example PO-123
+             */
+            purchase_order_number?: string | null;
             /**
              * Format: date
              * @description The date of creation of the credit note. It follows the ISO 8601 date format and provides the specific date when the credit note was created.
@@ -7162,7 +7260,7 @@ export interface components {
              * @example false
              */
             self_billed?: boolean;
-            customer?: components["schemas"]["CustomerBaseObject"];
+            customer?: components["schemas"]["CustomerObject"];
             metadata?: components["schemas"]["MetadataObject"];
             error_details?: components["schemas"]["CreditNoteErrorDetailsObject"][] | null;
         };
@@ -7249,7 +7347,7 @@ export interface components {
             };
         };
         CreditNoteExtendedObject: components["schemas"]["CreditNoteObject"] & {
-            customer?: components["schemas"]["CustomerBaseObject"];
+            customer?: components["schemas"]["CustomerObject"];
         };
         CreditNoteExtended: {
             credit_note: components["schemas"]["CreditNoteExtendedObject"];
@@ -7441,55 +7539,6 @@ export interface components {
         CreditNoteMetadataResponse: {
             metadata: components["schemas"]["MetadataObject"];
         };
-        /** @description Configuration specific to the accounting and tax integrations. This object contains settings and parameters necessary for syncing documents and payments. */
-        IntegrationCustomer: {
-            /**
-             * Format: uuid
-             * @description A unique identifier for the integration customer object in the Lago application.
-             * @example 1a901a90-1a90-1a90-1a90-1a901a901a90
-             */
-            lago_id: string;
-            /**
-             * @description The integration type used for accounting and tax syncs.
-             *     Accepted values: `netsuite, anrok`.
-             * @example netsuite
-             * @enum {string}
-             */
-            type: "netsuite" | "anrok" | "xero" | "hubspot" | "salesforce";
-            /**
-             * @description Unique code used to identify an integration connection.
-             * @example netsuite-eu-1
-             */
-            integration_code: string;
-            /**
-             * @description The customer ID within the integration's system. If this field is not provided, Lago has the option to create a new customer record within the integration's system on behalf of the customer.
-             * @example cus_12345
-             */
-            external_customer_id: string;
-            /**
-             * @description Set this field to `true` if you want to create a customer record in the integration's system. This option is applicable only when the `external_customer_id` is null and the `sync_with_provider` field is set to `true`. By default, the value is set to `false`
-             * @example true
-             */
-            sync_with_provider?: boolean | null;
-            /**
-             * @description This optional field is needed only when working with `netsuite` connection.
-             * @example 2
-             */
-            subsidiary_id?: string;
-            /**
-             * @description This optional field is present only when working with `hubspot` connection.
-             * @example contacts
-             */
-            targeted_object?: string | null;
-            /**
-             * @description This optional field is present only when working with `hubspot` connection.
-             * @example dinesh@piedpiper.test
-             */
-            email?: string | null;
-        };
-        CustomerObject: components["schemas"]["CustomerBaseObject"] & {
-            integration_customers?: components["schemas"]["IntegrationCustomer"][];
-        };
         ErrorDetailObject: {
             /**
              * Format: uuid
@@ -7581,7 +7630,7 @@ export interface components {
                  */
                 logo_url?: string | null;
                 /**
-                 * @description The full name of the customer
+                 * @description The full name of the customer (255 characters max).
                  * @example Gavin Belson
                  */
                 name?: string | null;
@@ -7752,6 +7801,11 @@ export interface components {
              * @example LAG-1234-001-002
              */
             number: string;
+            /**
+             * @description The purchase order number associated with the invoice. It is inherited from the subscription, wallet or wallet transaction the invoice was generated for.
+             * @example PO-123
+             */
+            purchase_order_number?: string | null;
             /**
              * Format: date
              * @description The date when the invoice was issued. It is provided in the ISO 8601 date format.
@@ -7793,10 +7847,11 @@ export interface components {
              *     - `voided`: the invoice has been issued and subsequently voided. In this state, events cannot be ingested or added to the invoice anymore.
              *     - `pending`: the invoice remains pending until the taxes are fetched from the external provider.
              *     - `failed`: during an attempt of finalization of the invoice, an error happened. This invoice will have an array of error_details, explaining, in which part of the system an error happened and how it's possible to fix it. This invoice can't be edited or updated, only retried. This action will discard current error_details and will create new ones if the finalization failed again.
+             *     - `deleted`: the draft invoice has been permanently deleted. This status is only returned by the delete endpoint and its webhook; a deleted invoice is no longer retrievable afterwards.
              * @example finalized
              * @enum {string}
              */
-            status: "draft" | "finalized" | "voided" | "failed" | "pending";
+            status: "draft" | "finalized" | "voided" | "failed" | "pending" | "deleted";
             /**
              * @description The status of the payment associated with the invoice. It can have one of the following values:
              *     - `pending`: the payment is pending, waiting for payment processing in Stripe or when the invoice is emitted but users have not updated the payment status through the endpoint.
@@ -7887,6 +7942,12 @@ export interface components {
              * @example https://getlago.com/invoice/file
              */
             file_url?: string;
+            /**
+             * Format: uri
+             * @description Contains the URL to the invoice page in the Lago dashboard. It is `null` for invoices that are not visible in the dashboard (for example while still generating). Use it to link users directly to the invoice overview page.
+             * @example https://app.getlago.com/acme/customer/1a901a90-1a90-1a90-1a90-1a901a901a90/invoice/2b012b01-2b01-2b01-2b01-2b012b012b01/overview
+             */
+            web_url?: string | null;
             /**
              * Format: date-time
              * @description The date of the invoice creation, represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC). The creation_date provides a standardized and internationally recognized timestamp for when the invoice object was created
@@ -7913,7 +7974,7 @@ export interface components {
              */
             key?: string;
             /**
-             * @description Represents the value of the metadata's key-value pair.
+             * @description Represents the value of the metadata's key-value pair (140 characters max).
              * @example INV-0123456-98765
              */
             value?: string;
@@ -8460,14 +8521,15 @@ export interface components {
              */
             consolidate_invoice: boolean;
             /**
-             * @description The reason a payment-gated subscription was canceled before activation. Null unless the subscription was canceled by payment gating.
+             * @description The reason a payment-gated subscription was canceled while still `incomplete`. Null unless the subscription was canceled before activation.
              *
              *     - `payment_failed`: the gating payment failed.
              *     - `timeout`: the activation rule expired before the payment succeeded.
+             *     - `manual`: the incomplete subscription was canceled on demand, via a terminate request with `status=incomplete`.
              * @example payment_failed
              * @enum {string|null}
              */
-            cancellation_reason?: "payment_failed" | "timeout" | null;
+            cancellation_reason?: "payment_failed" | "timeout" | "manual" | null;
             /**
              * Format: date-time
              * @description The date and time when a payment-gated subscription was activated (i.e. moved from `incomplete` to `active` once the gating payment succeeded), represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC). Null while the subscription is still `incomplete`.
@@ -8476,11 +8538,25 @@ export interface components {
             activated_at?: string | null;
             /** @description The activation rules attached to the subscription. A payment activation rule gates activation on a successful first payment, keeping the subscription in the `incomplete` state until the payment succeeds or the rule expires. */
             activation_rules?: components["schemas"]["SubscriptionActivationRuleObject"][];
+            /**
+             * @description The purchase order number associated with the subscription. It will be added to invoices generated for this subscription.
+             * @example PO-123
+             */
+            purchase_order_number?: string | null;
         };
         SubscriptionsPaginated: {
             subscriptions: components["schemas"]["SubscriptionObject"][];
             meta: components["schemas"]["PaginationMeta"];
         };
+        /**
+         * @description Fee type to which a wallet can be restricted. It can be any of the following values:
+         *       - `charge`
+         *       - `subscription`
+         *       - `commitment`
+         *       - `fixed_charge`
+         * @enum {string}
+         */
+        WalletFeeTypeEnum: "charge" | "subscription" | "commitment" | "fixed_charge";
         /** @description Object that represents rule for wallet recurring transactions. */
         WalletRecurringTransactionRule: {
             /**
@@ -8594,6 +8670,11 @@ export interface components {
             applied_invoice_custom_sections?: components["schemas"]["AppliedInvoiceCustomSectionObject"][];
             /** @description The payment method assigned to this recurring transaction rule for processing top-up payments. */
             payment_method?: components["schemas"]["PaymentMethodReference"];
+            /**
+             * @description The purchase order number associated with this recurring transaction rule. It will be added to invoices generated for the resulting wallet top-ups. If not set, falls back to the wallet's `purchase_order_number`.
+             * @example PO-123
+             */
+            purchase_order_number?: string | null;
         };
         WalletObject: {
             /**
@@ -8707,7 +8788,7 @@ export interface components {
                  *       "charge"
                  *     ]
                  */
-                fee_types?: ("charge" | "subscription" | "commitment")[];
+                fee_types?: components["schemas"]["WalletFeeTypeEnum"][];
                 /**
                  * @description An array of billable metric codes to which the wallet is applicable. By specifying the billable metric codes in this field, you can restrict the wallet's usage to specific metrics only.
                  * @example [
@@ -8752,6 +8833,11 @@ export interface components {
             applied_invoice_custom_sections?: components["schemas"]["AppliedInvoiceCustomSectionObject"][];
             /** @description The payment method assigned to this wallet for processing top-up payments. */
             payment_method?: components["schemas"]["PaymentMethodReference"];
+            /**
+             * @description The purchase order number associated with the wallet. It will be added to invoices generated for wallet top-ups, unless a more specific purchase order number is set on the wallet transaction or recurring transaction rule that triggered the top-up.
+             * @example PO-123
+             */
+            purchase_order_number?: string | null;
             metadata?: components["schemas"]["MetadataObject"];
         };
         WalletsPaginated: {
@@ -8855,6 +8941,11 @@ export interface components {
                  * @example Tokens for models 'high-fidelity-boost'
                  */
                 transaction_name?: string | null;
+                /**
+                 * @description The purchase order number associated with the wallet. It will be added to invoices generated for wallet top-ups, unless a more specific purchase order number is set on the wallet transaction or recurring transaction rule that triggered the top-up.
+                 * @example PO-123
+                 */
+                purchase_order_number?: string | null;
                 /** @description Set wallet limitations to fee types. */
                 applies_to?: {
                     /**
@@ -8863,7 +8954,7 @@ export interface components {
                      *       "charge"
                      *     ]
                      */
-                    fee_types?: ("charge" | "subscription" | "commitment")[] | null;
+                    fee_types?: components["schemas"]["WalletFeeTypeEnum"][] | null;
                     /**
                      * @description An array of billable metric codes to which the wallet is applicable. By specifying the billable metric codes in this field, you can restrict the wallet's usage to specific metrics only.
                      * @example []
@@ -8972,6 +9063,11 @@ export interface components {
                      * @example Tokens for models 'high-fidelity-boost'
                      */
                     transaction_name?: string | null;
+                    /**
+                     * @description The purchase order number associated with this recurring transaction rule. It will be added to invoices generated for the resulting wallet top-ups. If not set, falls back to the wallet's `purchase_order_number`.
+                     * @example PO-123
+                     */
+                    purchase_order_number?: string | null;
                     /**
                      * @description When true, allows rule to topped up wallet with transactions that exceed the paid top-up limits. Defaults to false.
                      * @example false
@@ -9022,6 +9118,11 @@ export interface components {
                  * @example default
                  */
                 billing_entity_code?: string;
+                /**
+                 * @description The purchase order number associated with the wallet. It will be added to invoices generated for wallet top-ups, unless a more specific purchase order number is set on the wallet transaction or recurring transaction rule that triggered the top-up.
+                 * @example PO-123
+                 */
+                purchase_order_number?: string | null;
                 invoice_custom_section?: components["schemas"]["InvoiceCustomSectionInput"];
                 /** @description List of recurring transaction rules. Currently, we only allow one recurring rule per wallet. */
                 recurring_transaction_rules?: {
@@ -9115,6 +9216,11 @@ export interface components {
                      * @example Tokens for models 'high-fidelity-boost'
                      */
                     transaction_name?: string | null;
+                    /**
+                     * @description The purchase order number associated with this recurring transaction rule. It will be added to invoices generated for the resulting wallet top-ups. If not set, falls back to the wallet's `purchase_order_number`.
+                     * @example PO-123
+                     */
+                    purchase_order_number?: string | null;
                     invoice_custom_section?: components["schemas"]["InvoiceCustomSectionInput"];
                     /** @description Optional payment method to use for processing recurring top-up payments. */
                     payment_method?: components["schemas"]["PaymentMethodReference"];
@@ -9129,7 +9235,7 @@ export interface components {
                      *       "charge"
                      *     ]
                      */
-                    fee_types?: ("charge" | "subscription" | "commitment")[] | null;
+                    fee_types?: components["schemas"]["WalletFeeTypeEnum"][] | null;
                     /**
                      * @description An array of billable metric codes to which the wallet is applicable. By specifying the billable metric codes in this field, you can restrict the wallet's usage to specific metrics only.
                      * @example []
@@ -10233,6 +10339,11 @@ export interface components {
                  * @example EUR
                  */
                 currency?: components["schemas"]["Currency"];
+                /**
+                 * @description The purchase order number to associate with the invoice.
+                 * @example PO-123
+                 */
+                purchase_order_number?: string | null;
                 fees: {
                     /**
                      * @description The code of the add-on used as invoice item.
@@ -10364,7 +10475,7 @@ export interface components {
                      */
                     key?: string;
                     /**
-                     * @description The value in the key-value pair of the metadata.
+                     * @description The value in the key-value pair of the metadata (140 characters max).
                      * @example INV-0123456-98765
                      */
                     value?: string;
@@ -12998,7 +13109,10 @@ export interface components {
                 /** @description List of taxes applied to the fixed charge. */
                 tax_codes?: components["schemas"]["TaxCodes"];
             }[];
-            /** @description List of usage thresholds applied to the subscription. */
+            /**
+             * @deprecated
+             * @description **Deprecated.** Managing usage thresholds through `plan_overrides` is deprecated and its behavior is inconsistent: an empty array does not reliably clear thresholds (it is ignored the first time a subscription is overridden), and it never affects thresholds inherited from a parent plan. Use the top-level `usage_thresholds` array on the subscription instead, or `progressive_billing_disabled` to switch progressive billing off.
+             */
             usage_thresholds?: components["schemas"]["UsageThresholdInput"][];
             metadata?: components["schemas"]["MetadataInput"];
         };
@@ -13095,6 +13209,25 @@ export interface components {
                  * @example true
                  */
                 consolidate_invoice: boolean;
+                /**
+                 * @description The purchase order number associated with the subscription. It will be added to invoices generated for this subscription.
+                 * @example PO-123
+                 */
+                purchase_order_number?: string | null;
+                /**
+                 * @description Disables progressive billing for this subscription, regardless of any usage thresholds defined on the plan (including thresholds inherited from a parent plan when the subscription runs on a plan override).
+                 *
+                 *     Set to `true` to switch progressive billing off for this subscription specifically, without changing the plan's thresholds.
+                 * @default false
+                 * @example true
+                 */
+                progressive_billing_disabled: boolean;
+                /**
+                 * @description Usage thresholds managed directly on the subscription. This is the recommended way to set progressive billing thresholds per subscription; when present, they take precedence over the thresholds defined on the plan.
+                 *
+                 *     This field cannot be combined with `plan_overrides.usage_thresholds` in the same request.
+                 */
+                usage_thresholds?: components["schemas"]["UsageThresholdInput"][];
                 /** @description Optional list of activation rules that gate the subscription activation. When a `payment` rule is provided and the plan is paid in advance (and the subscription is not in a trial), the subscription is created in the `incomplete` state and is only activated once the gating payment succeeds. If the payment fails or the rule's `timeout_hours` elapses, the subscription is canceled. */
                 activation_rules?: components["schemas"]["SubscriptionActivationRuleInput"][];
             };
@@ -13167,6 +13300,25 @@ export interface components {
                  * @example default
                  */
                 billing_entity_code?: string;
+                /**
+                 * @description The purchase order number associated with the subscription. It will be added to invoices generated for this subscription.
+                 * @example PO-123
+                 */
+                purchase_order_number?: string | null;
+                /**
+                 * @description Disables progressive billing for this subscription, regardless of any usage thresholds defined on the plan (including thresholds inherited from a parent plan when the subscription runs on a plan override).
+                 *
+                 *     Set to `true` to switch progressive billing off for this subscription specifically. This is the recommended way to stop progressive billing on a subscription that inherits thresholds from its plan, since clearing `usage_thresholds` only removes subscription-level thresholds and does not remove those defined on (or inherited from) the plan.
+                 * @default false
+                 * @example true
+                 */
+                progressive_billing_disabled: boolean;
+                /**
+                 * @description Usage thresholds managed directly on the subscription. This is the recommended way to set progressive billing thresholds per subscription; when present, they take precedence over the thresholds defined on the plan.
+                 *
+                 *     Sending an empty array removes all subscription-level thresholds. This field cannot be combined with `plan_overrides.usage_thresholds` in the same request. To fully disable progressive billing on a subscription that inherits thresholds from its plan, use `progressive_billing_disabled` instead.
+                 */
+                usage_thresholds?: components["schemas"]["UsageThresholdInput"][];
                 /** @description Optional list of activation rules that gate the subscription activation. Activation rules can only be set or modified while the subscription is `pending` (future-dated and not yet activated); the request is rejected for `incomplete`, `active`, or `terminated` subscriptions. */
                 activation_rules?: components["schemas"]["SubscriptionActivationRuleInput"][];
             };
@@ -13556,6 +13708,11 @@ export interface components {
                  * @example false
                  */
                 ignore_paid_top_up_limits?: boolean;
+                /**
+                 * @description The purchase order number associated with this wallet transaction. It will be added to invoices generated for the resulting wallet top-up. If not set, falls back to the wallet's `purchase_order_number`.
+                 * @example PO-123
+                 */
+                purchase_order_number?: string | null;
                 invoice_custom_section?: components["schemas"]["InvoiceCustomSectionInput"];
                 /** @description Optional payment method to use for processing the wallet transaction payment. */
                 payment_method?: components["schemas"]["PaymentMethodReference"];
@@ -13711,6 +13868,11 @@ export interface components {
             applied_invoice_custom_sections?: components["schemas"]["AppliedInvoiceCustomSectionObject"][];
             /** @description The payment method assigned to this wallet transaction for processing the payment. */
             payment_method: components["schemas"]["PaymentMethodReference"];
+            /**
+             * @description The purchase order number associated with this wallet transaction. It will be added to invoices generated for the resulting wallet top-up. If not set, falls back to the wallet's `purchase_order_number`.
+             * @example PO-123
+             */
+            purchase_order_number?: string | null;
         };
         WalletTransactions: {
             wallet_transactions: components["schemas"]["WalletTransactionObject"][];
@@ -13834,8 +13996,8 @@ export interface components {
              */
             lago_organization_id: string;
             /**
-             * @description The name of the wallet.
-             * @example Prepaid
+             * @description The URL of the webhook endpoint.
+             * @example https://foo.bar
              */
             webhook_url: string;
             /**
@@ -13844,6 +14006,19 @@ export interface components {
              * @enum {string}
              */
             signature_algo?: "jwt" | "hmac";
+            /**
+             * @description The name of the webhook.
+             * @example EC2-production
+             */
+            name?: string | null;
+            /**
+             * @description A list of event types that will trigger the webhook. Passing null means that all event types will be sent.
+             * @example [
+             *       "invoice.voided",
+             *       "customer.created"
+             *     ]
+             */
+            event_types?: string[] | null;
             /**
              * Format: date-time
              * @description The date of the webhook endpoint creation, represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
@@ -13868,6 +14043,19 @@ export interface components {
                  * @enum {string|null}
                  */
                 signature_algo?: "jwt" | "hmac" | null;
+                /**
+                 * @description The name of the webhook.
+                 * @example EC2-production
+                 */
+                name?: string | null;
+                /**
+                 * @description A list of event types that will trigger the webhook. Passing null means that all event types will be sent.
+                 * @example [
+                 *       "invoice.voided",
+                 *       "customer.created"
+                 *     ]
+                 */
+                event_types?: string[] | null;
             };
         };
         WebhookEndpoint: {
@@ -13886,6 +14074,19 @@ export interface components {
                  * @enum {string|null}
                  */
                 signature_algo?: "jwt" | "hmac" | null;
+                /**
+                 * @description The name of the webhook.
+                 * @example EC2-production
+                 */
+                name?: string | null;
+                /**
+                 * @description A list of event types that will trigger the webhook. Passing null means that all event types will be sent.
+                 * @example [
+                 *       "invoice.voided",
+                 *       "customer.created"
+                 *     ]
+                 */
+                event_types?: string[] | null;
             };
         };
         TriggeredAlertObject: {
@@ -14455,6 +14656,8 @@ export interface components {
         external_subscription_id: string;
         /** @description Show data only for given number of months. */
         months: number;
+        /** @description Filter by the invoice purchase order number. The match is exact but case-insensitive. */
+        purchase_order_number: string;
         /** @description The customer external unique identifier (provided by your own application) */
         external_customer_id_path: string;
         /** @description Filter by payment status. Possible values are `pending`, `failed` or `succeeded`. */
@@ -15617,6 +15820,8 @@ export interface operations {
                 refund_status?: "pending" | "succeeded" | "failed";
                 /** @description Filter credit notes by their related invoice number. */
                 invoice_number?: string;
+                /** @description Filter by the invoice purchase order number. The match is exact but case-insensitive. */
+                purchase_order_number?: components["parameters"]["purchase_order_number"];
                 /** @description Filter credit notes of at least a specific amount. This parameter must be defined in cents to ensure consistent handling for all currency types. */
                 amount_from?: number;
                 /** @description Filter credit notes up to a specific amount. This parameter must be defined in cents to ensure consistent handling for all currency types. */
@@ -16128,6 +16333,8 @@ export interface operations {
                 refund_status?: "pending" | "succeeded" | "failed";
                 /** @description Filter credit notes by their related invoice number. */
                 invoice_number?: string;
+                /** @description Filter by the invoice purchase order number. The match is exact but case-insensitive. */
+                purchase_order_number?: components["parameters"]["purchase_order_number"];
                 /** @description Filter credit notes of at least a specific amount. This parameter must be defined in cents to ensure consistent handling for all currency types. */
                 amount_from?: number;
                 /** @description Filter credit notes up to a specific amount. This parameter must be defined in cents to ensure consistent handling for all currency types. */
@@ -16188,6 +16395,8 @@ export interface operations {
                 self_billed?: boolean;
                 /** @description Filter invoices by metadata. Replace `key` with the actual metadata key you want to match, and provide the corresponding value. Providing empty value will search for invoice without given metadata key. For example, `metadata[color]=blue`. */
                 "metadata[key]"?: string;
+                /** @description Filter by the invoice purchase order number. The match is exact but case-insensitive. */
+                purchase_order_number?: components["parameters"]["purchase_order_number"];
             };
             header?: never;
             path: {
@@ -17435,6 +17644,8 @@ export interface operations {
                 "billing_entity_codes[]"?: string[];
                 /** @description Filter invoices by metadata. Replace `key` with the actual metadata key you want to match, and provide the corresponding value. Providing empty value will search for invoice without given metadata key. For example, `metadata[color]=blue`. */
                 "metadata[key]"?: string;
+                /** @description Filter by the invoice purchase order number. The match is exact but case-insensitive. */
+                purchase_order_number?: components["parameters"]["purchase_order_number"];
             };
             header?: never;
             path?: never;
@@ -17539,6 +17750,32 @@ export interface operations {
             422: components["responses"]["UnprocessableEntity"];
         };
     };
+    deleteInvoice: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                /** @description Unique identifier assigned to the invoice within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the invoice's record within the Lago system. */
+                lago_id: components["parameters"]["lago_invoice_id"];
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Invoice deleted */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["Invoice"];
+                };
+            };
+            401: components["responses"]["Unauthorized"];
+            404: components["responses"]["NotFound"];
+            405: components["responses"]["NotAllowed"];
+        };
+    };
     downloadInvoice: {
         parameters: {
             query?: never;
@@ -19061,7 +19298,12 @@ export interface operations {
     destroySubscription: {
         parameters: {
             query?: {
-                /** @description If the field is not defined, Lago will terminate only `active` subscriptions. However, if you wish to cancel a `pending` subscription, please ensure that you include `status=pending` in your request. */
+                /**
+                 * @description Selects which subscription to terminate for the given `external_id`, based on its status. If the field is not defined, Lago targets only `active` subscriptions.
+                 *
+                 *     - `pending`: cancel a subscription scheduled for a future activation (include `status=pending`).
+                 *     - `incomplete`: cancel a payment-gated subscription that is still awaiting its activation payment (include `status=incomplete`). The subscription is canceled with `cancellation_reason: manual`, its invoice is closed and nothing is billed, and any pending payment is canceled on a best-effort basis with the payment provider (some provider statuses cannot be canceled). Applied coupons, credit notes and wallet credits are recredited. Termination behaviours (`on_termination_credit_note`, `on_termination_invoice`) are ignored, as an incomplete subscription has never been billed.
+                 */
                 status?: string;
                 /**
                  * @description When a pay-in-advance subscription is terminated before the end of its billing period, we generate a credit note for the unused subscription time by default.
@@ -21976,6 +22218,48 @@ export interface operations {
             };
         };
     };
+    invoiceReadyToFinalize: {
+        parameters: {
+            query?: never;
+            header: {
+                /** @description Signature of the webhook payload */
+                "X-Lago-Signature": components["parameters"]["webhook_signature"];
+                /** @description Algorithm used to generate the signature */
+                "X-Lago-Signature-Algorithm": components["parameters"]["webhook_signature_algorithm"];
+                /** @description Unique id of the webhook. It can be used for idempotency */
+                "X-Lago-Unique-Key": components["parameters"]["webhook_unique_key"];
+            };
+            path?: never;
+            cookie?: never;
+        };
+        /** @description Details of the draft invoice ready to be finalized */
+        requestBody?: {
+            content: {
+                "application/json": {
+                    /** @enum {string} */
+                    webhook_type: "invoice.ready_to_finalize";
+                    /** @enum {string} */
+                    object_type: "invoice";
+                    /**
+                     * Format: uuid
+                     * @description Unique identifier of the organization, created by Lago.
+                     * @example 1a901a90-1a90-1a90-1a90-1a901a901a90
+                     */
+                    organization_id: string;
+                    invoice: components["schemas"]["InvoiceObjectExtended"];
+                };
+            };
+        };
+        responses: {
+            /** @description Return a 200 status to indicate that the data was received successfully */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content?: never;
+            };
+        };
+    };
     invoiceVoided: {
         parameters: {
             query?: never;
@@ -22018,6 +22302,48 @@ export interface operations {
             };
         };
     };
+    invoiceDeleted: {
+        parameters: {
+            query?: never;
+            header: {
+                /** @description Signature of the webhook payload */
+                "X-Lago-Signature": components["parameters"]["webhook_signature"];
+                /** @description Algorithm used to generate the signature */
+                "X-Lago-Signature-Algorithm": components["parameters"]["webhook_signature_algorithm"];
+                /** @description Unique id of the webhook. It can be used for idempotency */
+                "X-Lago-Unique-Key": components["parameters"]["webhook_unique_key"];
+            };
+            path?: never;
+            cookie?: never;
+        };
+        /** @description Details of the invoice */
+        requestBody?: {
+            content: {
+                "application/json": {
+                    /** @enum {string} */
+                    webhook_type: "invoice.deleted";
+                    /** @enum {string} */
+                    object_type: "invoice";
+                    /**
+                     * Format: uuid
+                     * @description Unique identifier of the organization, created by Lago.
+                     * @example 1a901a90-1a90-1a90-1a90-1a901a901a90
+                     */
+                    organization_id: string;
+                    invoice: components["schemas"]["InvoiceObjectExtended"];
+                };
+            };
+        };
+        responses: {
+            /** @description Return a 200 status to indicate that the data was received successfully */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content?: never;
+            };
+        };
+    };
     invoicePaymentDisputeLost: {
         parameters: {
             query?: never;