buildium-ruby 2.0.1 → 3.0.0

data/buildium-ruby.gemspec

@@ -3,7 +3,7 @@
 =begin
 #Open API, powered by Buildium
 
-#GetAllGLAccounts) response message now includes the property `IsBankAccount`. This is a boolean property that indicates whether the general ledger account is also a bank account.  * A `Country` property has been added to all Address messages. This property contains an enumeration indicating the country of the address.   
+#  # Introduction  ### Welcome!    Welcome to Buildium’s API—a powerful, RESTful programming interface that lets you leverage valuable Buildium data.    Using HTTP requests, you can create integrations with applications that specialize in accounting, lead tracking, and more. Enjoy greater flexibility, transparency, and control over your business!      ### What's in this Guide?    This guide is full of simple, easy-to-follow instructions that’ll help you use Buildium’s API like a pro.    Topics include:    * choosing the right resources for your use case  * making HTTP requests to any resource  * understanding data and response codes    <br />    # Getting Started  Excited to get going? We’ll walk you through the setup process.  >  **Note:** To take advantage of the Buildium Open API you must have a <a target=\"_blank\" href=\"https://www.buildium.com/pricing/\">**Premium Subscription**</a>.    ## Account Configuration  Before you can use Buildium’s API, you’ll need to make some tweaks to your account settings.    <br />    ### Enabling the API  In order to start creating your keys and making requests, you’ll need to enable the API.      >  **Tip:** You’ll need an administrator user role with access to ***Application settings*** to set things up properly.    <br />    ​ **Let's Begin!**    1. Sign in to your [Buildium](https://signin.managebuilding.com/manager/public/authentication/login?ReturnUrl=%2Fmanager%2F) account from your browser.    2. Open the ***Settings*** menu and click ***Application settings***.    3. Under ***System preferences***, click ***Api settings***. A modal will appear.    4. Click the ***Open API*** toggle to turn it on. Then click ***Save***.    <video width=\"100%\" autoplay loop muted>    <source src=\"enable_open_api.mp4\" type=\"video/mp4\" />  </video>      Congratulations! Your account's enabled. Now, you’re ready to start managing API keys.  <br />  <br />  If you are having issues enabling the API within your account you can submit a [Support](#section/API-Overview/Support) request for assistance.    <br />      ## API Keys  Account-level API keys authenticate every request and keep things secure.    API keys have two components: a “client ID” and a “secret”.    * **Client IDs** are similar to usernames. They’re used to identify your Buildium account and are safe to share.  * **Secrets** are similar to passwords. They must be kept confidential.    Whenever you make a request, you’ll need the API key’s client ID and secret. If you forget it, make a mistake, or try to use information that’s linked to a deleted key, the API will return a `401` response code.    >  **Tip:** We compiled a list of best practices that detail how securely store API keys. [Give it a read](#section/Getting-Started/Keeping-API-Keys-Safe)!    ## Creating API Keys  Now that the Open APi is enabled, you’ll be able to create API keys. You’re almost there!    >  **Tip:** You’ll need an administrator user role to complete this step, too.    <br />    **How to create an API key**    1. Sign in to your [Buildium](https://signin.managebuilding.com/manager/public/authentication/login?ReturnUrl=%2Fmanager%2F) account from your browser.    2. Open the ***Settings*** menu and click ***Developer Tools***. The page will open automatically.    3. Click the ***Create API Key*** button. A modal will appear.    4. Enter a clear, memorable name and description for your API key. It’ll make it easier to locate the right key when you make a request. Once finished, click **Next**.    5. Now, choose which pieces of Buildium data you want this API key to have access to by marking the corresponding checkboxes. Once finished, click **Next**.    6. You successfully created an API key!    > **Important:** This is your only chance to record the secret. Make sure it’s stored somewhere secure! If it’s forgotten, you’ll need to delete this key and start from scratch.    <br />    <video width=\"100%\" autoplay loop muted>    <source src=\"generate_open_api_key.mp4\" type=\"video/mp4\" />  </video>    <br />    You have now successfully created an API key and have everything you need to  send requests to the Buildium API!    Before moving on to [making your first request](#section/Getting-Started/How-to-Make-a-Request) please review [Keeping your Keys Safe](#section/Getting-Started/Keeping-your-Keys-Safe) for an overview on securely storing your API keys.    <br />  If you are having issues creating API keys you can submit a [Support](#section/API-Overview/Support) request for assistance.  <br />      ## Keeping API Keys Safe    Based on their permissions, API keys could have full access to your account’s Buildium data. It’s important that you only grant access to trusted applications, securely record secrets, and consider a password manager to stay organized.      ### Recommended Practices    - Avoid hard-coding client IDs and secrets inside source files.  - Avoid storing client IDs and secrets in any files that may be committed to source control, particularly cloud-based source control platforms.  - Apply restrictions to client IDs and secrets shared with your staff. You can restrict a key to particular Buildium entities or to read-only access (GET resources only).  - Avoid sharing client IDs and secrets across public, insecure platforms.  - Establish a process to regularly recreate your client IDs and secrets from your Buildium account.    <br />    <br />    ## How to Make a Request    You’ve done a great job setting up your account, Now, we’ll walk you through how to access your data. It’s very straightforward and should only take a few minutes!      > **Tip:** Looking for the right HTTP client? If you’re just getting started, we recommend Postman.      <br />    ### Let's Get Started!    #### Step 1: Get Your API Key    If you haven't yet done so, obtain your API key client ID and secret from your Buildium account. Your API key is how the Buildium API authenticates requests and ensures only you can access your data.    See [Getting Started](#section/Getting-Started) for a deeper dive into enabling the API and creating keys.    #### Step 2: Install a HTTP client  The Buildium API supports any standard HTTP client. If you're looking for a user-friendly HTTP client application, we recommend [Postman](https://www.postman.com/product/api-client) – it allows you to access the Buildium API without writing code. We’ll use Postman for our example below to demonstrate sending an API request.      #### Step 3: Make a Sample Request    Let's dive in and make a simple request to get all the [Rental Properties](#operation/RentalsGetAllGLAccounts) response message now includes the property `IsBankAccount`. This is a boolean property that indicates whether the general ledger account is also a bank account.  * A `Country` property has been added to all Address messages. This property contains an enumeration indicating the country of the address.   
 
 The version of the OpenAPI document: v1
 
