lago_ruby 0.46.0.pre.beta → 0.46.1.pre.beta

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2ec351e6c57887d41aef82f9e73a3fea92ad4f0c836b8b325b87148d9822209e
-  data.tar.gz: 55aa60e4d42507c45c78f96b2b9d11216dff5511dba716984560ad1bc5289b9a
+  metadata.gz: 3c651739a6a86ad79395baafc83008ecde44521484923eb79e69e88ceec65c72
+  data.tar.gz: d2e50e3a2e4e5eb9370e7eed9f60f8c7e2ba7a566bc5d467482558ac21514055
 SHA512:
-  metadata.gz: 74277aa7f89998f19f9a324be4d8a7f8ab6f12188ddca9d0b7468b0f2581b397d3e17c1c11ba991e7143ecf0977fd4961f1cd1c49d846f4ad3cf9a7e68f3aec4
-  data.tar.gz: e1f0adcd8189322dd7236b2c122fd57507cf103dc7b79ff664718317b7fb4cdfeaefe6d91aedb03e7ae217fc61c39c2efb91cbafb11e38d4b2ae7056985a95ae
+  metadata.gz: 8b883b38524192caba38358bbf4a97961305ee8f4d6065f3fab61a5f080bc3a1a84423a73d5cb402f929f51bdcda423a59107e2e317dee3085d81b242d50662f
+  data.tar.gz: b80b9c7e2e39a42b6d6206f168a233850815582b21b4c438addf37d79bf91574e2484df20432d53a09349fa2a63ca78ad89d1e714fa6c43a764256b4cfa7ba3c

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    lago_ruby (0.45.0.pre.beta)
+    lago_ruby (0.46.1.pre.beta)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM

data/README.md

