lago-javascript-client 1.33.3 → 1.36.0

package/esm/openapi/client.d.ts

@@ -2093,6 +2093,11 @@ export interface FeeObject {
      * @example "312.5"
      */
     precise_unit_amount: string;
+    /**
+     * The total number of units that have been aggregated for this specific fee.
+     * @example "0.32"
+     */
+    total_aggregated_units: string;
     /**
      * The cost of this specific fee, including any applicable taxes.
      * @example 120
@@ -2240,7 +2245,7 @@ export interface FeeObject {
          */
         lago_item_id: string;
         /**
-         * The type of the fee item. Possible values are `AddOn`, `BillableMetric`, `WalletTransaction`, `Subscription` or `Commitment`.
+         * The type of the fee item. Possible values are `AddOn`, `BillableMetric`, `WalletTransaction`, `Subscription`.
          * @example "Subscription"
          */
         item_type: "AddOn" | "BillableMetric" | "Subscription" | "WalletTransaction";
@@ -3195,1169 +3200,1574 @@ export interface CustomerCreateInput {
 export interface Customer {
     customer: CustomerObjectExtended;
 }
-/** Details about the pricing unit used for charge usage. */
-export interface UsagePricingUnitDetailsObject {
+export interface InvoiceBaseObject {
     /**
-     * The amount in cents in the pricing unit.
-     * @example 200
+     * Unique identifier assigned to the fee within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the fee's record within the Lago system.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    amount_cents: number;
+    lago_id: string;
     /**
-     * The short name of the pricing unit.
-     * @example "CR"
+     * The unique code of the billing entity associated with the invoice
+     * @example "acme_corp"
      */
-    short_name: string;
+    billing_entity_code: string | null;
     /**
-     * The conversion rate from pricing units to the plan's currency.
-     * @example "0.5"
+     * This ID helps in uniquely identifying and organizing the invoices associated with a specific customer. It provides a sequential numbering system specific to the customer, allowing for easy tracking and management of invoices within the customer's context.
+     * @example 2
      */
-    conversion_rate: string;
-}
-/** Array of filter object, representing multiple dimensions for a charge item. */
-export type CustomerChargeFiltersUsageObject = {
+    sequential_id?: number;
     /**
-     * The number of units consumed for a specific charge filter related to a charge item.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "0.9"
+     * The unique number assigned to the invoice. This number serves as a distinct identifier for the invoice and helps in differentiating it from other invoices in the system.
+     * @example "LAG-1234-001-002"
      */
-    units?: string;
+    number: string;
     /**
-     * The amount in cents, tax excluded, consumed for a specific charge filter related to a charge item.
-     * @example 1000
+     * The date when the invoice was issued. It is provided in the ISO 8601 date format.
+     * @format date
+     * @example "2022-04-30"
      */
-    amount_cents?: number;
+    issuing_date: string;
     /**
-     * The quantity of usage events that have been recorded for a particular charge filter during the specified time period. These events may also be referred to as the number of transactions in some contexts.
-     * @example 10
+     * The date when the payment dispute was lost. It is expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-09-14T16:35:31Z"
      */
-    events_count?: number;
+    payment_dispute_lost_at?: string;
     /**
-     * Specifies the name that will be displayed on an invoice.
-     * @example "AWS eu-east-1"
+     * The payment due date for the invoice, specified in the ISO 8601 date format.
+     * @format date
+     * @example "2022-04-30"
      */
-    invoice_display_name?: string;
-    /** Details about the pricing unit used for charge usage. */
-    pricing_unit_details?: UsagePricingUnitDetailsObject;
+    payment_due_date?: string;
     /**
-     * List of filter values applied to the usage.
-     * @example {"region":["us-east-1"]}
+     * Specifies if the payment is considered as overdue.
+     * @example true
      */
-    values?: Record<string, string[]>;
-}[];
-/** Array of aggregated fees, grouped by the event properties defined in a `standard` charge model. */
-export type CustomerChargeGroupedUsageObject = {
+    payment_overdue?: boolean;
     /**
-     * The amount in cents, tax excluded, consumed for a specific group related to a charge item.
-     * @example 1000
+     * The net payment term, expressed in days, specifies the duration within which a customer is expected to remit payment after the invoice is finalized.
+     * @example 30
      */
-    amount_cents?: number;
+    net_payment_term?: number;
     /**
-     * The quantity of usage events that have been recorded for a particular charge during the specified time period. These events may also be referred to as the number of transactions in some contexts.
-     * @example 10
+     * The type of invoice issued. Possible values are `subscription`, `one-off`, `credit` or `progressive_billing`.
+     * @example "subscription"
      */
-    events_count?: number;
+    invoice_type: "subscription" | "add_on" | "credit" | "one_off" | "progressive_billing";
     /**
-     * The number of units consumed for a specific group related to a charge item.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "0.9"
+     * The status of the invoice. It indicates the current state of the invoice and can have following values:
+     * - `draft`: the invoice is in the draft state, waiting for the end of the grace period to be finalized. During this period, events can still be ingested and added to the invoice.
+     * - `finalized`: the invoice has been issued and finalized. In this state, events cannot be ingested or added to the invoice anymore.
+     * - `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.
+     * @example "finalized"
      */
-    units?: string;
-    /** Details about the pricing unit used for charge usage. */
-    pricing_unit_details?: UsagePricingUnitDetailsObject;
-    /** Key value list of event properties aggregated by the charge model */
-    grouped_by?: Record<string, string>;
-    /** Array of filter object, representing multiple dimensions for a charge item. */
-    filters?: CustomerChargeFiltersUsageObject;
-}[];
-export interface CustomerChargeUsageObject {
+    status: "draft" | "finalized" | "voided" | "failed" | "pending";
     /**
-     * The number of units consumed by the customer for a specific charge item.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "1.0"
+     * 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.
+     * - `succeeded`: the payment of the invoice has been successfully processed.
+     * - `failed`: the payment of the invoice has failed or encountered an error during processing.
+     * @example "succeeded"
      */
-    units: string;
+    payment_status: "pending" | "succeeded" | "failed";
     /**
-     * The quantity of usage events that have been recorded for a particular charge during the specified time period. These events may also be referred to as the number of transactions in some contexts.
-     * @example 10
+     * The currency of the invoice issued.
+     * @example "EUR"
      */
-    events_count: number;
+    currency: Currency;
     /**
-     * The amount in cents, tax excluded, consumed by the customer for a specific charge item.
-     * @example 123
+     * The total sum of fees amount in cents. It calculates the cumulative amount of all the fees associated with the invoice, providing a consolidated value.
+     * @example 100
      */
-    amount_cents: number;
+    fees_amount_cents: number;
     /**
-     * The currency of a usage item consumed by the customer.
-     * @example "EUR"
+     * The total sum of all coupons discounted on the invoice. It calculates the cumulative discount amount applied by coupons, expressed in cents.
+     * @example 10
      */
-    amount_currency: Currency;
-    /** Details about the pricing unit used for charge usage. */
-    pricing_unit_details?: UsagePricingUnitDetailsObject;
-    /** Object listing all the properties for a specific charge item. */
-    charge: {
-        /**
-         * Unique identifier assigned to the charge within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the charge's record within the Lago system.
-         * @format uuid
-         * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-         */
-        lago_id: string;
-        /**
-         * The pricing model applied to this charge. Possible values are standard, `graduated`, `percentage`, `package` or `volume`.
-         * @example "graduated"
-         */
-        charge_model: "standard" | "graduated" | "package" | "percentage" | "volume";
-        /**
-         * Specifies the name that will be displayed on an invoice. If no value is set for this field, the name of the actual charge will be used as the default display name.
-         * @example "Setup"
-         */
-        invoice_display_name?: string;
-    };
-    /** The related billable metric object. */
-    billable_metric: {
-        /**
-         * Unique identifier assigned to the billable metric within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the billable metric's record within the Lago system.
-         * @format uuid
-         * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-         */
-        lago_id: string;
-        /**
-         * The name of the billable metric used for this charge.
-         * @example "Storage"
-         */
-        name: string;
-        /**
-         * The code of the billable metric used for this charge.
-         * @example "storage"
-         */
-        code: string;
-        /**
-         * The aggregation type of the billable metric used for this charge. Possible values are `count_agg`, `sum_agg`, `max_agg` or `unique_count_agg`.
-         * @example "sum_agg"
-         */
-        aggregation_type: "count_agg" | "sum_agg" | "max_agg" | "unique_count_agg" | "weighted_sum_agg" | "latest_agg";
-    };
-    /** Array of filter object, representing multiple dimensions for a charge item. */
-    filters?: CustomerChargeFiltersUsageObject;
-    /** Array of aggregated fees, grouped by the event properties defined in a `standard` charge model. */
-    grouped_usage?: CustomerChargeGroupedUsageObject;
-}
-export interface CustomerUsageObject {
+    coupons_amount_cents: number;
     /**
-     * The lower bound of the billing period, expressed in the ISO 8601 datetime format in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-07-01T00:00:00Z"
+     * The total sum of all credit notes discounted on the invoice. It calculates the cumulative discount amount applied by credit notes, expressed in cents.
+     * @example 10
      */
-    from_datetime: string;
+    credit_notes_amount_cents: number;
     /**
-     * The upper bound of the billing period, expressed in the ISO 8601 datetime format in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-07-31T23:59:59Z"
+     * Subtotal amount, excluding taxes, expressed in cents.
+     * This field depends on the version number. Here are the definitions based on the version:
+     * - Version 1: is equal to the sum of `fees_amount_cents`, minus `coupons_amount_cents`, and minus `prepaid_credit_amount_cents`.
+     * - Version 2: is equal to the `fees_amount_cents`.
+     * - Version 3 & 4: is equal to the `fees_amount_cents`, minus `coupons_amount_cents`
+     * @example 100
      */
-    to_datetime: string;
+    sub_total_excluding_taxes_amount_cents: number;
     /**
-     * The date of creation of the invoice.
-     * @format date
-     * @example "2022-08-01"
+     * The sum of tax amount associated with the invoice, expressed in cents.
+     * @example 20
      */
-    issuing_date: string;
+    taxes_amount_cents: number;
     /**
-     * A unique identifier associated with the invoice related to this particular usage record.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     * Subtotal amount, including taxes, expressed in cents.
+     * This field depends on the version number. Here are the definitions based on the version:
+     * - Version 1: is equal to the `total_amount_cents`.
+     * - Version 2: is equal to the sum of `fees_amount_cents` and `taxes_amount_cents`.
+     * - Version 3 & 4: is equal to the sum `sub_total_excluding_taxes_amount_cents` and `taxes_amount_cents`
+     * @example 120
      */
-    lago_invoice_id?: string | null;
+    sub_total_including_taxes_amount_cents: number;
     /**
-     * The currency of the customer's current usage.
-     * @example "EUR"
+     * The total sum of all prepaid credits discounted on the invoice. It calculates the cumulative discount amount applied by prepaid credits, expressed in cents.
+     * @example 0
      */
-    currency?: Currency;
+    prepaid_credit_amount_cents: number;
     /**
-     * The amount in cents, tax excluded.
-     * @example 123
+     * The usage already billed in previous invoices. Only apply to `progressive_billing` and `subscription` invoices.
+     * @example 0
      */
-    amount_cents: number;
+    progressive_billing_credit_amount_cents: number;
     /**
-     * The tax amount in cents.
-     * @example 200
+     * The sum of the amount and taxes amount on the invoice, expressed in cents. It calculates the total financial value of the invoice, including both the original amount and any applicable taxes.
+     * @example 100
      */
-    taxes_amount_cents: number;
+    total_amount_cents: number;
+    /** @example 3 */
+    version_number: number;
     /**
-     * The total amount in cents, tax included.
-     * @example 123
+     * Indicates if the invoice is self-billed. Self-billing is a process where an organization creates the invoice on behalf of the partner. This field specifies whether the invoice is self-billed or not.
+     * @example false
      */
-    total_amount_cents: number;
-    /** Array of charges that comprise the current usage. It contains detailed information about individual charge items associated with the usage. */
-    charges_usage: CustomerChargeUsageObject[];
-}
-export interface CustomerUsage {
-    customer_usage: CustomerUsageObject;
-}
-export interface CustomerProjectedUsageObject {
+    self_billed?: boolean;
     /**
-     * The lower bound of the billing period, expressed in the ISO 8601 datetime format in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-07-01T00:00:00Z"
+     * Contains the URL that provides direct access to the invoice PDF file. You can use this URL to download or view the PDF document of the invoice
+     * @format uri
+     * @example "https://getlago.com/invoice/file"
      */
-    from_datetime: string;
+    file_url?: string;
     /**
-     * The upper bound of the billing period, expressed in the ISO 8601 datetime format in Coordinated Universal Time (UTC).
+     * 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
      * @format date-time
-     * @example "2022-07-31T23:59:59Z"
+     * @example "2022-04-29T08:59:51Z"
      */
-    to_datetime: string;
+    created_at: string;
     /**
-     * The date of creation of the invoice.
-     * @format date
-     * @example "2022-08-01"
+     * The date of the invoice update, represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC). The update_date provides a standardized and internationally recognized timestamp for when the invoice object was updated
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
      */
-    issuing_date: string;
+    updated_at: string;
+}
+export interface BillingPeriodObject {
     /**
-     * A unique identifier associated with the invoice related to this particular usage record.
+     * Unique identifier assigned to the subscription, created by Lago.
      * @format uuid
      * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    lago_invoice_id?: string | null;
+    lago_subscription_id: string;
     /**
-     * The currency of the customer's current usage.
-     * @example "EUR"
+     * Unique identifier assigned to the subscription in your application.
+     * @example "external_id"
      */
-    currency?: Currency;
+    external_subscription_id: string;
     /**
-     * The amount in cents, tax excluded.
-     * @example 123
+     * Unique identifier assigned to the plan, created by Lago.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    amount_cents: number;
+    lago_plan_id: string;
     /**
-     * The projected amount in cents, tax excluded.
-     * @example 256
+     * The beginning date of the subscription billing period. This field indicates the start date of the billing period associated with the subscription fee.
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
      */
-    projected_amount_cents: number;
+    subscription_from_datetime: string;
     /**
-     * The tax amount in cents.
-     * @example 200
+     * The ending date of the subscription billing period. This field indicates the end date of the billing period associated with the subscription fee.
+     * @format date-time
+     * @example "2022-05-29T08:59:51Z"
      */
-    taxes_amount_cents: number;
+    subscription_to_datetime: string;
     /**
-     * The total amount in cents, tax included.
-     * @example 123
+     * The beginning date of the period that covers the charge fees. It is applicable only to the `charge` fees attached to the subscription. This field indicates the start date of the billing period or subscription period associated with the fees.
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
      */
-    total_amount_cents: number;
-    /** Array of charges that comprise the current usage. It contains detailed information about individual charge items associated with the usage. */
-    charges_usage: CustomerChargeUsageObject[];
-}
-export interface CustomerProjectedUsage {
-    customer_projected_usage: CustomerProjectedUsageObject;
-}
-export interface CustomerPastUsage {
-    usage_periods: CustomerUsage[];
-    meta: PaginationMeta;
+    charges_from_datetime: string;
+    /**
+     * The ending date of the period that covers the charge fees. It is applicable only to the `charge` fees attached to the subscription. This field indicates the end date of the billing period or subscription period associated with the fees.
+     * @format date-time
+     * @example "2022-05-29T08:59:51Z"
+     */
+    charges_to_datetime: string;
+    /**
+     * The reason explaining why this subscription appears on the invoice.
+     * @example "subscription_starting"
+     */
+    invoicing_reason: "subscription_starting" | "subscription_periodic" | "subscription_terminating" | "in_advance_charge" | "in_advance_charge_periodic" | "progressive_billing";
 }
-/** . */
-export interface CustomerCheckoutUrl {
-    customer?: {
-        /**
-         * Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system
-         * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-         */
-        lago_customer_id: string;
-        /**
-         * The customer external unique identifier (provided by your own application)
-         * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
-         */
-        external_customer_id: string;
-        /**
-         * The Payment Provider name linked to the Customer.
-         * @example "stripe"
-         */
-        payment_provider: string;
-        /**
-         * Code of the payment provider
-         * @example "Stripe Prod"
-         */
-        payment_provider_code?: string;
-        /**
-         * The new generated Payment Provider Checkout URL for the Customer.
-         * @example "https://foo.bar"
-         */
-        checkout_url?: string;
-    };
+export interface InvoiceMetadataObject {
+    /**
+     * Unique identifier assigned to the invoice metadata within the Lago application.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     */
+    lago_id?: string;
+    /**
+     * Represents the key of the metadata's key-value pair.
+     * @example "digital_ref_id"
+     */
+    key?: string;
+    /**
+     * Represents the value of the metadata's key-value pair.
+     * @example "INV-0123456-98765"
+     */
+    value?: string;
+    /**
+     * The date and time when the metadata object was created. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
+     */
+    created_at?: string;
 }
-export interface EventObject {
+export type InvoiceAppliedTaxObject = BaseAppliedTax & {
     /**
-     * Unique identifier assigned to the event within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the event's record within the Lago system
+     * Unique identifier of the invoice, created by Lago.
      * @format uuid
      * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    lago_id: string;
+    lago_invoice_id?: string;
     /**
-     * This field represents a unique identifier for the event. It is crucial for ensuring idempotency, meaning that each event can be uniquely identified and processed without causing any unintended side effects.
-     * @example "transaction_1234567890"
+     * Fees total amount on which the tax is applied
+     * @example 20000
      */
-    transaction_id: string;
+    fees_amount_cents?: number;
+};
+export interface UsageThresholdObject {
     /**
-     * Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system
+     * Unique identifier of the usage threshold created by Lago.
      * @format uuid
      * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    lago_customer_id: string | null;
+    lago_id: string;
     /**
-     * The code that identifies a targeted billable metric. It is essential that this code matches the `code` property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
-     * @example "storage"
+     * The display name of the usage threshold.
+     * @example "Threshold 1"
      */
-    code: string;
+    threshold_display_name: string | null;
     /**
-     * This field captures the Unix timestamp in seconds indicating the occurrence of the event in Coordinated Universal Time (UTC). If this timestamp is not provided, the API will automatically set it to the time of event reception.
-     * @format date-time
-     * @example "2022-04-29T08:59:51.123Z"
+     * The amount to reach to trigger a `progressive_billing` invoice.
+     * @example 10000
      */
-    timestamp: string;
+    amount_cents: number;
     /**
-     * The precise total amount that was sent in the event payload. This filed is used by the `dynamic` pricing model.
-     * @example "1234.56"
+     * This field when set to `true` indicates that a `progressive_billing` invoice will be created every time the lifetime usage increases by the specified amount.
+     * @example true
      */
-    precise_total_amount_cents?: string | null;
+    recurring: boolean;
     /**
-     * This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a `sum_agg`, `max_agg`, or `unique_count_agg` aggregation method. However, when using a simple `count_agg`, this object is not required.
-     * @example {"gb":10}
+     * The date and time when the usage threshold was created. It is expressed in UTC format according to the ISO 8601 datetime standard.
+     * @format date-time
+     * @example "2023-06-27T19:43:42Z"
      */
-    properties?: {
-        /** The `operation_type` field is only necessary when adding or removing a specific unit when the targeted billable metric adopts a `unique_count_agg` aggregation method. In other cases, the `operation_type` field is not required. The valid values for the `operation_type` field are `add` or `remove`, which indicate whether the unit is being added or removed from the unique count aggregation, respectively. */
-        operation_type?: "add" | "remove";
-        [key: string]: any;
-    };
+    created_at: string;
     /**
-     * Unique identifier assigned to the subscription within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the subscription's record within the Lago system
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     * The date and time when the usage threshold was last updated. It is expressed in UTC format according to the ISO 8601 datetime standard.
+     * @format date-time
+     * @example "2023-06-27T19:43:42Z"
      */
-    lago_subscription_id: string | null;
+    updated_at: string;
+}
+export interface AppliedUsageThresholdObject {
     /**
-     * The unique identifier of the subscription within your application. It is a mandatory field when the customer possesses multiple subscriptions or when the `external_customer_id` is not provided.
-     * @example "sub_1234567890"
+     * The amount of usage in cents that has been accumulated over the lifetime of the subscription.
+     * @example 2000
      */
-    external_subscription_id: string;
+    lifetime_usage_amount_cents: number;
     /**
-     * The creation date of the event's record in the Lago application, presented in the ISO 8601 datetime format, specifically in Coordinated Universal Time (UTC). It provides the precise timestamp of when the event's record was created within the Lago application
+     * The date and time when the lifetime usage was computed. It is expressed in UTC format according to the ISO 8601 datetime standard.
      * @format date-time
-     * @example "2022-04-29T08:59:51Z"
+     * @example "2025-03-31T12:31:44Z"
      */
     created_at: string;
+    usage_threshold: UsageThresholdObject;
 }
-export interface EventsPaginated {
-    events: EventObject[];
+export type InvoiceObject = InvoiceBaseObject & {
+    /** The customer on which the invoice applies. It refers to the customer account or entity associated with the invoice. */
+    customer?: CustomerObject;
+    billing_periods?: BillingPeriodObject[];
+    metadata?: InvoiceMetadataObject[];
+    applied_taxes?: InvoiceAppliedTaxObject[];
+    applied_usage_thresholds?: AppliedUsageThresholdObject[];
+};
+export interface InvoicesPaginated {
+    invoices: InvoiceObject[];
     meta: PaginationMeta;
 }
-export interface EventInputObject {
+export interface PaymentObject {
     /**
-     * This field represents a unique identifier for the event.
-     * It is crucial for ensuring idempotency, meaning that each event can be uniquely identified and processed without causing any unintended side effects.
-     *
-     * WARNING: If the Lago organization is configured to use the new Clickhouse-based event pipeline (designed for high-volume processing), the idempotency logic is handled differently.
-     * Event uniqueness is maintained with both `transaction_id` and `timestamp` fields.
-     * If a new event arrives with identical values for these two fields as an existing event, the new one will overwrite the previous event rather than being rejected.
-     * @example "transaction_1234567890"
+     * The unique identifier of the payment, created by Lago.
+     * @format uuid
+     * @example "4cf085a7-c196-4f07-a543-97c50ec6e8b2"
      */
-    transaction_id: string;
+    lago_id: string;
     /**
-     * The unique identifier of the subscription in your application. This field is mandatory in order to link events to the correct customer subscription.
-     * @example "sub_1234567890"
+     * Unique identifier of the customer, created by Lago.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    external_subscription_id: string;
+    lago_customer_id: string;
     /**
-     * The code that identifies a targeted billable metric. It is essential that this code matches the `code` property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
-     * @example "storage"
+     * The customer external unique identifier (provided by your own application)
+     * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
      */
-    code: string;
+    external_customer_id: string;
+    /** List of invoice IDs associated with the payment. */
+    invoice_ids: string[];
     /**
-     * This field captures the Unix timestamp in seconds indicating the occurrence of the event in Coordinated Universal Time (UTC).
-     * If this timestamp is not provided, the API will automatically set it to the time of event reception.
-     * You can also provide miliseconds precision by appending decimals to the timestamp.
-     * @example "1651240791.123"
+     * The unique identifier of the paid resource, created by Lago.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    timestamp?: number | string;
+    lago_payable_id: string;
     /**
-     * The precise total amount in cents with precision used by the `dynamic` pricing model to compute the usage amount.
-     * @example "1234.56"
+     * The type of the paid resource, associated with the `lago_payable_id`.
+     * @example "Invoice"
      */
-    precise_total_amount_cents?: string | null;
+    payable_type: "Invoice" | "PaymentRequest";
     /**
-     * This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a `sum_agg`, `max_agg`, or `unique_count_agg` aggregation method. However, when using a simple `count_agg`, this object is not required.
-     * @example {"gb":10}
+     * The amount of the payment in cents.
+     * @example 1099
      */
-    properties?: object | null;
-}
-export interface EventInput {
-    event: EventInputObject;
-}
-export interface EventCreated {
-    event: EventObject & {
-        /**
-         * The value will always be null in this response as the event processing is done asynchronously
-         * @example null
-         */
-        lago_customer_id?: null;
-    };
+    amount_cents: number;
+    /**
+     * The currency of the payment amount.
+     * @example "USD"
+     */
+    amount_currency: Currency;
+    /**
+     * The status of the payment within the payment provider. This can be very different from a payment provider to another.
+     * @example "Completed"
+     */
+    status: string;
+    /**
+     * The normalized payment status by Lago.
+     * @example "succeeded"
+     */
+    payment_status: "succeeded" | "failed" | "pending" | "processing";
+    /**
+     * The type of payment.
+     * @example "manual"
+     */
+    type: "manual" | "provider";
+    /**
+     * Reference for the payment.
+     * @example "ref1"
+     */
+    reference: string;
+    /**
+     * Code of the payment provider
+     * @example "stripe_prod"
+     */
+    payment_provider_code: string;
+    /**
+     * The type of payment provider
+     * @example "stripe"
+     */
+    payment_provider_type: "adyen" | "cashfree" | "gocardless" | "stripe" | "flutterwave" | "moneyhash";
+    /** DEPRECATED: use provider_payment_id */
+    external_payment_id: string | null;
+    /**
+     * Unique identifier of the payment within the payment provider (if applicable).
+     * @example "pi_5eb0285741bc6ba"
+     */
+    provider_payment_id: string | null;
+    /**
+     * Unique identifier of the customer within the payment provider
+     * @example "cus_5eb0285bcf941bc6ba"
+     */
+    provider_customer_id: string;
+    /**
+     * The next action to be taken by the customer to complete the payment. Should usually be empty, except when receiving the `payment.requires_action` webhook.
+     * @example {"type":"redirect_to_url","redirect_to_url":{"url":"https://hooks.stripe.com/3d_secure_2/hosted?merchant=acct_AAA&payment_intent=pi_BBB&payment_intent_client_secret=pi_BBB&publishable_key=pk_test_CCC","return_url":"https://app.example.com"}}
+     */
+    next_action: Record<string, any>;
+    /**
+     * Timestamp when the payment was created in Lago's database, not on the payment provider.
+     * @format date-time
+     * @example "2025-01-21T00:10:29Z"
+     */
+    created_at: string;
 }
-export interface EventBatchInput {
-    events: EventInputObject[];
+export interface PaymentsPaginated {
+    payments: PaymentObject[];
+    meta: PaginationMeta;
 }
-export interface EventsCreated {
-    events: (EventObject & {
-        /**
-         * The value will always be null in this response as the event processing is done asynchronously
-         * @example null
-         */
-        lago_customer_id?: null;
-    })[];
+export interface PaymentRequestObject {
+    /**
+     * Unique identifier of the payment request, created by Lago.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     */
+    lago_id: string;
+    /**
+     * The customer's email address used for sending dunning notifications
+     * @format email
+     * @example "dinesh@piedpiper.test"
+     */
+    email: string;
+    /**
+     * The sum of the total amounts of all the invoices included in the payment request, expressed in cents.
+     * @example 100
+     */
+    amount_cents: number;
+    /**
+     * The currency of the payment request.
+     * @example "EUR"
+     */
+    amount_currency: Currency;
+    /**
+     * The status of the payment associated with the payment request. It can have one of the following values:
+     * - `pending`: the payment is pending, waiting for payment processing in the payment provider or when the invoice is emitted but users have not updated the payment status through the endpoint.
+     * - `succeeded`: the payment of the payment request has been successfully processed.
+     * - `failed`: the payment of the payment request has failed or encountered an error during processing.
+     * @example "succeeded"
+     */
+    payment_status: "pending" | "succeeded" | "failed";
+    /**
+     * The date and time when the payment request was created. It is expressed in UTC format according to the ISO 8601 datetime standard. This field provides the timestamp for the exact moment when the payment request was initially created.
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
+     */
+    created_at: string;
+    /** The customer on which the payment request applies. It refers to the customer account or entity associated with the payment request. */
+    customer: CustomerBaseObject;
+    invoices: InvoiceBaseObject[];
 }
-export interface EventEstimateFeesInput {
-    event: {
-        /**
-         * The code that identifies a targeted billable metric. It is essential that this code matches the `code` property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
-         * @example "storage"
-         */
-        code: string;
-        /**
-         * The unique identifier of the subscription within your application.
-         * @example "sub_1234567890"
-         */
-        external_subscription_id: string;
-        /** This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a `sum_agg`, `max_agg`, or `unique_count_agg` aggregation method. However, when using a simple `count_agg`, this object is not required. */
-        properties?: object;
-    };
+export interface PaymentRequestsPaginated {
+    payment_requests: PaymentRequestObject[];
+    meta: PaginationMeta;
 }
-export interface Fees {
-    fees: FeeObject[];
+export interface SubscriptionObject {
+    /**
+     * Unique identifier assigned to the subscription within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the subscription's record within the Lago system
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     */
+    lago_id: string;
+    /**
+     * The subscription external unique identifier (provided by your own application).
+     * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
+     */
+    external_id: string;
+    /**
+     * Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     */
+    lago_customer_id: string;
+    /**
+     * The customer external unique identifier (provided by your own application).
+     * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
+     */
+    external_customer_id: string;
+    /**
+     * The billing time for the subscription, which can be set as either `anniversary` or `calendar`. If not explicitly provided, it will default to `calendar`. The billing time determines the timing of recurring billing cycles for the subscription. By specifying `anniversary`, the billing cycle will be based on the specific date the subscription started (billed fully), while `calendar` sets the billing cycle at the first day of the week/month/year (billed with proration).
+     * @example "anniversary"
+     */
+    billing_time: "calendar" | "anniversary";
+    /**
+     * The display name of the subscription on an invoice. This field allows for customization of the subscription's name for billing purposes, especially useful when a single customer has multiple subscriptions using the same plan.
+     * @example "Repository A"
+     */
+    name: string | null;
+    /**
+     * The unique code representing the plan to be attached to the customer. This code must correspond to the `code` property of one of the active plans.
+     * @example "premium"
+     */
+    plan_code: string;
+    /**
+     * The status of the subscription, which can have the following values:
+     * - `active`: the subscription is currently active and applied to the customer.
+     * - `canceled`: the subscription has been stopped before its activation. This can occur when two consecutive downgrades have been applied to a customer or when a subscription with a pending status is terminated.
+     * - `pending`: a previous subscription has been downgraded, and the current one is awaiting automatic activation at the end of the billing period.
+     * - `terminated`: the subscription is no longer active.
+     * @example "active"
+     */
+    status: "active" | "canceled" | "pending" | "terminated";
+    /**
+     * The creation date of the subscription, represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC). This date provides a timestamp indicating when the subscription was initially created.
+     * @format date-time
+     * @example "2022-08-08T00:00:00Z"
+     */
+    created_at: string;
+    /**
+     * The cancellation date of the subscription. This field is not null when the subscription is `canceled`. This date should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-09-14T16:35:31Z"
+     */
+    canceled_at: string | null;
+    /**
+     * The effective start date of the subscription. This field can be null if the subscription is `pending` or `canceled`. This date should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-08-08T00:00:00Z"
+     */
+    started_at: string | null;
+    /**
+     * The effective end date of the subscription. If this field is set to null, the subscription will automatically renew. This date should be provided in ISO 8601 datetime format, and use Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-10-08T00:00:00Z"
+     */
+    ending_at: string | null;
+    /**
+     * The anniversary date and time of the initial subscription. This date serves as the basis for billing subscriptions with `anniversary` billing time. The `anniversary_date` should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-08-08T00:00:00Z"
+     */
+    subscription_at: string;
+    /**
+     * The termination date of the subscription. This field is not null when the subscription is `terminated`. This date should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC)
+     * @format date-time
+     * @example "2022-09-14T16:35:31Z"
+     */
+    terminated_at: string | null;
+    /**
+     * The code identifying the previous plan associated with this subscription.
+     * @example null
+     */
+    previous_plan_code: string | null;
+    /**
+     * The code identifying the next plan in the case of a downgrade.
+     * @example null
+     */
+    next_plan_code: string | null;
+    /**
+     * The date when the plan will be downgraded, represented in ISO 8601 date format.
+     * @format date
+     * @example "2022-04-30"
+     */
+    downgrade_plan_date: string | null;
+    /**
+     * The date when the free trial is ended, represented in ISO 8601 date format.
+     * @format date-time
+     * @example "2022-08-08T00:00:00Z"
+     */
+    trial_ended_at: string | null;
+    /**
+     * The date and time when the current billing period started, represented in ISO 8601 date format.
+     * @format date-time
+     * @example "2022-08-08T00:00:00Z"
+     */
+    current_billing_period_started_at: string | null;
+    /**
+     * The date and time when the current billing period ends, represented in ISO 8601 date format.
+     * @format date-time
+     * @example "2022-09-08T00:00:00Z"
+     */
+    current_billing_period_ending_at: string | null;
+    /**
+     * 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.
+     * This field allows you to control the behavior of the credit note generation:
+     *
+     * - `credit`: A credit note is generated for the unused subscription time. The unused amount is credited back to the customer.
+     * - `refund`: A credit note is generated for the unused subscription time. If the invoice is paid or partially paid, the unused paid amount is refunded; any unpaid unused amount is credited back to the customer.
+     * - `skip`: No credit note is generated for the unused subscription time.
+     *
+     * _Note: This field is only applicable to pay-in-advance plans and will be `null` for pay-in-arrears plans._
+     * @example "credit"
+     */
+    on_termination_credit_note: "credit" | "refund" | "skip";
+    /**
+     * When a subscription is terminated before the end of its billing period, we generate an invoice for the unbilled usage.
+     * This field allows you to control the behavior of the invoice generation:
+     *
+     * - `generate`: An invoice is generated for the unbilled usage.
+     * - `skip`: No invoice is generated for the unbilled usage.
+     * @default "generate"
+     * @example "generate"
+     */
+    on_termination_invoice: "generate" | "skip";
 }
-export interface EventEstimateInstantFeesInput {
-    event: {
-        /**
-         * The code that identifies a targeted billable metric. It is essential that this code matches the `code` property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
-         * @example "storage"
-         */
-        code: string;
+export interface SubscriptionsPaginated {
+    subscriptions: SubscriptionObject[];
+    meta: PaginationMeta;
+}
+/** Object that represents rule for wallet recurring transactions. */
+export interface WalletRecurringTransactionRule {
+    /**
+     * A unique identifier for the recurring transaction rule in the Lago application. Can be used to update a recurring transaction rule.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     */
+    lago_id: string;
+    /**
+     * The trigger. Possible values are `interval` or `threshold`.
+     * @example "interval"
+     */
+    trigger: "interval" | "threshold";
+    /**
+     * The method used for recurring top-up. Possible values are `fixed` or `target`.
+     * @example "target"
+     */
+    method: "fixed" | "target";
+    /**
+     * The interval used for recurring top-up. It represents the frequency at which automatic top-up occurs. The interval can be one of the following values: `weekly`, `monthly`, `quarterly`, `semiannual` or `yearly`. Required only if trigger is set to `interval`.
+     * @example "monthly"
+     */
+    interval: "weekly" | "monthly" | "quarterly" | "semiannual" | "yearly";
+    /**
+     * The status of the recurring transaction rule. Possible values are `active` or `terminated`.
+     * @example "active"
+     */
+    status: "active" | "terminated";
+    /**
+     * The threshold for recurring top-ups is the value at which an automatic top-up is triggered. For example, if this threshold is set at 10 credits, an automatic top-up will occur whenever the wallet balance falls to or below 10 credits. Required only when trigger is set to `threshold`.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "20.0"
+     */
+    threshold_credits: string;
+    /**
+     * The number of paid credits. Required only if there is no granted credits.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "20.0"
+     */
+    paid_credits: string;
+    /**
+     * The number of free granted credits. Required only if there is no paid credits.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "10.0"
+     */
+    granted_credits: string;
+    /**
+     * The effective start date for recurring top-ups. This date should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-08-08T00:00:00Z"
+     */
+    started_at: string | null;
+    /**
+     * The target ongoing balance is the value set for the ongoing balance to be reached by the automatic top-up. Required only when trigger is set to `target`.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "200.0"
+     */
+    target_ongoing_balance: string | null;
+    /**
+     * The date of the metadata object 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 metadata object was created
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
+     */
+    created_at: string;
+    /**
+     * The expiration date and time for this specific recurring transaction rule. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2023-09-30T23:59:59Z"
+     */
+    expiration_at: string | null;
+    /**
+     * A boolean setting that, when set to true, delays issuing an invoice for a wallet top-up until a successful payment is made; if false, the invoice is issued immediately upon wallet top-up, regardless of the payment status. Default value of false.
+     * @example false
+     */
+    invoice_requires_successful_payment: boolean;
+    /**
+     * This field allows you to store a list of key-value pairs containing additional information or custom attributes. These key-value pairs will populate the metadata of the wallet transactions triggered by this rule.
+     * @example [{"key":"example_key","value":"example_value"},{"key":"another_key","value":"another_value"}]
+     */
+    transaction_metadata: {
+        /** The unique identifier for the attribute. */
+        key?: string;
+        /** The value associated with the key. */
+        value?: string;
+    }[];
+    /**
+     * The name of the wallet transactions triggered by this rule. It will appear on the invoice as the label for the fee. If not set, the label on the invoice will fallback to either `Prepaid credits - {{wallet_name}}` if the wallet name is set, or `Prepaid credits`.
+     * @example "Tokens for models 'high-fidelity-boost'"
+     */
+    transaction_name: string | null;
+    /**
+     * When true, allows rule to topped up wallet with transactions that exceed the paid top-up limits. Defaults to false.
+     * @example false
+     */
+    ignore_paid_top_up_limits: boolean;
+}
+export interface WalletObject {
+    /**
+     * Unique identifier assigned to the wallet within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the wallet's record within the Lago system.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     */
+    lago_id: string;
+    /**
+     * Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     */
+    lago_customer_id: string;
+    /**
+     * The customer external unique identifier (provided by your own application)
+     * @example "hooli_1234"
+     */
+    external_customer_id: string;
+    /**
+     * The status of the wallet. Possible values are `active` or `terminated`.
+     * @example "active"
+     */
+    status: "active" | "terminated";
+    /**
+     * The currency of the wallet.
+     * @example "USD"
+     */
+    currency: Currency;
+    /**
+     * The name of the wallet.
+     * @example "Prepaid"
+     */
+    name?: string | null;
+    /**
+     * The rate of conversion between credits and the amount in the specified currency. It indicates the ratio or factor used to convert credits into the corresponding monetary value in the currency of the transaction.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "1.5"
+     */
+    rate_amount: string;
+    /**
+     * The current wallet balance expressed in credits. This reflects the available balance after all transactions are settled.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "28.0"
+     */
+    credits_balance: string;
+    /**
+     * The current wallet balance expressed in cents. This reflects the available balance after all transactions are settled.
+     * @example 1000
+     */
+    balance_cents: number;
+    /**
+     * The number of consumed credits.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "2.0"
+     */
+    consumed_credits: string;
+    /**
+     * The date of the wallet creation, represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
+     */
+    created_at: string;
+    /**
+     * The date and time that determines when the wallet will expire. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example null
+     */
+    expiration_at?: string | null;
+    /**
+     * The date and time of the last balance top-up. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
+     */
+    last_balance_sync_at?: string | null;
+    /**
+     * The date and time of the last credits consumption. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-04-29T08:59:51Z"
+     */
+    last_consumed_credit_at?: string | null;
+    /**
+     * The date of terminaison of the wallet. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-09-14T16:35:31Z"
+     */
+    terminated_at?: string | null;
+    /**
+     * A boolean setting that, when set to true, delays issuing an invoice for a wallet top-up until a successful payment is made; if false, the invoice is issued immediately upon wallet top-up, regardless of the payment status. Default value of false.
+     * @example false
+     */
+    invoice_requires_successful_payment: boolean;
+    /** Set wallet limitations to fee types. */
+    applies_to?: {
         /**
-         * The unique identifier of the subscription within your application.
-         * @example "sub_1234567890"
+         * An array of fee types to which the wallet is applicable. By specifying the fee types in this field, you can restrict the wallet's usage to specific fee types only.
+         * @example ["charge"]
          */
-        external_subscription_id: string;
-        /** This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a `sum_agg`, `max_agg`, or `unique_count_agg` aggregation method. However, when using a simple `count_agg`, this object is not required. */
-        properties?: object;
+        fee_types?: ("charge" | "subscription" | "commitment")[];
         /**
-         * This field represents a unique identifier for the event.
-         * @example "transaction_1234567890"
+         * 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 ["bm1"]
          */
-        transaction_id?: string | null;
+        billable_metric_codes?: string[];
     };
-}
-export interface FeeEstimateObject {
-    lago_id?: null;
+    /** List of recurring transaction rules. Currently, we only allow one recurring rule per wallet. */
+    recurring_transaction_rules?: WalletRecurringTransactionRule[];
     /**
-     * Unique identifier assigned to the charge that the fee belongs to
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     * The ongoing wallet balance expressed in cents. This represents the `balance_cents` minus the `ongoing_usage_balance_cents`, showing the real time balance after accounting for current usage including taxes.
+     * @example 800
      */
-    lago_charge_id?: string;
+    ongoing_balance_cents: number;
     /**
-     * Unique identifier assigned to the charge filter that the fee belongs to
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     * The ongoing usage balance of the wallet, expressed in cents. This reflects all current usage and draft invoices including taxes.
+     * @example 200
      */
-    lago_charge_filter_id?: string | null;
-    lago_invoice_id?: null;
-    lago_true_up_fee_id?: null;
-    lago_true_up_parent_fee_id?: null;
+    ongoing_usage_balance_cents: number;
     /**
-     * Unique identifier assigned to the subscription, created by Lago. This field is specifically displayed when the fee type is charge or subscription.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     * The ongoing wallet balance expressed in credits. This represents the `credits_balance` minus the `credits_ongoing_usage_balance`, showing the real time balance after accounting for current usage including taxes.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "8.0"
      */
-    lago_subscription_id?: string;
+    credits_ongoing_balance: string;
     /**
-     * Unique identifier assigned to the customer, created by Lago. This field is specifically displayed when the fee type is charge or subscription.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     * The ongoing usage balance of the wallet, expressed in credits. This reflects all current usage and draft invoices including taxes.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "2.0"
      */
-    lago_customer_id?: string;
+    credits_ongoing_usage_balance: string;
     /**
-     * Unique identifier assigned to the customer in your application. This field is specifically displayed when the fee type is charge or subscription.
-     * @example "external_id"
+     * Minimum amount of cents that can be top-up with a single paid transaction.
+     * @example 100
      */
-    external_customer_id?: string;
+    paid_top_up_min_amount_cents?: number | null;
     /**
-     * Unique identifier assigned to the subscription in your application. This field is specifically displayed when the fee type is charge or subscription.
-     * @example "external_id"
+     * Maximum amount of cents that can be top-up with a single paid transaction.
+     * @example 1000
      */
-    external_subscription_id?: string;
+    paid_top_up_max_amount_cents?: number | null;
+}
+export interface WalletsPaginated {
+    wallets: WalletObject[];
+    meta: PaginationMeta;
+}
+/** Details about the pricing unit used for charge usage. */
+export interface UsagePricingUnitDetailsObject {
     /**
-     * The cost of this specific fee, excluding any applicable taxes.
-     * @example 100
+     * The amount in cents in the pricing unit.
+     * @example 200
      */
     amount_cents: number;
     /**
-     * The cost of this specific fee, excluding any applicable taxes, with precision.
-     * @example 1.0001
+     * The short name of the pricing unit.
+     * @example "CR"
      */
-    precise_amount?: number;
+    short_name: string;
     /**
-     * The cost of this specific fee, including any applicable taxes, with precision.
-     * @example 1.0212
+     * The conversion rate from pricing units to the plan's currency.
+     * @example "0.5"
      */
-    precise_total_amount?: number;
+    conversion_rate: string;
+}
+/** Array of filter object, representing multiple dimensions for a charge item. */
+export type CustomerChargeFiltersUsageObject = {
     /**
-     * The currency of this specific fee. It indicates the monetary unit in which the fee's cost is expressed.
-     * @example "EUR"
+     * The number of units consumed for a specific charge filter related to a charge item.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "0.9"
      */
-    amount_currency: Currency;
+    units?: string;
     /**
-     * The cost of the tax associated with this specific fee.
-     * @example 0
+     * The total number of units consumed by the customer for a specific charge item, aggregated across all usage events.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "1.0"
      */
-    taxes_amount_cents: number;
+    total_aggregated_units?: string;
     /**
-     * The cost of the tax associated with this specific fee, with precision.
-     * @example 0
+     * The amount in cents, tax excluded, consumed for a specific charge filter related to a charge item.
+     * @example 1000
      */
-    taxes_precise_amount?: number;
+    amount_cents?: number;
     /**
-     * The tax rate associated with this specific fee.
-     * @example 20
+     * The quantity of usage events that have been recorded for a particular charge filter during the specified time period. These events may also be referred to as the number of transactions in some contexts.
+     * @example 10
      */
-    taxes_rate: number;
+    events_count?: number;
     /**
-     * The number of units used to charge the customer. This field indicates the quantity or count of units consumed or utilized in the context of the charge. It helps in determining the basis for calculating the fee or cost associated with the usage of the service or product provided to the customer.
-     * @example "0.32"
+     * Specifies the name that will be displayed on an invoice.
+     * @example "AWS eu-east-1"
      */
-    units: string;
-    description?: null;
+    invoice_display_name?: string;
+    /** Details about the pricing unit used for charge usage. */
+    pricing_unit_details?: UsagePricingUnitDetailsObject;
     /**
-     * The unit amount of the fee per unit, with precision.
-     * @example 312.5
+     * List of filter values applied to the usage.
+     * @example {"region":["us-east-1"]}
      */
-    precise_unit_amount: number;
+    values?: Record<string, string[]>;
+}[];
+/** Array of aggregated fees, grouped by the event properties defined in a `standard` charge model. */
+export type CustomerChargeGroupedUsageObject = {
     /**
-     * The coupon amount applied to the estimated instant fee. It will always returns 0
-     * @example "0.0"
+     * The amount in cents, tax excluded, consumed for a specific group related to a charge item.
+     * @example 1000
      */
-    precise_coupons_amount_cents?: string;
+    amount_cents?: number;
     /**
-     * The cost of this specific fee, including any applicable taxes.
-     * @example 120
+     * The quantity of usage events that have been recorded for a particular charge during the specified time period. These events may also be referred to as the number of transactions in some contexts.
+     * @example 10
      */
-    total_amount_cents: number;
+    events_count?: number;
     /**
-     * The currency of this specific fee, including any applicable taxes.
-     * @example "EUR"
+     * The number of units consumed for a specific group related to a charge item.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "0.9"
      */
-    total_amount_currency: Currency;
+    units?: string;
     /**
-     * The number of events that have been sent and used to charge the customer. This field indicates the count or quantity of events that have been processed and considered in the charging process.
-     * @example 1
+     * The total number of units consumed by the customer for a specific charge item, aggregated across all usage events.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "1.0"
      */
-    events_count?: number;
+    total_aggregated_units?: string;
+    /** Details about the pricing unit used for charge usage. */
+    pricing_unit_details?: UsagePricingUnitDetailsObject;
+    /** Key value list of event properties aggregated by the charge model */
+    grouped_by?: Record<string, string>;
+    /** Array of filter object, representing multiple dimensions for a charge item. */
+    filters?: CustomerChargeFiltersUsageObject;
+}[];
+export interface CustomerChargeUsageObject {
     /**
-     * Flag that indicates whether the fee was paid in advance. It serves as a boolean value, where `true` represents that the fee was paid in advance (straightaway), and `false` indicates that the fee was not paid in arrears (at the end of the period).
-     * @example true
+     * The number of units consumed by the customer for a specific charge item.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "1.0"
      */
-    pay_in_advance: boolean;
+    units: string;
     /**
-     * Flag that indicates whether the fee was included on the invoice. It serves as a boolean value, where `true` represents that the fee was included on the invoice, and `false` indicates that the fee was not included on the invoice.
-     * @example true
+     * The total number of units consumed by the customer for a specific charge item, aggregated across all usage events.
+     * @pattern ^[0-9]+.?[0-9]*$
+     * @example "1.0"
      */
-    invoiceable: boolean;
+    total_aggregated_units: string;
     /**
-     * Indicates the payment status of the fee. It represents the current status of the payment associated with the fee. The value will always `pending`.
-     * @example "pending"
+     * The quantity of usage events that have been recorded for a particular charge during the specified time period. These events may also be referred to as the number of transactions in some contexts.
+     * @example 10
      */
-    payment_status: "pending";
-    created_at?: null;
-    succeeded_at?: null;
-    failed_at?: null;
-    refunded_at?: null;
+    events_count: number;
     /**
-     * Unique identifier assigned to the transaction. This field is specifically displayed when the fee type is `charge` and the payment for the fee is made in advance (`pay_in_advance` is set to `true`).
-     * @example "transaction_1234567890"
+     * The amount in cents, tax excluded, consumed by the customer for a specific charge item.
+     * @example 123
      */
-    event_transaction_id?: string;
-    amount_details?: null;
-    /** Item attached to the fee */
-    item: {
-        /**
-         * The fee type. The value will be `charge`.
-         * @example "charge"
-         */
-        type: "charge";
-        /**
-         * The code of the fee item. It will be the code of the `billable_metric`.
-         * @example "startup"
-         */
-        code: string;
+    amount_cents: number;
+    /**
+     * The currency of a usage item consumed by the customer.
+     * @example "EUR"
+     */
+    amount_currency: Currency;
+    /** Details about the pricing unit used for charge usage. */
+    pricing_unit_details?: UsagePricingUnitDetailsObject;
+    /** Object listing all the properties for a specific charge item. */
+    charge: {
         /**
-         * The name of the fee item. It will be the name of the `billable_metric`.
-         * @example "Startup"
+         * Unique identifier assigned to the charge within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the charge's record within the Lago system.
+         * @format uuid
+         * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
          */
-        name: string;
+        lago_id: string;
         /**
-         * The description of the fee item. It will be the name of the `billable_metric`.
-         * @example "Startup description"
+         * The pricing model applied to this charge. Possible values are standard, `graduated`, `percentage`, `package` or `volume`.
+         * @example "graduated"
          */
-        description?: string;
+        charge_model: "standard" | "graduated" | "package" | "percentage" | "volume";
         /**
          * Specifies the name that will be displayed on an invoice. If no value is set for this field, the name of the actual charge will be used as the default display name.
-         * @example "Setup Fee (SF1)"
+         * @example "Setup"
          */
         invoice_display_name?: string;
+    };
+    /** The related billable metric object. */
+    billable_metric: {
         /**
-         * Specifies the name that will be displayed on an invoice. If no value is set for this field, the actual charge filter values will be used as the default display name.
-         * @example "AWS eu-east-1"
-         */
-        filter_invoice_display_name?: string | null;
-        /** Key value list of event properties */
-        filters?: object | null;
-        /**
-         * Unique identifier of the fee item, created by Lago. It will be the identifier of the `billable_metric`.
+         * Unique identifier assigned to the billable metric within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the billable metric's record within the Lago system.
          * @format uuid
          * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
          */
-        lago_item_id: string;
+        lago_id: string;
         /**
-         * The type of the fee item. Values is `BillableMetric`.
-         * @example "BillableMetric"
+         * The name of the billable metric used for this charge.
+         * @example "Storage"
          */
-        item_type: "BillableMetric";
-        /** Key value list of event properties aggregated by the charge model */
-        grouped_by?: Record<string, string>;
-    };
-}
-export interface FeesEstimate {
-    fees: FeeEstimateObject[];
-}
-export interface EventBatchEstimateInstantFeesInput {
-    events: EventEstimateInstantFeesInput[];
-}
-export interface Event {
-    event: EventObject;
-}
-export interface FeesPaginated {
-    fees: FeeObject[];
-    meta: PaginationMeta;
-}
-export interface Fee {
-    fee: FeeObject;
-}
-export interface FeeUpdateInput {
-    fee: {
+        name: string;
         /**
-         * The payment status of the fee. Possible values are `pending`, `succeeded`, `failed` or `refunded`.
-         * @example "succeeded"
+         * The code of the billable metric used for this charge.
+         * @example "storage"
          */
-        payment_status: "pending" | "succeeded" | "failed" | "refunded";
+        code: string;
+        /**
+         * The aggregation type of the billable metric used for this charge. Possible values are `count_agg`, `sum_agg`, `max_agg` or `unique_count_agg`.
+         * @example "sum_agg"
+         */
+        aggregation_type: "count_agg" | "sum_agg" | "max_agg" | "unique_count_agg" | "weighted_sum_agg" | "latest_agg";
     };
+    /** Array of filter object, representing multiple dimensions for a charge item. */
+    filters?: CustomerChargeFiltersUsageObject;
+    /** Array of aggregated fees, grouped by the event properties defined in a `standard` charge model. */
+    grouped_usage?: CustomerChargeGroupedUsageObject;
 }
-export interface InvoiceBaseObject {
-    /**
-     * Unique identifier assigned to the fee within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the fee's record within the Lago system.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_id: string;
-    /**
-     * The unique code of the billing entity associated with the invoice
-     * @example "acme_corp"
-     */
-    billing_entity_code: string | null;
-    /**
-     * This ID helps in uniquely identifying and organizing the invoices associated with a specific customer. It provides a sequential numbering system specific to the customer, allowing for easy tracking and management of invoices within the customer's context.
-     * @example 2
-     */
-    sequential_id?: number;
-    /**
-     * The unique number assigned to the invoice. This number serves as a distinct identifier for the invoice and helps in differentiating it from other invoices in the system.
-     * @example "LAG-1234-001-002"
-     */
-    number: string;
+export interface CustomerUsageObject {
     /**
-     * The date when the invoice was issued. It is provided in the ISO 8601 date format.
-     * @format date
-     * @example "2022-04-30"
+     * The lower bound of the billing period, expressed in the ISO 8601 datetime format in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-07-01T00:00:00Z"
      */
-    issuing_date: string;
+    from_datetime: string;
     /**
-     * The date when the payment dispute was lost. It is expressed in Coordinated Universal Time (UTC).
+     * The upper bound of the billing period, expressed in the ISO 8601 datetime format in Coordinated Universal Time (UTC).
      * @format date-time
-     * @example "2022-09-14T16:35:31Z"
+     * @example "2022-07-31T23:59:59Z"
      */
-    payment_dispute_lost_at?: string;
+    to_datetime: string;
     /**
-     * The payment due date for the invoice, specified in the ISO 8601 date format.
+     * The date of creation of the invoice.
      * @format date
-     * @example "2022-04-30"
-     */
-    payment_due_date?: string;
-    /**
-     * Specifies if the payment is considered as overdue.
-     * @example true
-     */
-    payment_overdue?: boolean;
-    /**
-     * The net payment term, expressed in days, specifies the duration within which a customer is expected to remit payment after the invoice is finalized.
-     * @example 30
-     */
-    net_payment_term?: number;
-    /**
-     * The type of invoice issued. Possible values are `subscription`, `one-off`, `credit` or `progressive_billing`.
-     * @example "subscription"
-     */
-    invoice_type: "subscription" | "add_on" | "credit" | "one_off" | "progressive_billing";
-    /**
-     * The status of the invoice. It indicates the current state of the invoice and can have following values:
-     * - `draft`: the invoice is in the draft state, waiting for the end of the grace period to be finalized. During this period, events can still be ingested and added to the invoice.
-     * - `finalized`: the invoice has been issued and finalized. In this state, events cannot be ingested or added to the invoice anymore.
-     * - `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.
-     * @example "finalized"
+     * @example "2022-08-01"
      */
-    status: "draft" | "finalized" | "voided" | "failed" | "pending";
+    issuing_date: string;
     /**
-     * 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.
-     * - `succeeded`: the payment of the invoice has been successfully processed.
-     * - `failed`: the payment of the invoice has failed or encountered an error during processing.
-     * @example "succeeded"
+     * A unique identifier associated with the invoice related to this particular usage record.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    payment_status: "pending" | "succeeded" | "failed";
+    lago_invoice_id?: string | null;
     /**
-     * The currency of the invoice issued.
+     * The currency of the customer's current usage.
      * @example "EUR"
      */
-    currency: Currency;
-    /**
-     * The total sum of fees amount in cents. It calculates the cumulative amount of all the fees associated with the invoice, providing a consolidated value.
-     * @example 100
-     */
-    fees_amount_cents: number;
+    currency?: Currency;
     /**
-     * The total sum of all coupons discounted on the invoice. It calculates the cumulative discount amount applied by coupons, expressed in cents.
-     * @example 10
+     * The amount in cents, tax excluded.
+     * @example 123
      */
-    coupons_amount_cents: number;
+    amount_cents: number;
     /**
-     * The total sum of all credit notes discounted on the invoice. It calculates the cumulative discount amount applied by credit notes, expressed in cents.
-     * @example 10
+     * The tax amount in cents.
+     * @example 200
      */
-    credit_notes_amount_cents: number;
+    taxes_amount_cents: number;
     /**
-     * Subtotal amount, excluding taxes, expressed in cents.
-     * This field depends on the version number. Here are the definitions based on the version:
-     * - Version 1: is equal to the sum of `fees_amount_cents`, minus `coupons_amount_cents`, and minus `prepaid_credit_amount_cents`.
-     * - Version 2: is equal to the `fees_amount_cents`.
-     * - Version 3 & 4: is equal to the `fees_amount_cents`, minus `coupons_amount_cents`
-     * @example 100
+     * The total amount in cents, tax included.
+     * @example 123
      */
-    sub_total_excluding_taxes_amount_cents: number;
+    total_amount_cents: number;
+    /** Array of charges that comprise the current usage. It contains detailed information about individual charge items associated with the usage. */
+    charges_usage: CustomerChargeUsageObject[];
+}
+export interface CustomerUsage {
+    customer_usage: CustomerUsageObject;
+}
+export interface CustomerProjectedUsageObject {
     /**
-     * The sum of tax amount associated with the invoice, expressed in cents.
-     * @example 20
+     * The lower bound of the billing period, expressed in the ISO 8601 datetime format in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-07-01T00:00:00Z"
      */
-    taxes_amount_cents: number;
+    from_datetime: string;
     /**
-     * Subtotal amount, including taxes, expressed in cents.
-     * This field depends on the version number. Here are the definitions based on the version:
-     * - Version 1: is equal to the `total_amount_cents`.
-     * - Version 2: is equal to the sum of `fees_amount_cents` and `taxes_amount_cents`.
-     * - Version 3 & 4: is equal to the sum `sub_total_excluding_taxes_amount_cents` and `taxes_amount_cents`
-     * @example 120
+     * The upper bound of the billing period, expressed in the ISO 8601 datetime format in Coordinated Universal Time (UTC).
+     * @format date-time
+     * @example "2022-07-31T23:59:59Z"
      */
-    sub_total_including_taxes_amount_cents: number;
+    to_datetime: string;
     /**
-     * The total sum of all prepaid credits discounted on the invoice. It calculates the cumulative discount amount applied by prepaid credits, expressed in cents.
-     * @example 0
+     * The date of creation of the invoice.
+     * @format date
+     * @example "2022-08-01"
      */
-    prepaid_credit_amount_cents: number;
+    issuing_date: string;
     /**
-     * The usage already billed in previous invoices. Only apply to `progressive_billing` and `subscription` invoices.
-     * @example 0
+     * A unique identifier associated with the invoice related to this particular usage record.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    progressive_billing_credit_amount_cents: number;
+    lago_invoice_id?: string | null;
     /**
-     * The sum of the amount and taxes amount on the invoice, expressed in cents. It calculates the total financial value of the invoice, including both the original amount and any applicable taxes.
-     * @example 100
+     * The currency of the customer's current usage.
+     * @example "EUR"
      */
-    total_amount_cents: number;
-    /** @example 3 */
-    version_number: number;
+    currency?: Currency;
     /**
-     * Indicates if the invoice is self-billed. Self-billing is a process where an organization creates the invoice on behalf of the partner. This field specifies whether the invoice is self-billed or not.
-     * @example false
+     * The amount in cents, tax excluded.
+     * @example 123
      */
-    self_billed?: boolean;
+    amount_cents: number;
     /**
-     * Contains the URL that provides direct access to the invoice PDF file. You can use this URL to download or view the PDF document of the invoice
-     * @format uri
-     * @example "https://getlago.com/invoice/file"
+     * The projected amount in cents, tax excluded.
+     * @example 256
      */
-    file_url?: string;
+    projected_amount_cents: number;
     /**
-     * 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
-     * @format date-time
-     * @example "2022-04-29T08:59:51Z"
+     * The tax amount in cents.
+     * @example 200
      */
-    created_at: string;
+    taxes_amount_cents: number;
     /**
-     * The date of the invoice update, represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC). The update_date provides a standardized and internationally recognized timestamp for when the invoice object was updated
-     * @format date-time
-     * @example "2022-04-29T08:59:51Z"
+     * The total amount in cents, tax included.
+     * @example 123
      */
-    updated_at: string;
+    total_amount_cents: number;
+    /** Array of charges that comprise the current usage. It contains detailed information about individual charge items associated with the usage. */
+    charges_usage: CustomerChargeUsageObject[];
 }
-export interface BillingPeriodObject {
+export interface CustomerProjectedUsage {
+    customer_projected_usage: CustomerProjectedUsageObject;
+}
+export interface CustomerPastUsage {
+    usage_periods: CustomerUsage[];
+    meta: PaginationMeta;
+}
+/** . */
+export interface CustomerCheckoutUrl {
+    customer?: {
+        /**
+         * Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system
+         * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+         */
+        lago_customer_id: string;
+        /**
+         * The customer external unique identifier (provided by your own application)
+         * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
+         */
+        external_customer_id: string;
+        /**
+         * The Payment Provider name linked to the Customer.
+         * @example "stripe"
+         */
+        payment_provider: string;
+        /**
+         * Code of the payment provider
+         * @example "Stripe Prod"
+         */
+        payment_provider_code?: string;
+        /**
+         * The new generated Payment Provider Checkout URL for the Customer.
+         * @example "https://foo.bar"
+         */
+        checkout_url?: string;
+    };
+}
+export interface EventObject {
     /**
-     * Unique identifier assigned to the subscription, created by Lago.
+     * Unique identifier assigned to the event within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the event's record within the Lago system
      * @format uuid
      * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    lago_subscription_id: string;
+    lago_id: string;
     /**
-     * Unique identifier assigned to the subscription in your application.
-     * @example "external_id"
+     * This field represents a unique identifier for the event. It is crucial for ensuring idempotency, meaning that each event can be uniquely identified and processed without causing any unintended side effects.
+     * @example "transaction_1234567890"
      */
-    external_subscription_id: string;
+    transaction_id: string;
     /**
-     * Unique identifier assigned to the plan, created by Lago.
+     * Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system
      * @format uuid
      * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    lago_plan_id: string;
-    /**
-     * The beginning date of the subscription billing period. This field indicates the start date of the billing period associated with the subscription fee.
-     * @format date-time
-     * @example "2022-04-29T08:59:51Z"
-     */
-    subscription_from_datetime: string;
+    lago_customer_id: string | null;
     /**
-     * The ending date of the subscription billing period. This field indicates the end date of the billing period associated with the subscription fee.
-     * @format date-time
-     * @example "2022-05-29T08:59:51Z"
+     * The code that identifies a targeted billable metric. It is essential that this code matches the `code` property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
+     * @example "storage"
      */
-    subscription_to_datetime: string;
+    code: string;
     /**
-     * The beginning date of the period that covers the charge fees. It is applicable only to the `charge` fees attached to the subscription. This field indicates the start date of the billing period or subscription period associated with the fees.
+     * This field captures the Unix timestamp in seconds indicating the occurrence of the event in Coordinated Universal Time (UTC). If this timestamp is not provided, the API will automatically set it to the time of event reception.
      * @format date-time
-     * @example "2022-04-29T08:59:51Z"
+     * @example "2022-04-29T08:59:51.123Z"
      */
-    charges_from_datetime: string;
+    timestamp: string;
     /**
-     * The ending date of the period that covers the charge fees. It is applicable only to the `charge` fees attached to the subscription. This field indicates the end date of the billing period or subscription period associated with the fees.
-     * @format date-time
-     * @example "2022-05-29T08:59:51Z"
+     * The precise total amount that was sent in the event payload. This filed is used by the `dynamic` pricing model.
+     * @example "1234.56"
      */
-    charges_to_datetime: string;
+    precise_total_amount_cents?: string | null;
     /**
-     * The reason explaining why this subscription appears on the invoice.
-     * @example "subscription_starting"
+     * This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a `sum_agg`, `max_agg`, or `unique_count_agg` aggregation method. However, when using a simple `count_agg`, this object is not required.
+     * @example {"gb":10}
      */
-    invoicing_reason: "subscription_starting" | "subscription_periodic" | "subscription_terminating" | "in_advance_charge" | "in_advance_charge_periodic" | "progressive_billing";
-}
-export interface InvoiceMetadataObject {
+    properties?: {
+        /** The `operation_type` field is only necessary when adding or removing a specific unit when the targeted billable metric adopts a `unique_count_agg` aggregation method. In other cases, the `operation_type` field is not required. The valid values for the `operation_type` field are `add` or `remove`, which indicate whether the unit is being added or removed from the unique count aggregation, respectively. */
+        operation_type?: "add" | "remove";
+        [key: string]: any;
+    };
     /**
-     * Unique identifier assigned to the invoice metadata within the Lago application.
+     * Unique identifier assigned to the subscription within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the subscription's record within the Lago system
      * @format uuid
      * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    lago_id?: string;
-    /**
-     * Represents the key of the metadata's key-value pair.
-     * @example "digital_ref_id"
-     */
-    key?: string;
+    lago_subscription_id: string | null;
     /**
-     * Represents the value of the metadata's key-value pair.
-     * @example "INV-0123456-98765"
+     * The unique identifier of the subscription within your application. It is a mandatory field when the customer possesses multiple subscriptions or when the `external_customer_id` is not provided.
+     * @example "sub_1234567890"
      */
-    value?: string;
+    external_subscription_id: string;
     /**
-     * The date and time when the metadata object was created. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
+     * The creation date of the event's record in the Lago application, presented in the ISO 8601 datetime format, specifically in Coordinated Universal Time (UTC). It provides the precise timestamp of when the event's record was created within the Lago application
      * @format date-time
      * @example "2022-04-29T08:59:51Z"
      */
-    created_at?: string;
+    created_at: string;
 }
-export type InvoiceAppliedTaxObject = BaseAppliedTax & {
-    /**
-     * Unique identifier of the invoice, created by Lago.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_invoice_id?: string;
-    /**
-     * Fees total amount on which the tax is applied
-     * @example 20000
-     */
-    fees_amount_cents?: number;
-};
-export interface UsageThresholdObject {
+export interface EventsPaginated {
+    events: EventObject[];
+    meta: PaginationMeta;
+}
+export interface EventInputObject {
     /**
-     * Unique identifier of the usage threshold created by Lago.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+     * This field represents a unique identifier for the event.
+     * It is crucial for ensuring idempotency, meaning that each event can be uniquely identified and processed without causing any unintended side effects.
+     *
+     * WARNING: If the Lago organization is configured to use the new Clickhouse-based event pipeline (designed for high-volume processing), the idempotency logic is handled differently.
+     * Event uniqueness is maintained with both `transaction_id` and `timestamp` fields.
+     * If a new event arrives with identical values for these two fields as an existing event, the new one will overwrite the previous event rather than being rejected.
+     * @example "transaction_1234567890"
      */
-    lago_id: string;
+    transaction_id: string;
     /**
-     * The display name of the usage threshold.
-     * @example "Threshold 1"
+     * The unique identifier of the subscription in your application. This field is mandatory in order to link events to the correct customer subscription.
+     * @example "sub_1234567890"
      */
-    threshold_display_name: string | null;
+    external_subscription_id: string;
     /**
-     * The amount to reach to trigger a `progressive_billing` invoice.
-     * @example 10000
+     * The code that identifies a targeted billable metric. It is essential that this code matches the `code` property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
+     * @example "storage"
      */
-    amount_cents: number;
+    code: string;
     /**
-     * This field when set to `true` indicates that a `progressive_billing` invoice will be created every time the lifetime usage increases by the specified amount.
-     * @example true
+     * This field captures the Unix timestamp in seconds indicating the occurrence of the event in Coordinated Universal Time (UTC).
+     * If this timestamp is not provided, the API will automatically set it to the time of event reception.
+     * You can also provide miliseconds precision by appending decimals to the timestamp.
+     * @example "1651240791.123"
      */
-    recurring: boolean;
+    timestamp?: number | string;
     /**
-     * The date and time when the usage threshold was created. It is expressed in UTC format according to the ISO 8601 datetime standard.
-     * @format date-time
-     * @example "2023-06-27T19:43:42Z"
+     * The precise total amount in cents with precision used by the `dynamic` pricing model to compute the usage amount.
+     * @example "1234.56"
      */
-    created_at: string;
+    precise_total_amount_cents?: string | null;
     /**
-     * The date and time when the usage threshold was last updated. It is expressed in UTC format according to the ISO 8601 datetime standard.
-     * @format date-time
-     * @example "2023-06-27T19:43:42Z"
+     * This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a `sum_agg`, `max_agg`, or `unique_count_agg` aggregation method. However, when using a simple `count_agg`, this object is not required.
+     * @example {"gb":10}
      */
-    updated_at: string;
+    properties?: object | null;
 }
-export interface AppliedUsageThresholdObject {
-    /**
-     * The amount of usage in cents that has been accumulated over the lifetime of the subscription.
-     * @example 2000
-     */
-    lifetime_usage_amount_cents: number;
-    /**
-     * The date and time when the lifetime usage was computed. It is expressed in UTC format according to the ISO 8601 datetime standard.
-     * @format date-time
-     * @example "2025-03-31T12:31:44Z"
-     */
-    created_at: string;
-    usage_threshold: UsageThresholdObject;
+export interface EventInput {
+    event: EventInputObject;
 }
-export type InvoiceObject = InvoiceBaseObject & {
-    /** The customer on which the invoice applies. It refers to the customer account or entity associated with the invoice. */
-    customer?: CustomerObject;
-    billing_periods?: BillingPeriodObject[];
-    metadata?: InvoiceMetadataObject[];
-    applied_taxes?: InvoiceAppliedTaxObject[];
-    applied_usage_thresholds?: AppliedUsageThresholdObject[];
-};
-export interface InvoicesPaginated {
-    invoices: InvoiceObject[];
-    meta: PaginationMeta;
+export interface EventCreated {
+    event: EventObject & {
+        /**
+         * The value will always be null in this response as the event processing is done asynchronously
+         * @example null
+         */
+        lago_customer_id?: null;
+    };
 }
-export interface InvoiceOneOffCreateInput {
-    invoice: {
+export interface EventBatchInput {
+    events: EventInputObject[];
+}
+export interface EventsCreated {
+    events: (EventObject & {
         /**
-         * Unique identifier assigned to the customer in your application.
-         * @example "hooli_1234"
+         * The value will always be null in this response as the event processing is done asynchronously
+         * @example null
+         */
+        lago_customer_id?: null;
+    })[];
+}
+export interface EventEstimateFeesInput {
+    event: {
+        /**
+         * The code that identifies a targeted billable metric. It is essential that this code matches the `code` property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
+         * @example "storage"
+         */
+        code: string;
+        /**
+         * The unique identifier of the subscription within your application.
+         * @example "sub_1234567890"
+         */
+        external_subscription_id: string;
+        /** This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a `sum_agg`, `max_agg`, or `unique_count_agg` aggregation method. However, when using a simple `count_agg`, this object is not required. */
+        properties?: object;
+    };
+}
+export interface Fees {
+    fees: FeeObject[];
+}
+export interface EventEstimateInstantFeesInput {
+    event: {
+        /**
+         * The code that identifies a targeted billable metric. It is essential that this code matches the `code` property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
+         * @example "storage"
+         */
+        code: string;
+        /**
+         * The unique identifier of the subscription within your application.
+         * @example "sub_1234567890"
          */
-        external_customer_id: string;
+        external_subscription_id: string;
+        /** This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a `sum_agg`, `max_agg`, or `unique_count_agg` aggregation method. However, when using a simple `count_agg`, this object is not required. */
+        properties?: object;
         /**
-         * The currency of the invoice.
-         * @example "EUR"
+         * This field represents a unique identifier for the event.
+         * @example "transaction_1234567890"
          */
-        currency?: Currency;
-        fees: {
-            /**
-             * The code of the add-on used as invoice item.
-             * @example "setup_fee"
-             */
-            add_on_code: string;
-            /**
-             * Specifies the name that will be displayed on an invoice. If no value is set for this field, the name of the actual charge will be used as the default display name.
-             * @example "Setup Fee (SF1)"
-             */
-            invoice_display_name?: string;
-            /**
-             * The amount of the fee per unit, expressed in cents. By default, the amount of the add-on is used.
-             * @example 12000
-             */
-            unit_amount_cents?: number | null;
-            /**
-             * The quantity of units associated with the fee. By default, only 1 unit is added to the invoice.
-             * @pattern ^[0-9]+.?[0-9]*$
-             * @example "2.5"
-             */
-            units?: string | null;
-            /**
-             * This is a description
-             * @example "The description of the fee line item in the invoice. By default, the description of the add-on is used."
-             */
-            description?: string | null;
-            /**
-             * The lower boundary of the invoice billing interval. The `from_datetime` should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
-             * @format date-time
-             * @example "2022-08-08T00:00:00Z"
-             */
-            from_datetime?: string;
-            /**
-             * The upper boundary of the invoice billing interval. The `to_datetime` should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
-             * @format date-time
-             * @example "2022-08-08T00:00:00Z"
-             */
-            to_datetime?: string;
-            /** List of unique code used to identify the taxes. */
-            tax_codes?: TaxCodes;
-            /**
-             * If true, the invoice will be created but not sent to the payment provider.
-             * @default false
-             * @example true
-             */
-            skip_psp?: boolean | null;
-        }[];
+        transaction_id?: string | null;
     };
 }
-export interface SubscriptionObject {
+export interface FeeEstimateObject {
+    lago_id?: null;
     /**
-     * Unique identifier assigned to the subscription within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the subscription's record within the Lago system
+     * Unique identifier assigned to the charge that the fee belongs to
      * @format uuid
      * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    lago_id: string;
+    lago_charge_id?: string;
     /**
-     * The subscription external unique identifier (provided by your own application).
-     * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
+     * Unique identifier assigned to the charge filter that the fee belongs to
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    external_id: string;
+    lago_charge_filter_id?: string | null;
+    lago_invoice_id?: null;
+    lago_true_up_fee_id?: null;
+    lago_true_up_parent_fee_id?: null;
     /**
-     * Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system
+     * Unique identifier assigned to the subscription, created by Lago. This field is specifically displayed when the fee type is charge or subscription.
      * @format uuid
      * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    lago_customer_id: string;
+    lago_subscription_id?: string;
     /**
-     * The customer external unique identifier (provided by your own application).
-     * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
+     * Unique identifier assigned to the customer, created by Lago. This field is specifically displayed when the fee type is charge or subscription.
+     * @format uuid
+     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
      */
-    external_customer_id: string;
+    lago_customer_id?: string;
     /**
-     * The billing time for the subscription, which can be set as either `anniversary` or `calendar`. If not explicitly provided, it will default to `calendar`. The billing time determines the timing of recurring billing cycles for the subscription. By specifying `anniversary`, the billing cycle will be based on the specific date the subscription started (billed fully), while `calendar` sets the billing cycle at the first day of the week/month/year (billed with proration).
-     * @example "anniversary"
+     * Unique identifier assigned to the customer in your application. This field is specifically displayed when the fee type is charge or subscription.
+     * @example "external_id"
      */
-    billing_time: "calendar" | "anniversary";
+    external_customer_id?: string;
     /**
-     * The display name of the subscription on an invoice. This field allows for customization of the subscription's name for billing purposes, especially useful when a single customer has multiple subscriptions using the same plan.
-     * @example "Repository A"
+     * Unique identifier assigned to the subscription in your application. This field is specifically displayed when the fee type is charge or subscription.
+     * @example "external_id"
      */
-    name: string | null;
+    external_subscription_id?: string;
     /**
-     * The unique code representing the plan to be attached to the customer. This code must correspond to the `code` property of one of the active plans.
-     * @example "premium"
+     * The cost of this specific fee, excluding any applicable taxes.
+     * @example 100
      */
-    plan_code: string;
+    amount_cents: number;
     /**
-     * The status of the subscription, which can have the following values:
-     * - `active`: the subscription is currently active and applied to the customer.
-     * - `canceled`: the subscription has been stopped before its activation. This can occur when two consecutive downgrades have been applied to a customer or when a subscription with a pending status is terminated.
-     * - `pending`: a previous subscription has been downgraded, and the current one is awaiting automatic activation at the end of the billing period.
-     * - `terminated`: the subscription is no longer active.
-     * @example "active"
+     * The cost of this specific fee, excluding any applicable taxes, with precision.
+     * @example 1.0001
      */
-    status: "active" | "canceled" | "pending" | "terminated";
+    precise_amount?: number;
     /**
-     * The creation date of the subscription, represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC). This date provides a timestamp indicating when the subscription was initially created.
-     * @format date-time
-     * @example "2022-08-08T00:00:00Z"
+     * The cost of this specific fee, including any applicable taxes, with precision.
+     * @example 1.0212
      */
-    created_at: string;
+    precise_total_amount?: number;
     /**
-     * The cancellation date of the subscription. This field is not null when the subscription is `canceled`. This date should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-09-14T16:35:31Z"
+     * The currency of this specific fee. It indicates the monetary unit in which the fee's cost is expressed.
+     * @example "EUR"
      */
-    canceled_at: string | null;
+    amount_currency: Currency;
     /**
-     * The effective start date of the subscription. This field can be null if the subscription is `pending` or `canceled`. This date should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-08-08T00:00:00Z"
+     * The cost of the tax associated with this specific fee.
+     * @example 0
      */
-    started_at: string | null;
+    taxes_amount_cents: number;
     /**
-     * The effective end date of the subscription. If this field is set to null, the subscription will automatically renew. This date should be provided in ISO 8601 datetime format, and use Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-10-08T00:00:00Z"
+     * The cost of the tax associated with this specific fee, with precision.
+     * @example 0
      */
-    ending_at: string | null;
+    taxes_precise_amount?: number;
     /**
-     * The anniversary date and time of the initial subscription. This date serves as the basis for billing subscriptions with `anniversary` billing time. The `anniversary_date` should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-08-08T00:00:00Z"
+     * The tax rate associated with this specific fee.
+     * @example 20
      */
-    subscription_at: string;
+    taxes_rate: number;
     /**
-     * The termination date of the subscription. This field is not null when the subscription is `terminated`. This date should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC)
-     * @format date-time
-     * @example "2022-09-14T16:35:31Z"
+     * The number of units used to charge the customer. This field indicates the quantity or count of units consumed or utilized in the context of the charge. It helps in determining the basis for calculating the fee or cost associated with the usage of the service or product provided to the customer.
+     * @example "0.32"
      */
-    terminated_at: string | null;
+    units: string;
+    description?: null;
     /**
-     * The code identifying the previous plan associated with this subscription.
-     * @example null
+     * The unit amount of the fee per unit, with precision.
+     * @example 312.5
      */
-    previous_plan_code: string | null;
+    precise_unit_amount: number;
     /**
-     * The code identifying the next plan in the case of a downgrade.
-     * @example null
+     * The coupon amount applied to the estimated instant fee. It will always returns 0
+     * @example "0.0"
      */
-    next_plan_code: string | null;
+    precise_coupons_amount_cents?: string;
     /**
-     * The date when the plan will be downgraded, represented in ISO 8601 date format.
-     * @format date
-     * @example "2022-04-30"
+     * The cost of this specific fee, including any applicable taxes.
+     * @example 120
      */
-    downgrade_plan_date: string | null;
+    total_amount_cents: number;
     /**
-     * The date when the free trial is ended, represented in ISO 8601 date format.
-     * @format date-time
-     * @example "2022-08-08T00:00:00Z"
+     * The currency of this specific fee, including any applicable taxes.
+     * @example "EUR"
      */
-    trial_ended_at: string | null;
+    total_amount_currency: Currency;
     /**
-     * The date and time when the current billing period started, represented in ISO 8601 date format.
-     * @format date-time
-     * @example "2022-08-08T00:00:00Z"
+     * The number of events that have been sent and used to charge the customer. This field indicates the count or quantity of events that have been processed and considered in the charging process.
+     * @example 1
      */
-    current_billing_period_started_at: string | null;
+    events_count?: number;
     /**
-     * The date and time when the current billing period ends, represented in ISO 8601 date format.
-     * @format date-time
-     * @example "2022-09-08T00:00:00Z"
+     * Flag that indicates whether the fee was paid in advance. It serves as a boolean value, where `true` represents that the fee was paid in advance (straightaway), and `false` indicates that the fee was not paid in arrears (at the end of the period).
+     * @example true
      */
-    current_billing_period_ending_at: string | null;
+    pay_in_advance: boolean;
     /**
-     * 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.
-     * This field allows you to control the behavior of the credit note generation:
-     *
-     * - `credit`: A credit note is generated for the unused subscription time. The unused amount is credited back to the customer.
-     * - `refund`: A credit note is generated for the unused subscription time. If the invoice is paid or partially paid, the unused paid amount is refunded; any unpaid unused amount is credited back to the customer.
-     * - `skip`: No credit note is generated for the unused subscription time.
-     *
-     * _Note: This field is only applicable to pay-in-advance plans and will be `null` for pay-in-arrears plans._
-     * @example "credit"
+     * Flag that indicates whether the fee was included on the invoice. It serves as a boolean value, where `true` represents that the fee was included on the invoice, and `false` indicates that the fee was not included on the invoice.
+     * @example true
      */
-    on_termination_credit_note: "credit" | "refund" | "skip";
+    invoiceable: boolean;
     /**
-     * When a subscription is terminated before the end of its billing period, we generate an invoice for the unbilled usage.
-     * This field allows you to control the behavior of the invoice generation:
-     *
-     * - `generate`: An invoice is generated for the unbilled usage.
-     * - `skip`: No invoice is generated for the unbilled usage.
-     * @default "generate"
-     * @example "generate"
+     * Indicates the payment status of the fee. It represents the current status of the payment associated with the fee. The value will always `pending`.
+     * @example "pending"
      */
-    on_termination_invoice: "generate" | "skip";
+    payment_status: "pending";
+    created_at?: null;
+    succeeded_at?: null;
+    failed_at?: null;
+    refunded_at?: null;
+    /**
+     * Unique identifier assigned to the transaction. This field is specifically displayed when the fee type is `charge` and the payment for the fee is made in advance (`pay_in_advance` is set to `true`).
+     * @example "transaction_1234567890"
+     */
+    event_transaction_id?: string;
+    amount_details?: null;
+    /** Item attached to the fee */
+    item: {
+        /**
+         * The fee type. The value will be `charge`.
+         * @example "charge"
+         */
+        type: "charge";
+        /**
+         * The code of the fee item. It will be the code of the `billable_metric`.
+         * @example "startup"
+         */
+        code: string;
+        /**
+         * The name of the fee item. It will be the name of the `billable_metric`.
+         * @example "Startup"
+         */
+        name: string;
+        /**
+         * The description of the fee item. It will be the name of the `billable_metric`.
+         * @example "Startup description"
+         */
+        description?: string;
+        /**
+         * Specifies the name that will be displayed on an invoice. If no value is set for this field, the name of the actual charge will be used as the default display name.
+         * @example "Setup Fee (SF1)"
+         */
+        invoice_display_name?: string;
+        /**
+         * Specifies the name that will be displayed on an invoice. If no value is set for this field, the actual charge filter values will be used as the default display name.
+         * @example "AWS eu-east-1"
+         */
+        filter_invoice_display_name?: string | null;
+        /** Key value list of event properties */
+        filters?: object | null;
+        /**
+         * Unique identifier of the fee item, created by Lago. It will be the identifier of the `billable_metric`.
+         * @format uuid
+         * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+         */
+        lago_item_id: string;
+        /**
+         * The type of the fee item. Values is `BillableMetric`.
+         * @example "BillableMetric"
+         */
+        item_type: "BillableMetric";
+        /** Key value list of event properties aggregated by the charge model */
+        grouped_by?: Record<string, string>;
+    };
+}
+export interface FeesEstimate {
+    fees: FeeEstimateObject[];
+}
+export interface EventBatchEstimateInstantFeesInput {
+    events: EventEstimateInstantFeesInput[];
+}
+export interface Event {
+    event: EventObject;
+}
+export interface FeesPaginated {
+    fees: FeeObject[];
+    meta: PaginationMeta;
+}
+export interface Fee {
+    fee: FeeObject;
+}
+export interface FeeUpdateInput {
+    fee: {
+        /**
+         * The payment status of the fee. Possible values are `pending`, `succeeded`, `failed` or `refunded`.
+         * @example "succeeded"
+         */
+        payment_status: "pending" | "succeeded" | "failed" | "refunded";
+    };
+}
+export interface InvoiceOneOffCreateInput {
+    invoice: {
+        /**
+         * Unique identifier assigned to the customer in your application.
+         * @example "hooli_1234"
+         */
+        external_customer_id: string;
+        /**
+         * The currency of the invoice.
+         * @example "EUR"
+         */
+        currency?: Currency;
+        fees: {
+            /**
+             * The code of the add-on used as invoice item.
+             * @example "setup_fee"
+             */
+            add_on_code: string;
+            /**
+             * Specifies the name that will be displayed on an invoice. If no value is set for this field, the name of the actual charge will be used as the default display name.
+             * @example "Setup Fee (SF1)"
+             */
+            invoice_display_name?: string;
+            /**
+             * The amount of the fee per unit, expressed in cents. By default, the amount of the add-on is used.
+             * @example 12000
+             */
+            unit_amount_cents?: number | null;
+            /**
+             * The quantity of units associated with the fee. By default, only 1 unit is added to the invoice.
+             * @pattern ^[0-9]+.?[0-9]*$
+             * @example "2.5"
+             */
+            units?: string | null;
+            /**
+             * This is a description
+             * @example "The description of the fee line item in the invoice. By default, the description of the add-on is used."
+             */
+            description?: string | null;
+            /**
+             * The lower boundary of the invoice billing interval. The `from_datetime` should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
+             * @format date-time
+             * @example "2022-08-08T00:00:00Z"
+             */
+            from_datetime?: string;
+            /**
+             * The upper boundary of the invoice billing interval. The `to_datetime` should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
+             * @format date-time
+             * @example "2022-08-08T00:00:00Z"
+             */
+            to_datetime?: string;
+            /** List of unique code used to identify the taxes. */
+            tax_codes?: TaxCodes;
+            /**
+             * If true, the invoice will be created but not sent to the payment provider.
+             * @default false
+             * @example true
+             */
+            skip_psp?: boolean | null;
+        }[];
+    };
 }
 export interface ErrorDetailObject {
     /**
@@ -4846,67 +5256,6 @@ export interface OrganizationObject {
 export interface Organization {
     organization: OrganizationObject;
 }
-export interface PaymentObject {
-    /**
-     * Unique identifier of the payment, created by Lago.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_id: string;
-    /**
-     * The unique identifier of the paid resource, created by Lago.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_payable_id: string;
-    /**
-     * Unique identifier of the customer, created by Lago.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_customer_id: string;
-    /**
-     * The status of the payment within the payment provider
-     * @example "processing"
-     */
-    status: string;
-    /**
-     * The customer external unique identifier (provided by your own application)
-     * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
-     */
-    external_id?: string;
-    /**
-     * Unique identifier of the customer within the payment provider
-     * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
-     */
-    provider_customer_id: string;
-    /**
-     * Code of the payment provider
-     * @example "Stripe Prod"
-     */
-    payment_provider_code?: string;
-    /**
-     * The type of payment provider
-     * @example "stripe"
-     */
-    payment_provider_type: "adyen" | "cashfree" | "gocardless" | "stripe";
-    /**
-     * Unique identifier of the payment within the payment provider
-     * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
-     */
-    provider_payment_id: string;
-    next_action: Record<string, any>;
-    /**
-     * The amount of the payment in cents
-     * @example 1000
-     */
-    amount_cents?: number;
-    /**
-     * The currency of the payment
-     * @example "EUR"
-     */
-    amount_currency?: string;
-}
 export interface PaymentReceiptObject {
     /**
      * Unique identifier of the payment receipt, created by Lago.
@@ -4934,51 +5283,6 @@ export interface PaymentReceiptsPaginated {
 export interface PaymentReceipt {
     payment_receipt: PaymentReceiptObject;
 }
-export interface PaymentRequestObject {
-    /**
-     * Unique identifier of the payment request, created by Lago.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_id: string;
-    /**
-     * The customer's email address used for sending dunning notifications
-     * @format email
-     * @example "dinesh@piedpiper.test"
-     */
-    email: string;
-    /**
-     * The sum of the total amounts of all the invoices included in the payment request, expressed in cents.
-     * @example 100
-     */
-    amount_cents: number;
-    /**
-     * The currency of the payment request.
-     * @example "EUR"
-     */
-    amount_currency: Currency;
-    /**
-     * The status of the payment associated with the payment request. It can have one of the following values:
-     * - `pending`: the payment is pending, waiting for payment processing in the payment provider or when the invoice is emitted but users have not updated the payment status through the endpoint.
-     * - `succeeded`: the payment of the payment request has been successfully processed.
-     * - `failed`: the payment of the payment request has failed or encountered an error during processing.
-     * @example "succeeded"
-     */
-    payment_status: "pending" | "succeeded" | "failed";
-    /**
-     * The date and time when the payment request was created. It is expressed in UTC format according to the ISO 8601 datetime standard. This field provides the timestamp for the exact moment when the payment request was initially created.
-     * @format date-time
-     * @example "2022-04-29T08:59:51Z"
-     */
-    created_at: string;
-    /** The customer on which the payment request applies. It refers to the customer account or entity associated with the payment request. */
-    customer: CustomerBaseObject;
-    invoices: InvoiceBaseObject[];
-}
-export interface PaymentRequestsPaginated {
-    payment_requests: PaymentRequestObject[];
-    meta: PaginationMeta;
-}
 export interface PaymentRequestCreateInput {
     payment_request: {
         /**
@@ -4986,68 +5290,18 @@ export interface PaymentRequestCreateInput {
          * @example "5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba"
          */
         external_customer_id: string;
-        /**
-         * The customer's email address used for sending dunning notifications
-         * @format email
-         * @example "dinesh@piedpiper.test"
-         */
-        email: string;
-        /** A list of Lago IDs for the customer's overdue invoices to start the dunning process */
-        lago_invoice_ids: string[];
-    };
-}
-export interface PaymentRequest {
-    payment_request: PaymentRequestObject;
-}
-export interface PaymentManualObject {
-    /**
-     * The unique identifier of the payment, created by Lago.
-     * @format uuid
-     * @example "4cf085a7-c196-4f07-a543-97c50ec6e8b2"
-     */
-    lago_id?: string;
-    /** List of invoice IDs associated with the payment. */
-    invoice_ids?: string[];
-    /**
-     * The amount of the payment in cents.
-     * @example 100
-     */
-    amount_cents?: number;
-    /**
-     * The currency of the payment amount.
-     * @example "USD"
-     */
-    amount_currency?: string;
-    /**
-     * The current status of the payment.
-     * @example "succeeded"
-     */
-    payment_status?: string;
-    /**
-     * The type of payment.
-     * @example "manual"
-     */
-    type?: string;
-    /**
-     * Reference for the payment.
-     * @example "ref1"
-     */
-    reference?: string;
-    /**
-     * External identifier for the payment (if applicable).
-     * @example null
-     */
-    external_payment_id?: string | null;
-    /**
-     * Timestamp when the payment was created.
-     * @format date-time
-     * @example "2025-02-20T00:00:00Z"
-     */
-    created_at?: string;
+        /**
+         * The customer's email address used for sending dunning notifications
+         * @format email
+         * @example "dinesh@piedpiper.test"
+         */
+        email: string;
+        /** A list of Lago IDs for the customer's overdue invoices to start the dunning process */
+        lago_invoice_ids: string[];
+    };
 }
-export interface PaymentsPaginated {
-    payments: PaymentManualObject[];
-    meta: PaginationMeta;
+export interface PaymentRequest {
+    payment_request: PaymentRequestObject;
 }
 export interface PaymentCreateInput {
     payment: {
@@ -5075,7 +5329,7 @@ export interface PaymentCreateInput {
     };
 }
 export interface Payment {
-    payment: PaymentManualObject;
+    payment: PaymentObject;
 }
 export interface MinimumCommitmentObject {
     /**
@@ -5100,10 +5354,10 @@ export interface MinimumCommitmentObject {
      */
     invoice_display_name?: string;
     /**
-     * The interval used for recurring billing. It represents the frequency at which subscription billing occurs. The interval can be one of the following values: `yearly`, `quarterly`, `monthly` or `weekly`.
+     * The interval used for recurring billing. It represents the frequency at which subscription billing occurs. The interval can be one of the following values: `yearly`, `semiannual`, `quarterly`, `monthly` or `weekly`.
      * @example "monthly"
      */
-    interval?: "weekly" | "monthly" | "quarterly" | "yearly";
+    interval?: "weekly" | "monthly" | "quarterly" | "semiannual" | "yearly";
     /**
      * The date and time when the minimum commitment was created. It is expressed in UTC format according to the ISO 8601 datetime standard. This field provides the timestamp for the exact moment when the minimum commitment was initially created.
      * @format date-time
@@ -5446,10 +5700,10 @@ export interface PlanObject {
      */
     code: string;
     /**
-     * The interval used for recurring billing. It represents the frequency at which subscription billing occurs. The interval can be one of the following values: `yearly`, `quarterly`, `monthly` or `weekly`.
+     * The interval used for recurring billing. It represents the frequency at which subscription billing occurs. The interval can be one of the following values: `yearly`, `semiannual`, `quarterly`, `monthly` or `weekly`.
      * @example "monthly"
      */
-    interval: "weekly" | "monthly" | "quarterly" | "yearly";
+    interval: "weekly" | "monthly" | "quarterly" | "semiannual" | "yearly";
     /**
      * The description on the plan.
      * @example ""
@@ -5476,7 +5730,7 @@ export interface PlanObject {
      */
     pay_in_advance?: boolean;
     /**
-     * This field, when set to `true`, enables to invoice usage-based charges on monthly basis, even if the cadence of the plan is yearly. This allows customers to pay charges overage on a monthly basis. This can be set to true only if the plan's interval is `yearly`.
+     * This field, when set to `true`, enables to invoice usage-based charges on monthly basis, even if the cadence of the plan is yearly or semiannual. This allows customers to pay charges overage on a monthly basis. This can be set to true only if the plan's interval is `yearly` or `semiannual`.
      * @example null
      */
     bill_charges_monthly?: boolean | null;
@@ -5563,10 +5817,10 @@ export interface PlanCreateInput {
          */
         code?: string;
         /**
-         * The interval used for recurring billing. It represents the frequency at which subscription billing occurs. The interval can be one of the following values: `yearly`, `quarterly`, `monthly`, or `weekly`.
+         * The interval used for recurring billing. It represents the frequency at which subscription billing occurs. The interval can be one of the following values: `yearly`, `semiannual`, `quarterly`, `monthly`, or `weekly`.
          * @example "monthly"
          */
-        interval?: "weekly" | "monthly" | "quarterly" | "yearly";
+        interval?: "weekly" | "monthly" | "quarterly" | "semiannual" | "yearly";
         /**
          * The description on the plan.
          * @example "Plan for early stage startups."
@@ -5593,7 +5847,7 @@ export interface PlanCreateInput {
          */
         pay_in_advance?: boolean;
         /**
-         * This field, when set to `true`, enables to invoice usage-based charges on monthly basis, even if the cadence of the plan is yearly. This allows customers to pay charges overage on a monthly basis. This can be set to true only if the plan's interval is `yearly`.
+         * This field, when set to `true`, enables to invoice usage-based charges on monthly basis, even if the cadence of the plan is `yearly` or `semiannual`. This allows customers to pay charges overage on a monthly basis. This can be set to true only if the plan's interval is `yearly` or `semiannual`.
          * @example null
          */
         bill_charges_monthly?: boolean | null;
@@ -5708,10 +5962,10 @@ export interface PlanUpdateInput {
          */
         code?: string;
         /**
-         * The interval used for recurring billing. It represents the frequency at which subscription billing occurs. The interval can be one of the following values: `yearly`, `quarterly`, `monthly`, or `weekly`.
+         * The interval used for recurring billing. It represents the frequency at which subscription billing occurs. The interval can be one of the following values: `yearly`, `semiannual`, `quarterly`, `monthly`, or `weekly`.
          * @example "monthly"
          */
-        interval?: "weekly" | "monthly" | "quarterly" | "yearly";
+        interval?: "weekly" | "monthly" | "quarterly" | "semiannual" | "yearly";
         /**
          * The description on the plan.
          * @example "Plan for early stage startups."
@@ -5738,7 +5992,7 @@ export interface PlanUpdateInput {
          */
         pay_in_advance?: boolean;
         /**
-         * This field, when set to `true`, enables to invoice usage-based charges on monthly basis, even if the cadence of the plan is yearly. This allows customers to pay charges overage on a monthly basis. This can be set to true only if the plan's interval is `yearly`.
+         * This field, when set to `true`, enables to invoice usage-based charges on monthly basis, even if the cadence of the plan is yearly or semiannual. This allows customers to pay charges overage on a monthly basis. This can be set to true only if the plan's interval is `yearly` or `semiannual`.
          * @example null
          */
         bill_charges_monthly?: boolean | null;
@@ -5848,10 +6102,6 @@ export interface EntitlementUpdateInput {
      */
     entitlements: Record<string, Record<string, number | boolean | string>>;
 }
-export interface SubscriptionsPaginated {
-    subscriptions: SubscriptionObject[];
-    meta: PaginationMeta;
-}
 /** Based plan overrides. */
 export interface PlanOverridesObject {
     /**
@@ -5944,28 +6194,28 @@ export interface PlanOverridesObject {
     usage_thresholds?: UsageThresholdInput[];
 }
 export interface SubscriptionCreateInput {
-    subscription: {
+    /**
+     * Optionally, you can create a pre-authorization on the customer's card before creating a subscription. This process places a temporary hold (capture) for a specified amount on the customer's account, but does not actually withdraw the funds.
+     *
+     * Important notes:
+     *   - The final amount due for the subscription is not known at the time of creation; it is determined only after the invoice is finalized.
+     *   - The payment intent generated for pre-authorization cannot be reused, as the final invoice amount may exceed the authorized amount.
+     *   - The payment intent is canceled immediately after creation, but this cancellation occurs asynchronously.
+     *   - For these reasons, it is recommended to use a small amount (such as $1) for pre-authorization. While this does not guarantee sufficient funds for the final payment, it helps reduce the likelihood of payment errors.
+     */
+    authorization?: {
         /**
-         * Optionally, you can create a pre-authorization on the customer's card before creating a subscription. This process places a temporary hold (capture) for a specified amount on the customer's account, but does not actually withdraw the funds.
-         *
-         * Important notes:
-         *   - The final amount due for the subscription is not known at the time of creation; it is determined only after the invoice is finalized.
-         *   - The payment intent generated for pre-authorization cannot be reused, as the final invoice amount may exceed the authorized amount.
-         *   - The payment intent is canceled immediately after creation, but this cancellation occurs asynchronously.
-         *   - For these reasons, it is recommended to use a small amount (such as $1) for pre-authorization. While this does not guarantee sufficient funds for the final payment, it helps reduce the likelihood of payment errors.
+         * The amount of the authorization in cents.
+         * @example 1000
          */
-        authorization?: {
-            /**
-             * The amount of the authorization in cents.
-             * @example 1000
-             */
-            amount_cents: number;
-            /**
-             * The currency of the authorization.
-             * @example "USD"
-             */
-            amount_currency: string;
-        };
+        amount_cents: number;
+        /**
+         * The currency of the authorization.
+         * @example "USD"
+         */
+        amount_currency: string;
+    };
+    subscription: {
         /**
          * The code of the billing entity to be used for the subscription. If not provided, the default billing entity will be used.
          * @example "default"
@@ -6344,225 +6594,6 @@ export interface Tax {
 export interface TaxUpdateInput {
     tax: TaxBaseInput;
 }
-/** Object that represents rule for wallet recurring transactions. */
-export interface WalletRecurringTransactionRule {
-    /**
-     * A unique identifier for the recurring transaction rule in the Lago application. Can be used to update a recurring transaction rule.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_id: string;
-    /**
-     * The trigger. Possible values are `interval` or `threshold`.
-     * @example "interval"
-     */
-    trigger: "interval" | "threshold";
-    /**
-     * The method used for recurring top-up. Possible values are `fixed` or `target`.
-     * @example "target"
-     */
-    method: "fixed" | "target";
-    /**
-     * The interval used for recurring top-up. It represents the frequency at which automatic top-up occurs. The interval can be one of the following values: `weekly`, `monthly`, `quarterly` or `yearly`. Required only if trigger is set to `interval`.
-     * @example "monthly"
-     */
-    interval: "weekly" | "monthly" | "quarterly" | "yearly";
-    /**
-     * The status of the recurring transaction rule. Possible values are `active` or `terminated`.
-     * @example "active"
-     */
-    status?: "active" | "terminated";
-    /**
-     * The threshold for recurring top-ups is the value at which an automatic top-up is triggered. For example, if this threshold is set at 10 credits, an automatic top-up will occur whenever the wallet balance falls to or below 10 credits. Required only when trigger is set to `threshold`.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "20.0"
-     */
-    threshold_credits: string;
-    /**
-     * The number of paid credits. Required only if there is no granted credits.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "20.0"
-     */
-    paid_credits: string;
-    /**
-     * The number of free granted credits. Required only if there is no paid credits.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "10.0"
-     */
-    granted_credits: string;
-    /**
-     * The effective start date for recurring top-ups. This date should be provided in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-08-08T00:00:00Z"
-     */
-    started_at?: string | null;
-    /**
-     * The target ongoing balance is the value set for the ongoing balance to be reached by the automatic top-up. Required only when trigger is set to `target`.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "200.0"
-     */
-    target_ongoing_balance: string | null;
-    /**
-     * The date of the metadata object 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 metadata object was created
-     * @format date-time
-     * @example "2022-04-29T08:59:51Z"
-     */
-    created_at: string;
-    /**
-     * The expiration date and time for this specific recurring transaction rule. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2023-09-30T23:59:59Z"
-     */
-    expiration_at?: string | null;
-    /**
-     * A boolean setting that, when set to true, delays issuing an invoice for a wallet top-up until a successful payment is made; if false, the invoice is issued immediately upon wallet top-up, regardless of the payment status. Default value of false.
-     * @example false
-     */
-    invoice_requires_successful_payment?: boolean;
-    /**
-     * This field allows you to store a list of key-value pairs containing additional information or custom attributes. These key-value pairs will populate the metadata of the wallet transactions triggered by this rule.
-     * @example [{"key":"example_key","value":"example_value"},{"key":"another_key","value":"another_value"}]
-     */
-    transaction_metadata?: {
-        /** The unique identifier for the attribute. */
-        key?: string;
-        /** The value associated with the key. */
-        value?: string;
-    }[];
-}
-export interface WalletObject {
-    /**
-     * Unique identifier assigned to the wallet within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the wallet's record within the Lago system.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_id: string;
-    /**
-     * Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system.
-     * @format uuid
-     * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
-     */
-    lago_customer_id: string;
-    /**
-     * The customer external unique identifier (provided by your own application)
-     * @example "hooli_1234"
-     */
-    external_customer_id: string;
-    /**
-     * The status of the wallet. Possible values are `active` or `terminated`.
-     * @example "active"
-     */
-    status: "active" | "terminated";
-    /**
-     * The currency of the wallet.
-     * @example "USD"
-     */
-    currency: Currency;
-    /**
-     * The name of the wallet.
-     * @example "Prepaid"
-     */
-    name?: string | null;
-    /**
-     * The rate of conversion between credits and the amount in the specified currency. It indicates the ratio or factor used to convert credits into the corresponding monetary value in the currency of the transaction.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "1.5"
-     */
-    rate_amount: string;
-    /**
-     * The current wallet balance expressed in credits. This reflects the available balance after all transactions are settled.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "28.0"
-     */
-    credits_balance: string;
-    /**
-     * The current wallet balance expressed in cents. This reflects the available balance after all transactions are settled.
-     * @example 1000
-     */
-    balance_cents: number;
-    /**
-     * The number of consumed credits.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "2.0"
-     */
-    consumed_credits: string;
-    /**
-     * The date of the wallet creation, represented in ISO 8601 datetime format and expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-04-29T08:59:51Z"
-     */
-    created_at: string;
-    /**
-     * The date and time that determines when the wallet will expire. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example null
-     */
-    expiration_at?: string | null;
-    /**
-     * The date and time of the last balance top-up. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-04-29T08:59:51Z"
-     */
-    last_balance_sync_at?: string | null;
-    /**
-     * The date and time of the last credits consumption. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-04-29T08:59:51Z"
-     */
-    last_consumed_credit_at?: string | null;
-    /**
-     * The date of terminaison of the wallet. It follows the ISO 8601 datetime format and is expressed in Coordinated Universal Time (UTC).
-     * @format date-time
-     * @example "2022-09-14T16:35:31Z"
-     */
-    terminated_at?: string | null;
-    /**
-     * A boolean setting that, when set to true, delays issuing an invoice for a wallet top-up until a successful payment is made; if false, the invoice is issued immediately upon wallet top-up, regardless of the payment status. Default value of false.
-     * @example false
-     */
-    invoice_requires_successful_payment: boolean;
-    /** Set wallet limitations to fee types. */
-    applies_to?: {
-        /**
-         * An array of fee types to which the wallet is applicable. By specifying the fee types in this field, you can restrict the wallet's usage to specific fee types only.
-         * @example ["charge"]
-         */
-        fee_types?: ("charge" | "subscription" | "commitment")[];
-        /**
-         * 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 ["bm1"]
-         */
-        billable_metric_codes?: string[];
-    };
-    /** List of recurring transaction rules. Currently, we only allow one recurring rule per wallet. */
-    recurring_transaction_rules?: WalletRecurringTransactionRule[];
-    /**
-     * The ongoing wallet balance expressed in cents. This represents the `balance_cents` minus the `ongoing_usage_balance_cents`, showing the real time balance after accounting for current usage including taxes.
-     * @example 800
-     */
-    ongoing_balance_cents: number;
-    /**
-     * The ongoing usage balance of the wallet, expressed in cents. This reflects all current usage and draft invoices including taxes.
-     * @example 200
-     */
-    ongoing_usage_balance_cents: number;
-    /**
-     * The ongoing wallet balance expressed in credits. This represents the `credits_balance` minus the `credits_ongoing_usage_balance`, showing the real time balance after accounting for current usage including taxes.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "8.0"
-     */
-    credits_ongoing_balance: string;
-    /**
-     * The ongoing usage balance of the wallet, expressed in credits. This reflects all current usage and draft invoices including taxes.
-     * @pattern ^[0-9]+.?[0-9]*$
-     * @example "2.0"
-     */
-    credits_ongoing_usage_balance: string;
-}
-export interface WalletsPaginated {
-    wallets: WalletObject[];
-    meta: PaginationMeta;
-}
 export interface WalletCreateInput {
     wallet?: {
         /**
@@ -6614,6 +6645,11 @@ export interface WalletCreateInput {
          * @example [{"key":"example_key","value":"example_value"},{"key":"another_key","value":"another_value"}]
          */
         transaction_metadata?: any[] | null;
+        /**
+         * The name of the wallet transactions triggered when creating the wallet. It will appear on the invoice as the label for the fee. If not set, the label on the invoice will fallback to either `Prepaid credits - {{wallet_name}}` if the wallet name is set, or `Prepaid credits`.
+         * @example "Tokens for models 'high-fidelity-boost'"
+         */
+        transaction_name?: string | null;
         /** Set wallet limitations to fee types. */
         applies_to?: {
             /**
@@ -6627,6 +6663,21 @@ export interface WalletCreateInput {
              */
             billable_metric_codes?: any[] | null;
         };
+        /**
+         * Minimum amount of cents that can be top-up with a single paid transaction.
+         * @example 100
+         */
+        paid_top_up_min_amount_cents?: number | null;
+        /**
+         * Maximum amount of cents that can be top-up with a single paid transaction.
+         * @example 1000
+         */
+        paid_top_up_max_amount_cents?: number | null;
+        /**
+         * If set to true, the wallet will ignore paid top-up limits on creation.
+         * @example false
+         */
+        ignore_paid_top_up_limits_on_creation?: boolean | null;
         /** List of recurring transaction rules. Currently, we only allow one recurring rule per wallet. */
         recurring_transaction_rules?: any[] | null;
     };
@@ -6671,10 +6722,10 @@ export interface WalletUpdateInput {
              */
             method?: "fixed" | "target";
             /**
-             * The interval used for recurring top-up. It represents the frequency at which automatic top-up occurs. The interval can be one of the following values: `weekly`, `monthly`, `quarterly` or `yearly`. Required only when trigger is set to `interval`.
+             * The interval used for recurring top-up. It represents the frequency at which automatic top-up occurs. The interval can be one of the following values: `weekly`, `monthly`, `quarterly`, `semiannual` or `yearly`. Required only when trigger is set to `interval`.
              * @example "monthly"
              */
-            interval?: "weekly" | "monthly" | "quarterly" | "yearly";
+            interval?: "weekly" | "monthly" | "quarterly" | "semiannual" | "yearly";
             /**
              * The threshold for recurring top-ups is the value at which an automatic top-up is triggered. For example, if this threshold is set at 10 credits, an automatic top-up will occur whenever the wallet balance falls to or below 10 credits. Required only when trigger is set to `threshold`.
              * @pattern ^[0-9]+.?[0-9]*$
@@ -6726,6 +6777,11 @@ export interface WalletUpdateInput {
                 /** The value associated with the key. */
                 value?: string;
             }[];
+            /**
+             * The name of the wallet transactions triggered by this rule. It will appear on the invoice as the label for the fee. If not set, the label on the invoice will fallback to either `Prepaid credits - {{wallet_name}}` if the wallet name is set, or `Prepaid credits`.
+             * @example "Tokens for models 'high-fidelity-boost'"
+             */
+            transaction_name?: string | null;
         }[];
         /** Set wallet limitations to fee types. */
         applies_to?: {
@@ -6780,6 +6836,11 @@ export interface WalletTransactionCreateInput {
          * @example false
          */
         invoice_requires_successful_payment?: boolean;
+        /**
+         * When true, allows topping up the wallet with transactions that exceed the paid top-up limits. Defaults to false.
+         * @example false
+         */
+        ignore_paid_top_up_limits?: boolean;
         /**
          * This optional field allows you to store a list of key-value pairs that hold additional information or custom attributes related to the data.
          * @example [{"key":"example key","value":"example value"},{"key":"another key","value":"another value"}]
@@ -7465,7 +7526,7 @@ export declare class HttpClient<SecurityDataType = unknown> {
 }
 /**
  * @title Lago API documentation
- * @version 1.33.3
+ * @version 1.36.0
  * @license AGPLv3
  * @baseUrl https://api.getlago.com/api/v1
  * @externalDocs https://github.com/getlago
@@ -7803,7 +7864,8 @@ export declare class Api<SecurityDataType extends unknown> extends HttpClient<Se
              *
              * - Revenue from `monthly` subscription invoices is included in the MRR for the month in which the invoice is issued.
              * - Revenue from `quarterly` subscription invoices is distributed evenly over three months. This distribution applies to fees paid in advance (allocated to the next remaining months depending on calendar or anniversary billing) as well as to fees paid in arrears (allocated to the preceding months depending on calendar or anniversary billing).
-             * - Revenue from `yearly` subscription invoices is distributed evenly over twelve months. This allocation is applicable for fees paid in advance (spread over the next  remaining months depending on calendar or anniversary billing) and for fees paid in arrears (spread over the previous months depending on calendar or anniversary billing).
+             * - Revenue from `yearly` subscription invoices is distributed evenly over twelve months. This allocation is applicable for fees paid in advance (spread over the next remaining months depending on calendar or anniversary billing) and for fees paid in arrears (spread over the previous months depending on calendar or anniversary billing).
+             * - Revenue from `semiannual` subscription invoices is distributed evenly over six months. This allocation is applicable for fees paid in advance (spread over the next remaining months depending on calendar or anniversary billing) and for fees paid in arrears (spread over the previous months depending on calendar or anniversary billing).
              * - Revenue from `weekly` subscription invoices, the total revenue from all invoices issued within a month is summed up. This total is then divided by the number of invoices issued during that month, and the result is multiplied by 4.33, representing the average number of weeks in a month.
              */
             currency?: Currency;
@@ -8340,6 +8402,51 @@ export declare class Api<SecurityDataType extends unknown> extends HttpClient<Se
              * @example ["billing_entity_code_1","billing_entity_code_2"]
              */
             "billing_entity_codes[]"?: string[];
+            /**
+             * Filter customers by search term. This will filter all customers whose name, firstname, lastname, legal name, external id or email contain the search term.
+             * @example "John Doe"
+             */
+            search_term?: string;
+            /**
+             * Filter customers by countries. Possible values are the ISO 3166-1 alpha-2 codes.
+             * @example ["US","FR"]
+             */
+            "countries[]"?: Country[];
+            /**
+             * Filter customers by states.
+             * @example ["CA","Paris"]
+             */
+            "states[]"?: string[];
+            /**
+             * Filter customers by zipcodes.
+             * @example ["10115","75001"]
+             */
+            "zipcodes[]"?: string[];
+            /**
+             * Filter customers by currencies.
+             * @example ["USD","EUR"]
+             */
+            "currencies[]"?: Currency[];
+            /**
+             * Filter customers by whether they have a tax identification number or not.
+             * @example true
+             */
+            has_tax_identification_number?: boolean;
+            /**
+             * Filter customers by metadata. Replace `key` with the actual metadata key you want to match, and provide the corresponding value. Providing empty value will search for customers without given metadata key. For example, `metadata[is_synced]=true&metadata[last_synced_at]=`.
+             * @example "value"
+             */
+            "metadata[key]"?: string;
+            /**
+             * Filter customers by customer type.
+             * @example "company"
+             */
+            customer_type?: "company" | "individual";
+            /**
+             * Filter customers by whether they have a customer type or not.
+             * @example true
+             */
+            has_customer_type?: boolean;
         }, params?: RequestParams) => Promise<HttpResponse<CustomersPaginated, ApiErrorUnauthorized>>;
         /**
          * @description This endpoint retrieves an existing customer.
@@ -8361,6 +8468,37 @@ export declare class Api<SecurityDataType extends unknown> extends HttpClient<Se
          * @secure
          */
         destroyCustomer: (externalCustomerId: string, params?: RequestParams) => Promise<HttpResponse<Customer, ApiErrorUnauthorized | ApiErrorNotFound>>;
+        /**
+         * @description This endpoint is used to list all applied coupons for a customer.
+         *
+         * @tags customers, coupons
+         * @name FindAllCustomerAppliedCoupons
+         * @summary List all customer's applied coupons
+         * @request GET:/customers/{external_customer_id}/applied_coupons
+         * @secure
+         */
+        findAllCustomerAppliedCoupons: (externalCustomerId: string, query?: {
+            /**
+             * Page number.
+             * @example 1
+             */
+            page?: number;
+            /**
+             * Number of records per page.
+             * @example 20
+             */
+            per_page?: number;
+            /**
+             * The status of the coupon. Can be either `active` or `terminated`.
+             * @example "active"
+             */
+            status?: "active" | "terminated";
+            /**
+             * The code of the coupon applied to the customer. Use it to filter applied coupons by their code.
+             * @example ["BLACK_FRIDAY_2024","CHRISTMAS_2024"]
+             */
+            "coupon_code[]"?: string[];
+        }, params?: RequestParams) => Promise<HttpResponse<AppliedCouponsPaginated, ApiErrorUnauthorized | ApiErrorNotFound>>;
         /**
          * @description This endpoint is used to delete a specific coupon that has been applied to a customer.
          *
@@ -8371,6 +8509,197 @@ export declare class Api<SecurityDataType extends unknown> extends HttpClient<Se
          * @secure
          */
         deleteAppliedCoupon: (externalCustomerId: string, appliedCouponId: string, params?: RequestParams) => Promise<HttpResponse<AppliedCoupon, ApiErrorUnauthorized | ApiErrorNotFound>>;
+        /**
+         * @description This endpoint list all existing credit notes for a customer.
+         *
+         * @tags customers, credit_notes
+         * @name FindAllCustomerCreditNotes
+         * @summary List all customer's credit notes
+         * @request GET:/customers/{external_customer_id}/credit_notes
+         * @secure
+         */
+        findAllCustomerCreditNotes: (externalCustomerId: string, query?: {
+            /**
+             * Page number.
+             * @example 1
+             */
+            page?: number;
+            /**
+             * Number of records per page.
+             * @example 20
+             */
+            per_page?: number;
+            /**
+             * Filter credit notes starting from a specific date.
+             * @format date
+             * @example "2022-07-08"
+             */
+            issuing_date_from?: string;
+            /**
+             * Filter credit notes up to a specific date.
+             * @format date
+             * @example "2022-08-09"
+             */
+            issuing_date_to?: string;
+            /**
+             * Search credit notes by id, number, customer name, customer external_id or customer email.
+             * @example "Jane"
+             */
+            search_term?: string;
+            /** Filter credit notes by reasons. Possible values are `product_unsatisfactory`, `order_change`, `order_cancellation`, `fraudulent_charge`, `duplicated_charge` or `other`. */
+            reason?: "product_unsatisfactory" | "order_change" | "order_cancellation" | "fraudulent_charge" | "duplicated_charge" | "other";
+            /** Filter credit notes by credit status. Possible values are `available`, `consumed`  or `voided`. */
+            credit_status?: "available" | "consumed" | "voided";
+            /** Filter credit notes by refund status. Possible values are `pending`, `succeeded`  or `failed`. */
+            refund_status?: "pending" | "succeeded" | "failed";
+            /**
+             * Filter credit notes by their related invoice number.
+             * @example "INV-001-002"
+             */
+            invoice_number?: string;
+            /**
+             * Filter credit notes of at least a specific amount. This parameter must be defined in cents to ensure consistent handling for all currency types.
+             * @example 9000
+             */
+            amount_from?: number;
+            /**
+             * Filter credit notes up to a specific amount. This parameter must be defined in cents to ensure consistent handling for all currency types.
+             * @example 100000
+             */
+            amount_to?: number;
+            /**
+             * Filter credit notes belonging to a self billed invoice. Possible values are `true` or `false`.
+             * @example true
+             */
+            self_billed?: boolean;
+        }, params?: RequestParams) => Promise<HttpResponse<CreditNotesPaginated, ApiErrorUnauthorized | ApiErrorNotFound>>;
+        /**
+         * @description This endpoint is used for retrieving all invoices of a customer.
+         *
+         * @tags customers, invoices
+         * @name FindAllCustomerInvoices
+         * @summary List all customer's invoices
+         * @request GET:/customers/{external_customer_id}/invoices
+         * @secure
+         */
+        findAllCustomerInvoices: (externalCustomerId: string, query?: {
+            /**
+             * Page number.
+             * @example 1
+             */
+            page?: number;
+            /**
+             * Number of records per page.
+             * @example 20
+             */
+            per_page?: number;
+            /**
+             * Filter invoices of at least a specific amount. This parameter must be defined in cents to ensure consistent handling for all currency types.
+             * @example 9000
+             */
+            amount_from?: number;
+            /**
+             * Filter invoices up to a specific amount. This parameter must be defined in cents to ensure consistent handling for all currency types.
+             * @example 100000
+             */
+            amount_to?: number;
+            /**
+             * Filter invoices starting from a specific date.
+             * @format date
+             * @example "2022-07-08"
+             */
+            issuing_date_from?: string;
+            /**
+             * Filter invoices up to a specific date.
+             * @format date
+             * @example "2022-08-09"
+             */
+            issuing_date_to?: string;
+            /** Filter invoices by status. Possible values are `draft` or `finalized`. */
+            status?: "draft" | "finalized";
+            /** Filter invoices by payment status. Possible values are `pending`, `failed` or `succeeded`. */
+            payment_status?: "pending" | "failed" | "succeeded";
+            /**
+             * Filter invoices by payment_overdue. Possible values are `true` or `false`.
+             * @example true
+             */
+            payment_overdue?: boolean;
+            /**
+             * Search invoices by id, number, customer name, customer external_id or customer email.
+             * @example "Jane"
+             */
+            search_term?: string;
+            /**
+             * Filter invoices with a payment dispute lost. Possible values are `true` or `false`.
+             * @example true
+             */
+            payment_dispute_lost?: boolean;
+            /** Filter invoices by invoice type. Possible values are `subscription`, `add_on`, `credit`, `one_off`, `advance_charges` or `progressive_billing`. */
+            invoice_type?: "subscription" | "add_on" | "credit" | "one_off" | "advance_charges" | "progressive_billing";
+            /**
+             * Filter invoices by self billed. Possible values are `true` or `false`.
+             * @example true
+             */
+            self_billed?: boolean;
+            /**
+             * 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`.
+             * @example "someValue"
+             */
+            "metadata[key]"?: string;
+        }, params?: RequestParams) => Promise<HttpResponse<InvoicesPaginated, ApiErrorUnauthorized | ApiErrorUnprocessableEntity | ApiErrorNotFound>>;
+        /**
+         * @description This endpoint is used to list all payments of a customer
+         *
+         * @tags customers, payments
+         * @name FindAllCustomerPayments
+         * @summary List all customer's payments
+         * @request GET:/customers/{external_customer_id}/payments
+         * @secure
+         */
+        findAllCustomerPayments: (externalCustomerId: string, query?: {
+            /**
+             * Page number.
+             * @example 1
+             */
+            page?: number;
+            /**
+             * Number of records per page.
+             * @example 20
+             */
+            per_page?: number;
+            /**
+             * 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.
+             * @format uuid
+             * @example "1a901a90-1a90-1a90-1a90-1a901a901a90"
+             */
+            invoice_id?: string;
+        }, params?: RequestParams) => Promise<HttpResponse<PaymentsPaginated, ApiErrorUnauthorized | ApiErrorNotFound>>;
+        /**
+         * @description This endpoint is used to list all existing payment requests of a customer.
+         *
+         * @tags customers, payment_requests
+         * @name FindAllCustomerPaymentRequests
+         * @summary List all customer's payment requests
+         * @request GET:/customers/{external_customer_id}/payment_requests
+         * @secure
+         */
+        findAllCustomerPaymentRequests: (externalCustomerId: string, query?: {
+            /**
+             * Page number.
+             * @example 1
+             */
+            page?: number;
+            /**
+             * Number of records per page.
+             * @example 20
+             */
+            per_page?: number;
+            /**
+             * Filter by payment status. Possible values are `pending`, `failed` or `succeeded`.
+             * @example "pending"
+             */
+            payment_status?: "pending" | "failed" | "succeeded";
+        }, params?: RequestParams) => Promise<HttpResponse<PaymentRequestsPaginated, ApiErrorUnauthorized | ApiErrorNotFound>>;
         /**
          * @description Retrieves an embeddable link for displaying a customer portal. This endpoint allows you to fetch the URL that can be embedded to provide customers access to a dedicated portal
          *
@@ -8389,6 +8718,58 @@ export declare class Api<SecurityDataType extends unknown> extends HttpClient<Se
                 portal_url: string;
             };
         }, ApiErrorUnauthorized | ApiErrorNotFound>>;
+        /**
+         * @description This endpoint retrieves all active subscriptions for a customer.
+         *
+         * @tags customers, subscriptions
+         * @name FindAllCustomerSubscriptions
+         * @summary List all customer's subscriptions
+         * @request GET:/customers/{external_customer_id}/subscriptions
+         * @secure
+         */
+        findAllCustomerSubscriptions: (externalCustomerId: string, query?: {
+            /**
+             * Page number.
+             * @example 1
+             */
+            page?: number;
+            /**
+             * Number of records per page.
+             * @example 20
+             */
+            per_page?: number;
+            /**
+             * The unique code representing the plan to be attached to the customer. This code must correspond to the code property of one of the active plans.
+             * @example "premium"
+             */
+            plan_code?: string;
+            /**
+             * If the field is not defined, Lago will return only `active` subscriptions. However, if you wish to fetch subscriptions by different status you can define them in a status[] query param. Available filter values: `pending`, `canceled`, `terminated`, `active`.
+             * @example ["active","pending"]
+             */
+            "status[]"?: ("pending" | "canceled" | "terminated" | "active")[];
+        }, params?: RequestParams) => Promise<HttpResponse<SubscriptionsPaginated, ApiErrorUnauthorized | ApiErrorNotFound>>;
+        /**
+         * @description This endpoint is used to list all wallets with prepaid credits of a customer
+         *
+         * @tags customers, wallets
+         * @name FindAllCustomerWallets
+         * @summary List all customer's wallets
+         * @request GET:/customers/{external_customer_id}/wallets
+         * @secure
+         */
+        findAllCustomerWallets: (externalCustomerId: string, query?: {
+            /**
+             * Page number.
+             * @example 1
+             */
+            page?: number;
+            /**
+             * Number of records per page.
+             * @example 20
+             */
+            per_page?: number;
+        }, params?: RequestParams) => Promise<HttpResponse<WalletsPaginated, ApiErrorUnauthorized | ApiErrorForbidden | ApiErrorNotFound>>;
         /**
          * @description This endpoint enables the retrieval of the usage-based billing data for a customer within the current period.
          *
@@ -8521,6 +8902,11 @@ export declare class Api<SecurityDataType extends unknown> extends HttpClient<Se
              * @example "event-123"
              */
             code?: string;
+            /**
+             * Requires `external_subscription_id` to be set. Filter events by timestamp after the subscription started at datetime.
+             * @example true
+             */
+            timestamp_from_started_at?: boolean;
             /**
              * Filter events by timestamp starting from a specific date.
              * @format date-time
@@ -9084,7 +9470,7 @@ export declare class Api<SecurityDataType extends unknown> extends HttpClient<Se
          * @request GET:/payments/{lago_id}
          * @secure
          */
-        findPayment: (lagoId: string, params?: RequestParams) => Promise<HttpResponse<PaymentManualObject, ApiErrorUnauthorized | ApiErrorNotFound>>;
+        findPayment: (lagoId: string, params?: RequestParams) => Promise<HttpResponse<PaymentObject, ApiErrorUnauthorized | ApiErrorNotFound>>;
     };
     plans: {
         /**