@@ -25,13 +25,11 @@ Gem::Specification.new do |s|
   s.summary     = "Open API, powered by Buildium Ruby Gem"
   s.description = "API client library for Buildium"
   s.license     = "Unlicense"
-  s.required_ruby_version = "> 2.6.0"
+  s.required_ruby_version = "> 3.0.0"
 
   s.add_runtime_dependency 'faraday', '>= 1.0.1', '< 3.0'
   s.add_runtime_dependency 'faraday-multipart'
 
-  s.add_development_dependency 'rspec', '~> 3.6', '>= 3.6.0'
-
   s.files         = `git ls-files`.split("\n").uniq.sort.select { |f| !f.empty? }
   s.test_files    = `git ls-files spec/*`.split("\n")
   s.executables   = []

data/docs/AccountingEntityMessage.md

@@ -7,6 +7,7 @@
 | **id** | **Integer** | The accounting entity unique identifier. | [optional] |
 | **accounting_entity_type** | **String** | The type of accounting entity. | [optional] |
 | **href** | **String** | A link to the accounting entity resource. | [optional] |
+| **unit** | [**UnitEntityMessage**](UnitEntityMessage.md) |  | [optional] |
 
 ## Example
 
@@ -16,7 +17,8 @@ require 'buildium-ruby'
 instance = Buildium::AccountingEntityMessage.new(
   id: null,
   accounting_entity_type: null,
-  href: null
+  href: null,
+  unit: null
 )
 ```
 

data/docs/AccountingEntitySaveMessage.md

@@ -6,6 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **id** | **Integer** | The unique identifier of the accounting entity |  |
 | **accounting_entity_type** | **String** | The type of the accounting entity |  |
+| **unit_id** | **Integer** | The unit unique identifier for the accounting entity. | [optional] |
 
 ## Example
 
@@ -14,7 +15,8 @@ require 'buildium-ruby'
 
 instance = Buildium::AccountingEntitySaveMessage.new(
   id: null,
-  accounting_entity_type: null
+  accounting_entity_type: null,
+  unit_id: null
 )
 ```
 