@@ -6,8 +6,8 @@ Lago API allows your application to push customer information and metrics (event
 
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: 0.46.0-beta
-- Package version: 0.46.0-beta
+- API version: 0.46.1-beta
+- Package version: 0.46.1-beta
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
 [![Gem Version](https://badge.fury.io/rb/lago-ruby.svg)](https://badge.fury.io/rb/lago-ruby)
@@ -26,16 +26,16 @@ gem build lago_ruby.gemspec
 Then either install the gem locally:
 
 ```shell
-gem install ./lago_ruby-0.46.0-beta.gem
+gem install ./lago_ruby-0.46.1-beta.gem
 ```
 
-(for development, run `gem install --dev ./lago_ruby-0.46.0-beta.gem` to install the development dependencies)
+(for development, run `gem install --dev ./lago_ruby-0.46.1-beta.gem` to install the development dependencies)
 
 or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
 
 Finally add this to the Gemfile:
 
-    gem 'lago_ruby', '~> 0.46.0-beta'
+    gem 'lago_ruby', '~> 0.46.1-beta'
 
 ### Install from Git
 
@@ -68,14 +68,14 @@ LagoAPI.configure do |config|
 end
 
 api_instance = LagoAPI::AddOnsApi.new
-applied_add_on_input = LagoAPI::AppliedAddOnInput.new({applied_add_on: LagoAPI::AppliedAddOnInputAppliedAddOn.new({external_customer_id: '5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba', add_on_code: 'setup_fee'})}) # AppliedAddOnInput | Apply add-on payload
+add_on_create_input = LagoAPI::AddOnCreateInput.new({add_on: LagoAPI::AddOnCreateInputAddOn.new({name: 'Setup Fee', code: 'setup_fee', amount_cents: 50000, amount_currency: LagoAPI::Currency::AED})}) # AddOnCreateInput | Add-on payload
 
 begin
-  #Apply an add-on to a customer
-  result = api_instance.apply_add_on(applied_add_on_input)
+  #Create an add-on
+  result = api_instance.create_add_on(add_on_create_input)
   p result
 rescue LagoAPI::ApiError => e
-  puts "Exception when calling AddOnsApi->apply_add_on: #{e}"
+  puts "Exception when calling AddOnsApi->create_add_on: #{e}"
 end
 
 ```
@@ -88,7 +88,6 @@ All URIs are relative to *https://api.getlago.com/api/v1*
 
 Class | Method | HTTP request | Description
 ------------ | ------------- | ------------- | -------------
-*LagoAPI::AddOnsApi* | [**apply_add_on**](docs/AddOnsApi.md#apply_add_on) | **POST** /applied_add_ons | Apply an add-on to a customer
 *LagoAPI::AddOnsApi* | [**create_add_on**](docs/AddOnsApi.md#create_add_on) | **POST** /add_ons | Create an add-on
 *LagoAPI::AddOnsApi* | [**destroy_add_on**](docs/AddOnsApi.md#destroy_add_on) | **DELETE** /add_ons/{code} | Delete an add-on
 *LagoAPI::AddOnsApi* | [**find_add_on**](docs/AddOnsApi.md#find_add_on) | **GET** /add_ons/{code} | Retrieve an add-on
@@ -181,10 +180,6 @@ Class | Method | HTTP request | Description
  - [LagoAPI::ApiErrorNotFound](docs/ApiErrorNotFound.md)
  - [LagoAPI::ApiErrorUnauthorized](docs/ApiErrorUnauthorized.md)
  - [LagoAPI::ApiErrorUnprocessableEntity](docs/ApiErrorUnprocessableEntity.md)
- - [LagoAPI::AppliedAddOn](docs/AppliedAddOn.md)
- - [LagoAPI::AppliedAddOnInput](docs/AppliedAddOnInput.md)
- - [LagoAPI::AppliedAddOnInputAppliedAddOn](docs/AppliedAddOnInputAppliedAddOn.md)
- - [LagoAPI::AppliedAddOnObject](docs/AppliedAddOnObject.md)
  - [LagoAPI::AppliedCoupon](docs/AppliedCoupon.md)
  - [LagoAPI::AppliedCouponInput](docs/AppliedCouponInput.md)
  - [LagoAPI::AppliedCouponInputAppliedCoupon](docs/AppliedCouponInputAppliedCoupon.md)
@@ -260,6 +255,7 @@ Class | Method | HTTP request | Description
  - [LagoAPI::EventInput](docs/EventInput.md)
  - [LagoAPI::EventInputEvent](docs/EventInputEvent.md)
  - [LagoAPI::EventObject](docs/EventObject.md)
+ - [LagoAPI::EventObjectProperties](docs/EventObjectProperties.md)
  - [LagoAPI::Fee](docs/Fee.md)
  - [LagoAPI::FeeAppliedTaxObject](docs/FeeAppliedTaxObject.md)
  - [LagoAPI::FeeObject](docs/FeeObject.md)

data/docs/AddOnsApi.md

@@ -4,7 +4,6 @@ All URIs are relative to *https://api.getlago.com/api/v1*
 
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
-| [**apply_add_on**](AddOnsApi.md#apply_add_on) | **POST** /applied_add_ons | Apply an add-on to a customer |
 | [**create_add_on**](AddOnsApi.md#create_add_on) | **POST** /add_ons | Create an add-on |
 | [**destroy_add_on**](AddOnsApi.md#destroy_add_on) | **DELETE** /add_ons/{code} | Delete an add-on |
 | [**find_add_on**](AddOnsApi.md#find_add_on) | **GET** /add_ons/{code} | Retrieve an add-on |
@@ -12,75 +11,6 @@ All URIs are relative to *https://api.getlago.com/api/v1*
 | [**update_add_on**](AddOnsApi.md#update_add_on) | **PUT** /add_ons/{code} | Update an add-on |
 
 
-## apply_add_on
-
-> <AppliedAddOn> apply_add_on(applied_add_on_input)
-
-Apply an add-on to a customer
-
-Apply an add-on to a customer
-
-### Examples
-
-```ruby
-require 'time'
-require 'lago_ruby'
-# setup authorization
-LagoAPI.configure do |config|
-  # Configure Bearer authorization: bearerAuth
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = LagoAPI::AddOnsApi.new
-applied_add_on_input = LagoAPI::AppliedAddOnInput.new({applied_add_on: LagoAPI::AppliedAddOnInputAppliedAddOn.new({external_customer_id: '5eb02857-a71e-4ea2-bcf9-57d3a41bc6ba', add_on_code: 'setup_fee'})}) # AppliedAddOnInput | Apply add-on payload
-
-begin
-  # Apply an add-on to a customer
-  result = api_instance.apply_add_on(applied_add_on_input)
-  p result
-rescue LagoAPI::ApiError => e
-  puts "Error when calling AddOnsApi->apply_add_on: #{e}"
-end
-```
-
-#### Using the apply_add_on_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(<AppliedAddOn>, Integer, Hash)> apply_add_on_with_http_info(applied_add_on_input)
-
-```ruby
-begin
-  # Apply an add-on to a customer
-  data, status_code, headers = api_instance.apply_add_on_with_http_info(applied_add_on_input)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <AppliedAddOn>
-rescue LagoAPI::ApiError => e
-  puts "Error when calling AddOnsApi->apply_add_on_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **applied_add_on_input** | [**AppliedAddOnInput**](AppliedAddOnInput.md) | Apply add-on payload |  |
-
-### Return type
-
-[**AppliedAddOn**](AppliedAddOn.md)
-
-### Authorization
-
-[bearerAuth](../README.md#bearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: application/json
-
-
 ## create_add_on
 
 > <AddOn> create_add_on(add_on_create_input)

data/docs/EventInputEvent.md

@@ -9,7 +9,7 @@
 | **external_subscription_id** | **String** | 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. | [optional] |
 | **code** | **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. |  |
 | **timestamp** | **Integer** | 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. | [optional] |
-| **properties** | [**EventBatchInputEventProperties**](EventBatchInputEventProperties.md) |  | [optional] |
+| **properties** | **Hash<String, 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. | [optional] |
 
 ## Example
 
@@ -22,7 +22,7 @@ instance = LagoAPI::EventInputEvent.new(
   external_subscription_id: sub_1234567890,
   code: storage,
   timestamp: 1651240791,
-  properties: null
+  properties: {"gb":10}
 )
 ```
 

data/docs/EventInputEventProperties.md

@@ -0,0 +1,18 @@
+# LagoAPI::EventInputEventProperties
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **operation_type** | **String** | 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. | [optional] |
+
+## Example
+
+```ruby
+require 'lago_ruby'
+
+instance = LagoAPI::EventInputEventProperties.new(
+  operation_type: null
+)
+```
+

data/docs/EventObject.md

@@ -10,7 +10,7 @@
 | **external_customer_id** | **String** | The customer external unique identifier (provided by your own application). This field is optional if you send the `external_subscription_id`, targeting a specific subscription. |  |
 | **code** | **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. |  |
 | **timestamp** | **Time** | 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. |  |
-| **properties** | [**EventBatchInputEventProperties**](EventBatchInputEventProperties.md) |  | [optional] |
+| **properties** | [**EventObjectProperties**](EventObjectProperties.md) |  | [optional] |
 | **lago_subscription_id** | **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 |  |
 | **external_subscription_id** | **String** | 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. |  |
 | **created_at** | **Time** | 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 |  |

data/docs/EventObjectProperties.md

@@ -0,0 +1,18 @@
+# LagoAPI::EventObjectProperties
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **operation_type** | **String** | 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. | [optional] |
+
+## Example
+
+```ruby
+require 'lago_ruby'
+
+instance = LagoAPI::EventObjectProperties.new(
+  operation_type: null
+)
+```
+

data/lago_ruby.gemspec

@@ -5,7 +5,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/add_ons_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT
@@ -19,74 +19,6 @@ module LagoAPI
     def initialize(api_client = ApiClient.default)
       @api_client = api_client
     end
-    # Apply an add-on to a customer
-    # Apply an add-on to a customer
-    # @param applied_add_on_input [AppliedAddOnInput] Apply add-on payload
-    # @param [Hash] opts the optional parameters
-    # @return [AppliedAddOn]
-    def apply_add_on(applied_add_on_input, opts = {})
-      data, _status_code, _headers = apply_add_on_with_http_info(applied_add_on_input, opts)
-      data
-    end
-
-    # Apply an add-on to a customer
-    # Apply an add-on to a customer
-    # @param applied_add_on_input [AppliedAddOnInput] Apply add-on payload
-    # @param [Hash] opts the optional parameters
-    # @return [Array<(AppliedAddOn, Integer, Hash)>] AppliedAddOn data, response status code and response headers
-    def apply_add_on_with_http_info(applied_add_on_input, opts = {})
-      if @api_client.config.debugging
-        @api_client.config.logger.debug 'Calling API: AddOnsApi.apply_add_on ...'
-      end
-      # verify the required parameter 'applied_add_on_input' is set
-      if @api_client.config.client_side_validation && applied_add_on_input.nil?
-        fail ArgumentError, "Missing the required parameter 'applied_add_on_input' when calling AddOnsApi.apply_add_on"
-      end
-      # resource path
-      local_var_path = '/applied_add_ons'
-
-      # query parameters
-      query_params = opts[:query_params] || {}
-
-      # header parameters
-      header_params = opts[:header_params] || {}
-      # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
-      # HTTP header 'Content-Type'
-      content_type = @api_client.select_header_content_type(['application/json'])
-      if !content_type.nil?
-          header_params['Content-Type'] = content_type
-      end
-
-      # form parameters
-      form_params = opts[:form_params] || {}
-
-      # http body (model)
-      post_body = opts[:debug_body] || @api_client.object_to_http_body(applied_add_on_input)
-
-      # return_type
-      return_type = opts[:debug_return_type] || 'AppliedAddOn'
-
-      # auth_names
-      auth_names = opts[:debug_auth_names] || ['bearerAuth']
-
-      new_options = opts.merge(
-        :operation => :"AddOnsApi.apply_add_on",
-        :header_params => header_params,
-        :query_params => query_params,
-        :form_params => form_params,
-        :body => post_body,
-        :auth_names => auth_names,
-        :return_type => return_type
-      )
-
-      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
-      if @api_client.config.debugging
-        @api_client.config.logger.debug "API called: AddOnsApi#apply_add_on\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
-      end
-      return data, status_code, headers
-    end
-
     # Create an add-on
     # This endpoint is used to create an add-on that can be then attached to a one-off invoice.
     # @param add_on_create_input [AddOnCreateInput] Add-on payload

data/lib/lago_ruby/api/billable_metrics_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/coupons_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/credit_notes_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/customers_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/events_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/fees_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/invoices_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/organizations_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/plans_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/subscriptions_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/taxes_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/wallets_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/webhook_endpoints_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api/webhooks_api.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api_client.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/api_error.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/configuration.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/add_on.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/add_on_base_input.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/add_on_create_input.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/add_on_create_input_add_on.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/add_on_object.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/add_on_update_input.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/add_ons_paginated.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/api_error_bad_request.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/api_error_forbidden.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/api_error_not_allowed.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/api_error_not_found.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT

data/lib/lago_ruby/models/api_error_unauthorized.rb

@@ -3,7 +3,7 @@
 
 #Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
 
-The version of the OpenAPI document: 0.46.0-beta
+The version of the OpenAPI document: 0.46.1-beta
 Contact: tech@getlago.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 7.0.1-SNAPSHOT