data/docs/{AssociationAppliancesApi.md → AppliancesApi.md}

@@ -1,17 +1,17 @@
-# Buildium::AssociationAppliancesApi
+# Buildium::AppliancesApi
 
 All URIs are relative to *https://api.buildium.com*
 
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
-| [**create_association_appliance**](AssociationAppliancesApi.md#create_association_appliance) | **POST** /v1/associations/appliances | Create an appliance |
-| [**create_association_appliance_service_history**](AssociationAppliancesApi.md#create_association_appliance_service_history) | **POST** /v1/associations/appliances/{applianceId}/servicehistory | Create a service history |
-| [**delete_association_appliances**](AssociationAppliancesApi.md#delete_association_appliances) | **DELETE** /v1/associations/appliances/{applianceId} | Delete an appliance |
-| [**get_all_association_appliance_service_history**](AssociationAppliancesApi.md#get_all_association_appliance_service_history) | **GET** /v1/associations/appliances/{applianceId}/servicehistory | Retrieve all service history |
-| [**get_association_appliance_by_id**](AssociationAppliancesApi.md#get_association_appliance_by_id) | **GET** /v1/associations/appliances/{applianceId} | Retrieve an appliance |
-| [**get_association_appliance_service_history_by_id**](AssociationAppliancesApi.md#get_association_appliance_service_history_by_id) | **GET** /v1/associations/appliances/{applianceId}/servicehistory/{serviceHistoryId} | Retrieve a service history |
-| [**get_association_appliances**](AssociationAppliancesApi.md#get_association_appliances) | **GET** /v1/associations/appliances | Retrieve all appliances |
-| [**update_association_appliance**](AssociationAppliancesApi.md#update_association_appliance) | **PUT** /v1/associations/appliances/{applianceId} | Update an appliance |
+| [**create_association_appliance**](AppliancesApi.md#create_association_appliance) | **POST** /v1/associations/appliances | Create an appliance |
+| [**create_association_appliance_service_history**](AppliancesApi.md#create_association_appliance_service_history) | **POST** /v1/associations/appliances/{applianceId}/servicehistory | Create a service history |
+| [**delete_association_appliances**](AppliancesApi.md#delete_association_appliances) | **DELETE** /v1/associations/appliances/{applianceId} | Delete an appliance |
+| [**get_all_association_appliance_service_history**](AppliancesApi.md#get_all_association_appliance_service_history) | **GET** /v1/associations/appliances/{applianceId}/servicehistory | Retrieve all service history |
+| [**get_association_appliance_by_id**](AppliancesApi.md#get_association_appliance_by_id) | **GET** /v1/associations/appliances/{applianceId} | Retrieve an appliance |
+| [**get_association_appliance_service_history_by_id**](AppliancesApi.md#get_association_appliance_service_history_by_id) | **GET** /v1/associations/appliances/{applianceId}/servicehistory/{serviceHistoryId} | Retrieve a service history |
+| [**get_association_appliances**](AppliancesApi.md#get_association_appliances) | **GET** /v1/associations/appliances | Retrieve all appliances |
+| [**update_association_appliance**](AppliancesApi.md#update_association_appliance) | **PUT** /v1/associations/appliances/{applianceId} | Update an appliance |
 
 
 ## create_association_appliance
@@ -20,7 +20,7 @@ All URIs are relative to *https://api.buildium.com*
 
 Create an appliance
 
-Creates an association appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Association properties and units</span> - `View` `Edit`
+Creates an association appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Associations and units</span> - `View` `Edit`
 
 ### Examples
 
@@ -40,7 +40,7 @@ Buildium.configure do |config|
   # config.api_key_prefix['clientSecret'] = 'Bearer'
 end
 
-api_instance = Buildium::AssociationAppliancesApi.new
+api_instance = Buildium::AppliancesApi.new
 association_appliance_post_message = Buildium::AssociationAppliancePostMessage.new({association_id: 37, name: 'name_example'}) # AssociationAppliancePostMessage | 
 
 begin
@@ -48,7 +48,7 @@ begin
   result = api_instance.create_association_appliance(association_appliance_post_message)
   p result
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->create_association_appliance: #{e}"
+  puts "Error when calling AppliancesApi->create_association_appliance: #{e}"
 end
 ```
 
@@ -66,7 +66,7 @@ begin
   p headers # => { ... }
   p data # => <AssociationApplianceMessage>
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->create_association_appliance_with_http_info: #{e}"
+  puts "Error when calling AppliancesApi->create_association_appliance_with_http_info: #{e}"
 end
 ```
 
@@ -96,7 +96,7 @@ end
 
 Create a service history
 
-Creates a service history for an appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Association properties and units</span> - `View` `Edit`
+Creates a service history for an appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Associations and units</span> - `View` `Edit`
 
 ### Examples
 
@@ -116,7 +116,7 @@ Buildium.configure do |config|
   # config.api_key_prefix['clientSecret'] = 'Bearer'
 end
 
-api_instance = Buildium::AssociationAppliancesApi.new
+api_instance = Buildium::AppliancesApi.new
 appliance_id = 56 # Integer | 
 association_appliance_service_history_post_message = Buildium::AssociationApplianceServiceHistoryPostMessage.new({service_type: 'Installed', date: Date.today}) # AssociationApplianceServiceHistoryPostMessage | 
 
@@ -125,7 +125,7 @@ begin
   result = api_instance.create_association_appliance_service_history(appliance_id, association_appliance_service_history_post_message)
   p result
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->create_association_appliance_service_history: #{e}"
+  puts "Error when calling AppliancesApi->create_association_appliance_service_history: #{e}"
 end
 ```
 
@@ -143,7 +143,7 @@ begin
   p headers # => { ... }
   p data # => <AssociationApplianceServiceHistoryMessage>
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->create_association_appliance_service_history_with_http_info: #{e}"
+  puts "Error when calling AppliancesApi->create_association_appliance_service_history_with_http_info: #{e}"
 end
 ```
 
@@ -174,7 +174,7 @@ end
 
 Delete an appliance
 
-Deletes an associations appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Association properties and units</span> - `View` `Edit`
+Deletes an associations appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Associations and units</span> - `View` `Edit`
 
 ### Examples
 
@@ -194,14 +194,14 @@ Buildium.configure do |config|
   # config.api_key_prefix['clientSecret'] = 'Bearer'
 end
 
-api_instance = Buildium::AssociationAppliancesApi.new
+api_instance = Buildium::AppliancesApi.new
 appliance_id = 56 # Integer | 
 
 begin
   # Delete an appliance
   api_instance.delete_association_appliances(appliance_id)
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->delete_association_appliances: #{e}"
+  puts "Error when calling AppliancesApi->delete_association_appliances: #{e}"
 end
 ```
 
@@ -219,7 +219,7 @@ begin
   p headers # => { ... }
   p data # => nil
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->delete_association_appliances_with_http_info: #{e}"
+  puts "Error when calling AppliancesApi->delete_association_appliances_with_http_info: #{e}"
 end
 ```
 
@@ -249,7 +249,7 @@ nil (empty response body)
 
 Retrieve all service history
 
-Retrieves all of the service history records for an appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Association properties and units</span> - `View`
+Retrieves all of the service history records for an appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Associations and units</span> - `View`
 
 ### Examples
 
@@ -269,7 +269,7 @@ Buildium.configure do |config|
   # config.api_key_prefix['clientSecret'] = 'Bearer'
 end
 
-api_instance = Buildium::AssociationAppliancesApi.new
+api_instance = Buildium::AppliancesApi.new
 appliance_id = 56 # Integer | 
 opts = {
   orderby: 'orderby_example', # String | `orderby` indicates the field(s) and direction to sort the results in the response. See <a href=\"#section/API-Overview/Bulk-Request-Options\">Bulk Request Options</a> for more information.
@@ -282,7 +282,7 @@ begin
   result = api_instance.get_all_association_appliance_service_history(appliance_id, opts)
   p result
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->get_all_association_appliance_service_history: #{e}"
+  puts "Error when calling AppliancesApi->get_all_association_appliance_service_history: #{e}"
 end
 ```
 
@@ -300,7 +300,7 @@ begin
   p headers # => { ... }
   p data # => <Array<AssociationApplianceServiceHistoryMessage>>
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->get_all_association_appliance_service_history_with_http_info: #{e}"
+  puts "Error when calling AppliancesApi->get_all_association_appliance_service_history_with_http_info: #{e}"
 end
 ```
 
@@ -333,7 +333,7 @@ end
 
 Retrieve an appliance
 
-Retrieves an association appliance by id.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Association properties and units</span> - `View`
+Retrieves an association appliance by id.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Associations and units</span> - `View`
 
 ### Examples
 
@@ -353,7 +353,7 @@ Buildium.configure do |config|
   # config.api_key_prefix['clientSecret'] = 'Bearer'
 end
 
-api_instance = Buildium::AssociationAppliancesApi.new
+api_instance = Buildium::AppliancesApi.new
 appliance_id = 56 # Integer | 
 
 begin
@@ -361,7 +361,7 @@ begin
   result = api_instance.get_association_appliance_by_id(appliance_id)
   p result
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->get_association_appliance_by_id: #{e}"
+  puts "Error when calling AppliancesApi->get_association_appliance_by_id: #{e}"
 end
 ```
 
@@ -379,7 +379,7 @@ begin
   p headers # => { ... }
   p data # => <AssociationApplianceMessage>
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->get_association_appliance_by_id_with_http_info: #{e}"
+  puts "Error when calling AppliancesApi->get_association_appliance_by_id_with_http_info: #{e}"
 end
 ```
 
@@ -409,7 +409,7 @@ end
 
 Retrieve a service history
 
-Retrieves a specific service history record for a given appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Association properties and units</span> - `View`
+Retrieves a specific service history record for a given appliance.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Associations and units</span> - `View`
 
 ### Examples
 
@@ -429,7 +429,7 @@ Buildium.configure do |config|
   # config.api_key_prefix['clientSecret'] = 'Bearer'
 end
 
-api_instance = Buildium::AssociationAppliancesApi.new
+api_instance = Buildium::AppliancesApi.new
 appliance_id = 56 # Integer | 
 service_history_id = 56 # Integer | 
 
@@ -438,7 +438,7 @@ begin
   result = api_instance.get_association_appliance_service_history_by_id(appliance_id, service_history_id)
   p result
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->get_association_appliance_service_history_by_id: #{e}"
+  puts "Error when calling AppliancesApi->get_association_appliance_service_history_by_id: #{e}"
 end
 ```
 
@@ -456,7 +456,7 @@ begin
   p headers # => { ... }
   p data # => <AssociationApplianceServiceHistoryMessage>
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->get_association_appliance_service_history_by_id_with_http_info: #{e}"
+  puts "Error when calling AppliancesApi->get_association_appliance_service_history_by_id_with_http_info: #{e}"
 end
 ```
 
@@ -487,7 +487,7 @@ end
 
 Retrieve all appliances
 
-Retrieves all association appliances.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Association properties and units</span> - `View`
+Retrieves all association appliances.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Associations and units</span> - `View`
 
 ### Examples
 
@@ -507,7 +507,7 @@ Buildium.configure do |config|
   # config.api_key_prefix['clientSecret'] = 'Bearer'
 end
 
-api_instance = Buildium::AssociationAppliancesApi.new
+api_instance = Buildium::AppliancesApi.new
 opts = {
   associationids: [37], # Array<Integer> | Filters results to appliances associated to any of the specified association identifiers.
   unitids: [37], # Array<Integer> | Filters results to appliances associated to any of the specified association unit identifiers.
@@ -521,7 +521,7 @@ begin
   result = api_instance.get_association_appliances(opts)
   p result
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->get_association_appliances: #{e}"
+  puts "Error when calling AppliancesApi->get_association_appliances: #{e}"
 end
 ```
 
@@ -539,7 +539,7 @@ begin
   p headers # => { ... }
   p data # => <Array<AssociationApplianceMessage>>
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->get_association_appliances_with_http_info: #{e}"
+  puts "Error when calling AppliancesApi->get_association_appliances_with_http_info: #{e}"
 end
 ```
 
@@ -573,7 +573,7 @@ end
 
 Update an appliance
 
-Updates an association appliance.              <br /><br /><strong>NOTE:</strong> Any field not included in the update request will be set to either an empty string or `null` in the database depending on the field definition. <br />The recommended workflow to ensure no data is inadvertently overwritten is to execute a `GET` request for the resource you're about to update and then use this response to fill any of the fields that are not being updated.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Association properties and units</span> - `View` `Edit`
+Updates an association appliance.              <br /><br /><strong>NOTE:</strong> Any field not included in the update request will be set to either an empty string or `null` in the database depending on the field definition. <br />The recommended workflow to ensure no data is inadvertently overwritten is to execute a `GET` request for the resource you're about to update and then use this response to fill any of the fields that are not being updated.              <br /><br /><h4>Required permission(s):</h4><span class=\"permissionBlock\">Associations &gt; Associations and units</span> - `View` `Edit`
 
 ### Examples
 
@@ -593,7 +593,7 @@ Buildium.configure do |config|
   # config.api_key_prefix['clientSecret'] = 'Bearer'
 end
 
-api_instance = Buildium::AssociationAppliancesApi.new
+api_instance = Buildium::AppliancesApi.new
 appliance_id = 56 # Integer | 
 association_appliance_put_message = Buildium::AssociationAppliancePutMessage.new({name: 'name_example'}) # AssociationAppliancePutMessage | 
 
@@ -602,7 +602,7 @@ begin
   result = api_instance.update_association_appliance(appliance_id, association_appliance_put_message)
   p result
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->update_association_appliance: #{e}"
+  puts "Error when calling AppliancesApi->update_association_appliance: #{e}"
 end
 ```
 
@@ -620,7 +620,7 @@ begin
   p headers # => { ... }
   p data # => <AssociationApplianceMessage>
 rescue Buildium::ApiError => e
-  puts "Error when calling AssociationAppliancesApi->update_association_appliance_with_http_info: #{e}"
+  puts "Error when calling AppliancesApi->update_association_appliance_with_http_info: #{e}"
 end
 ```
 

data/docs/ApplicantMessage.md

@@ -13,6 +13,7 @@
 | **last_name** | **String** | Applicant last name. | [optional] |
 | **email** | **String** | Applicant email address. | [optional] |
 | **phone_numbers** | [**Array<PhoneNumberMessage>**](PhoneNumberMessage.md) | Applicant phone numbers. | [optional] |
+| **status** | **String** | Applicant status. | [optional] |
 | **applications** | [**Array<ApplicantApplicationMessage>**](ApplicantApplicationMessage.md) | A collection of applications associated with the applicant. | [optional] |
 
 ## Example
@@ -30,6 +31,7 @@ instance = Buildium::ApplicantMessage.new(
   last_name: null,
   email: null,
   phone_numbers: null,
+  status: null,
   applications: null
 )
 ```

data/docs/AppliedVendorCreditMessage.md

@@ -0,0 +1,20 @@
+# Buildium::AppliedVendorCreditMessage
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **Integer** | The vendor credit id applied to the bill payment. | [optional] |
+| **href** | **String** | A link to the resource endpoint associated with the vendor credit. | [optional] |
+
+## Example
+
+```ruby
+require 'buildium-ruby'
+
+instance = Buildium::AppliedVendorCreditMessage.new(
+  id: null,
+  href: null
+)
+```
+

data/docs/AssociationMessage.md

@@ -16,6 +16,7 @@
 | **association_manager** | [**PropertyManagerMessage**](PropertyManagerMessage.md) |  | [optional] |
 | **fiscal_year_end_day** | **Integer** | The day the fiscal year ends for the association. | [optional] |
 | **fiscal_year_end_month** | **Integer** | The month the fiscal year ends for the association. | [optional] |
+| **tax_information** | [**AssociationTaxInformationMessage**](AssociationTaxInformationMessage.md) |  | [optional] |
 
 ## Example
 
@@ -34,7 +35,8 @@ instance = Buildium::AssociationMessage.new(
   address: null,
   association_manager: null,
   fiscal_year_end_day: null,
-  fiscal_year_end_month: null
+  fiscal_year_end_month: null,
+  tax_information: null
 )
 ```