{
"openapi": "3.0.0",
"info": {
"version": "v1",
"title": "Open API, powered by Buildium",
"description": "\r\n# Introduction\r\n### Welcome!\r\n\r\nWelcome to Buildium’s API—a powerful, RESTful programming interface that lets you leverage valuable Buildium data.\r\n\r\nUsing 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!\r\n\r\n\r\n### What's in this Guide?\r\n\r\nThis guide is full of simple, easy-to-follow instructions that’ll help you use Buildium’s API like a pro.\r\n\r\nTopics include:\r\n\r\n* choosing the right resources for your use case\r\n* making HTTP requests to any resource\r\n* understanding data and response codes\r\n\r\n
\r\n\r\n# Getting Started\r\nExcited to get going? We’ll walk you through the setup process.\r\n> **Note:** To take advantage of the Buildium Open API you must have a **Premium Subscription**.\r\n\r\n## Account Configuration\r\nBefore you can use Buildium’s API, you’ll need to make some tweaks to your account settings.\r\n\r\n
\r\n\r\n### Enabling the API\r\nIn order to start creating your keys and making requests, you’ll need to enable the API.\r\n\r\n\r\n> **Tip:** You’ll need an administrator user role with access to ***Application settings*** to set things up properly.\r\n\r\n
\r\n\r\n\t**Let's Begin!**\r\n\r\n1. Sign in to your [Buildium](https://signin.managebuilding.com/manager/public/authentication/login?ReturnUrl=%2Fmanager%2F) account from your browser.\r\n\r\n2. Open the ***Settings*** menu and click ***Application settings***.\r\n\r\n3. Under ***System preferences***, click ***Api settings***. A modal will appear.\r\n\r\n4. Click the ***Open API*** toggle to turn it on. Then click ***Save***.\r\n\r\n\r\n\r\n\r\nCongratulations! Your account's enabled. Now, you’re ready to start managing API keys.\r\n
\r\n
\r\nIf you are having issues enabling the API within your account you can submit a [Support](#section/API-Overview/Support) request for assistance.\r\n\r\n
\r\n\r\n\r\n## API Keys\r\nAccount-level API keys authenticate every request and keep things secure.\r\n\r\nAPI keys have two components: a “client ID” and a “secret”.\r\n\r\n* **Client IDs** are similar to usernames. They’re used to identify your Buildium account and are safe to share.\r\n* **Secrets** are similar to passwords. They must be kept confidential.\r\n\r\nWhenever 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.\r\n\r\n> **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)!\r\n\r\n## Creating API Keys\r\nNow that the Open APi is enabled, you’ll be able to create API keys. You’re almost there!\r\n\r\n> **Tip:** You’ll need an administrator user role to complete this step, too.\r\n\r\n
\r\n\r\n**How to create an API key**\r\n\r\n1. Sign in to your [Buildium](https://signin.managebuilding.com/manager/public/authentication/login?ReturnUrl=%2Fmanager%2F) account from your browser.\r\n\r\n2. Open the ***Settings*** menu and click ***Developer Tools***. The page will open automatically.\r\n\r\n3. Click the ***Create API Key*** button. A modal will appear.\r\n\r\n4. 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**.\r\n\r\n5. 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**.\r\n\r\n6. You successfully created an API key!\r\n\r\n> **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.\r\n\r\n
\r\n\r\n\r\n\r\n
\r\n\r\nYou have now successfully created an API key and have everything you need to send requests to the Buildium API!\r\n\r\nBefore 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. \r\n
\r\nIf you are having issues creating API keys you can submit a [Support](#section/API-Overview/Support) request for assistance.\r\n
\r\n\r\n\r\n## Keeping API Keys Safe\r\n\r\nBased 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.\r\n\r\n\r\n### Recommended Practices\r\n\r\n- Avoid hard-coding client IDs and secrets inside source files.\r\n- Avoid storing client IDs and secrets in any files that may be committed to source control, particularly cloud-based source control platforms.\r\n- 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).\r\n- Avoid sharing client IDs and secrets across public, insecure platforms.\r\n- Establish a process to regularly recreate your client IDs and secrets from your Buildium account.\r\n
\r\n
\r\n\r\n## How to Make a Request\r\n\r\nYou’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!\r\n\r\n\r\n> **Tip:** Looking for the right HTTP client? If you’re just getting started, we recommend Postman.\r\n\r\n\r\n
\r\n\r\n### Let's Get Started!\r\n\r\n#### Step 1: Get Your API Key\r\n\r\nIf 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.\r\n\r\nSee [Getting Started](#section/Getting-Started) for a deeper dive into enabling the API and creating keys.\r\n\r\n#### Step 2: Install a HTTP client\r\nThe 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.\r\n\r\n\r\n#### Step 3: Make a Sample Request\r\n\r\nLet's dive in and make a simple request to get all the [Rental Properties](#operation/RentalsExternalApi_GetAllRentals) in your account. This will confirm your connectivity to our platform and validate the keys you created on our website. Simply follow the instructions below.\r\n\r\n\r\n1. Open the Postman application.\r\n2. Open the *verb* menu and select **GET**.\r\n3. Enter the request endpoint in the field next to GET.\r\n - Here’s the endpoint to get all rentals: https://api.buildium.com/v1/rentals.\r\n4. To authenticate the request, enter your `client ID` and `secret` respectively in these request headers:\r\n - `x-buildium-client-id`\r\n - `x-buildium-client-secret`\r\n - Your full request should look similar to the image below.\r\n\r\n
\r\n\r\n5. Review the parameters of your request on last time. Once finished, click **Send**.\r\n\r\n6. If successful, you should see a JSON response and a `200` HTTP status code. Voilà! You've connected to the Buildium API.\r\n\r\n
\r\nYou now have the knowledge required to make requests for any of our resources.\r\n\r\nIf you've received an error response please review the JSON response message for a description of how to resolve the issue. You can also see more information about HTTP status codes in the [Response Codes](#section/API-Overview/Response-Codes) section. If you are still having trouble making a request after reviewing these sections please submit a [Support](#section/API-Overview/Support) request.\r\n\r\n
\r\n\r\n# API Overview\r\nThe Buildium API is built upon standard REST conventions. It's designed to use consistent resource-oriented URLs, accept and return JSON-encoded messages, and use standard HTTP status codes and verbs.\r\n\r\n## Base URL\r\nThe base URL for production environment API requests is: `https://api.buildium.com/`\r\n\r\nThe base URL for sandbox environment API requests is: `https://apisandbox.buildium.com/`\r\n\r\nIn order to ensure all requests and responses are secure between the API consumer and Buildium servers, requests must be made using the `https` protocol. Any requests not made with the `https` protocol will be refused by the Buildium API platform.\r\n\r\n> **Note:** URL paths are case-sensitive to stay consistent with common REST standards. If your request doesn’t align with the documented URL path, you’ll receive a `404` response code reminding you of this constraint.\r\n\r\n## API Versioning\r\nThe Buildium API is version controlled. Versioning ensures backwards-incompatible changes to the API don’t impact any existing integrations.\r\n\r\nBuildium uses only a major version nomenclature to manage changes. The current version of the Buildium API is version 1. By specifying a version in the resource request URL, you'll get expected responses regardless of future changes to the API. Here's an example of calling version 1 of the retrieve all rentals resource:\r\n\r\n`https://api.buildium.com/v1/rentals`\r\n\r\nAny request submitted without the version in the URL path will result in a `404` error response code.\r\n\r\n### Releasing Changes to the API\r\nThe Buildium API will continue to evolve to ensure it meets the needs of our customers. Changes will be defined as either backwards-compatible or backwards-incompatible.\r\n\r\nWe’ll always provide advance notice for all API releases–regardless of the type of modifications being made.\r\n\r\n#### Backward-compatible Changes\r\nBackward-compatible changes are modifications to the API that shouldn't impact existing integrations. They'll apply to the current version of the API. Simply put: you won’t need to change the version to consume new changes like these.\r\n\r\nIt's important as you develop against the Buildium API that you ensure these types of changes don't impact your integration. Here's are examples of backward-compatible modifications.\r\n\r\n* Adding new API resources and/or endpoints.\r\n* Adding new optional request parameters to existing API methods.\r\n* Adding new properties to existing API responses and non-required properties for request messages.\r\n* Changing property order in existing API responses.\r\n\r\nAll backward-compatible changes to the API will be documented in the [Changelog](#section/Changelog).\r\n\r\n#### Backwards-incompatible Changes\r\n\r\nWhen backwards-incompatible changes to the API occur, a new version of the API will be released. You’ll need to update the URL path to consume resources under the new API version.\r\n\r\nBackwards-incompatible changes include:\r\n\r\n* Removing a property from a request and/or response message.\r\n* Changing the name of a property in a message.\r\n* Adding a required parameter to a request message.\r\n* Changing existing enumeration values.\r\n\r\nNew versions of the API will have full reference documentation and an upgrade guide.\r\n\r\n
\r\n\r\n\r\n\r\n## Authentication\r\nThe Buildium API uses API key’s client IDs and secrets to authenticate requests.\r\n\r\nAn API key client ID and secret must be passed in every request header using the following parameters:\r\n\r\n- `x-buildium-client-id`\r\n- `x-buildium-client-secret`\r\n\r\nFailing to provide both of them in the request header will cause the API to return a `401` HTTP status code.\r\n\r\n> **Note:** We currently do not support enabling CORS to access the Buildium API due to the security and authentication mechanisms we have in place to protect your data. Buildium supports authentication through API keys passed in the headers of a request versus a more CORS supported authentication mechanism like oAuth. Our recommendation is to access the Buildium API using server to server communication versus browser to server communication for the safest implementation.\r\n\r\n## Rate Limiting\r\nRate limits help us ensure consistent and reliable performance for all users, even during peak loads. That’s why we limit clients to **10 concurrent requests per second**.\r\n\r\nIf your request rate violates that limit, a response code of `429` is returned. Simply retry the request after a short interval (~200ms).\r\n\r\n## Request Size Limits\r\nThe query string for a request is limited to a maximum length of `4096` characters. If the query string exceeds this length, the API will return a `500` HTTP status code.\r\n\r\n## Bulk Request Options\r\nAll top-level API resources support bulk fetches. For instance, you can retrieve all [Associations](#operation/AssociationsExternalApi_GetAssociations). These resources also allow for filtering criteria. Each resource has descriptions of the filter criteria available.\r\n\r\nIn addition to filtering, our API gives you the ability to control the returned data’s pagination and the sort order.\r\n\r\n### Pagination\r\nEndpoints that return result sets allow for pagination using `limit` and `offset` request parameters to reduce the amount of data returned.\r\n\r\nThe `limit` request parameter will cap the number of results that come back in the response. If you don't specify a `limit` value, a **default of 50 results** are returned. The maximum `limit` value is 1000. If a `limit` value is specified greater than 1000, it will be overridden to the default to 1000.\r\n\r\nThe `offset` request parameter indicates the record position within the resultset to start at when returning the results. The `offset` is zero-based and is inclusive. If no `offset` value is submitted it will default to 0.\r\n\r\nThe total resultset count is returned in the HTTP Header `X-Total-Count`\r\n\r\n
\r\n\r\n#### Pagination Example\r\n\r\nAs an example, let's say we make a request to retrieve all rental properties with no paging parameters. Our response indicates in the `X-Total-Count` header that there are 150 total rental properties. We want to get only the last 50 results so we would submit a request with the `offset` set to 100 and the `limit` set to 50.\r\n\r\n> **Note:** The `limit` and `offset` parameter names are case-sensitive. If they aren't formatted correctly, the API will return a `404` HTTP status code.\r\n\r\n\r\n
\r\n\r\n### Sorting Results\r\nYou can specify the sort order of returned data by assigning any property from the returned object to the `orderby` parameter in the querystring. For example:\r\n```\r\norderby=LeaseType\r\n```\r\nBy default, the sort is performed in ascending order. To specify sort order, use \"asc\" for ascending or \"desc\" for descending. For example:\r\n```\r\norderby=LeaseType desc\r\n```\r\nAdditionally, you can sort by multiple properties by comma separating the properties. For example:\r\n```\r\norderby=Rent desc,City asc\r\n```\r\n
\r\n\r\n> **Note:** While the `orderby` parameter is case-sensitive, the properties specified in the `orderby` value aren't.\r\n\r\n## Response Codes\r\nThe Buildium API supports standard HTTP status codes.\r\n\r\n|Response Code |Description |\r\n|--|--|\r\n|200 OK | Everything worked as expected. |\r\n|400 Bad Request | The request was unacceptable, often due to missing a required parameter.|\r\n|401 Unauthorized|The API client ID and secret weren’t provided or they’re no longer valid. Be sure that the client ID and secret combination are correct and they are still active.|\r\n|403 Forbidden|The API key doesn't have permission to perform the request. This could be due to authorization for the given endpoint or an inability to access given entities within the platform (e.g. properties).\r\n|404 Not Found|The requested resource doesn't exist.|\r\n|415 Unsupported Media Type |Ensure you have the appropriate content-type header value set on your request. Each resource is documented with media type(s) that are accepted.|\r\n|429 Too Many Requests |Too many requests against the API too quickly. We recommend an exponential backoff of your requests. See more information in [Rate Limiting](#section/API-Overview/Rate-Limiting).|\r\n|500 and above - Server Errors|Something went wrong on Buildium's end. Review the JSON response message for more details about the error. These are rare.|\r\n\r\n## Support\r\nIf you are unable to resolve your issue after reviewing the API documentation our support team can assist you. Please fill out the form below and let us know how we can help.\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
\r\n Applicants\r\n | \r\n\r\n Applicant.Created\r\n \r\n Applicant.Updated\r\n \r\n Applicant.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n ApplicantId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Applicant Applications\r\n | \r\n\r\n ApplicantApplication.Created\r\n \r\n ApplicantApplication.Updated\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n ApplicantId: [integer]\r\n ApplicationId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Association Board Members\r\n | \r\n\r\n AssociationBoardMember.Created \r\n \r\n AssociationBoardMember.Updated\r\n \r\n AssociationBoardMember.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n BoardMemberId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Associations\r\n | \r\n\r\n Association.Created \r\n \r\n Association.Updated\r\n \r\n Association.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n PropertyId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Association Meter Readings\r\n | \r\n\r\n Association.MeterReading.Created \r\n \r\n Association.MeterReading.Updated\r\n \r\n Association.MeterReading.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n PropertyId: [integer],\r\n ReadingDate: [date],\r\n MeterType: [string] \r\n \r\n }\r\n \r\n | \r\n
\r\n Association Owners\r\n | \r\n\r\n AssociationOwner.Created \r\n \r\n AssociationOwner.Updated\r\n \r\n AssociationOwner.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n OwnerId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Association Ownership Account Transactions\r\n | \r\n\r\n OwnershipAccountTransaction.Created \r\n \r\n OwnershipAccountTransaction.Updated\r\n \r\n OwnershipAccountTransaction.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n TransactionId: [integer],\r\n TransactionType: [string]\r\n \r\n }\r\n \r\n | \r\n
\r\n Association Ownership Accounts\r\n | \r\n\r\n OwnershipAccount.Created \r\n \r\n OwnershipAccount.Updated\r\n \r\n OwnershipAccount.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n OwnershipAccountId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Association Tenants\r\n | \r\n\r\n AssociationTenant.Created \r\n \r\n AssociationTenant.Updated\r\n \r\n AssociationTenant.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n TenantId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Association Units\r\n | \r\n\r\n AssociationUnit.Created \r\n \r\n AssociationUnit.Updated\r\n \r\n AssociationUnit.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n UnitId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Bank Accounts\r\n | \r\n\r\n BankAccount.Created \r\n \r\n BankAccount.Updated\r\n \r\n BankAccount.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n BankAccountId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Bank Account Transactions\r\n | \r\n\r\n BankAccount.Transaction.Created \r\n \r\n BankAccount.Transaction.Updated\r\n \r\n BankAccount.Transaction.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n BankAccountId: [integer],\r\n TransactionId: [integer],\r\n TransactionType: [string]\r\n \r\n }\r\n \r\n | \r\n
\r\n Bills\r\n | \r\n\r\n Bill.Created \r\n \r\n Bill.Updated\r\n \r\n Bill.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n BillId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Bill Payments\r\n | \r\n\r\n Bill.Payment.Created \r\n \r\n Bill.Payment.Updated\r\n \r\n Bill.Payment.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n PaymentId: [integer]\r\n BillIds: [\r\n [integer]\r\n ]\r\n \r\n }\r\n \r\n | \r\n
\r\n Budgets\r\n | \r\n\r\n Budget.Created \r\n \r\n Budget.Updated\r\n \r\n Budget.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n BudgetId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n General Ledger Accounts\r\n | \r\n\r\n GLAccount.Created \r\n \r\n GLAccount.Updated\r\n \r\n GLAccount.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n GLAccountId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Integrations\r\n | \r\n\r\n Installation.Created \r\n \r\n Installation.Updated\r\n \r\n Installation.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n IntegrationName: [string]\r\n \r\n }\r\n \r\n | \r\n
\r\n Lease Move Outs\r\n | \r\n\r\n Lease.MoveOut.Created\r\n | \r\n\r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n LeaseId: [integer],\r\n TenantId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Lease Tenants\r\n | \r\n\r\n LeaseTenant.Created \r\n \r\n LeaseTenant.Updated\r\n \r\n LeaseTenant.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n TenantId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Lease Transactions\r\n | \r\n\r\n LeaseTransaction.Created \r\n \r\n LeaseTransaction.Updated\r\n \r\n LeaseTransaction.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n TransactionId: [integer],\r\n TransactionType: [string]\r\n \r\n }\r\n \r\n | \r\n
\r\n Leases\r\n | \r\n\r\n Lease.Created \r\n \r\n Lease.Updated\r\n \r\n Lease.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n LeaseId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Listings\r\n | \r\n\r\n Listing.Created \r\n \r\n Listing.Updated\r\n \r\n Listing.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n UnitId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Phone Logs\r\n | \r\n\r\n PhoneLog.Created \r\n \r\n PhoneLog.Updated\r\n \r\n PhoneLog.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n PhoneLogId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Rental Meter Readings\r\n | \r\n\r\n Rental.MeterReading.Created \r\n \r\n Rental.MeterReading.Updated\r\n \r\n Rental.MeterReading.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n PropertyId: [integer],\r\n ReadingDate: [date],\r\n MeterType: [string] \r\n \r\n }\r\n \r\n | \r\n
\r\n Rental Properties\r\n | \r\n\r\n Rental.Created\r\n \r\n Rental.Updated\r\n \r\n Rental.Deleted\r\n | \r\n \r\n { EventName: [string], EventDateTime: [datetime], AccountId: [integer], PropertyId: [integer] }\r\n | \r\n
\r\n Rental Units\r\n | \r\n\r\n RentalUnit.Created \r\n \r\n RentalUnit.Updated\r\n \r\n RentalUnit.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n UnitId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Task Categories\r\n | \r\n\r\n TaskCategory.Created \r\n \r\n TaskCategory.Updated\r\n \r\n TaskCategory.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n TaskCategoryId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Tasks\r\n | \r\n\r\n Task.Created \r\n \r\n Task.Updated\r\n \r\n Task.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n TaskId: [integer],\r\n TaskType: [string],\r\n \r\n }\r\n \r\n | \r\n
\r\n Vendor Categories\r\n | \r\n\r\n VendorCategory.Created \r\n \r\n VendorCategory.Updated\r\n \r\n VendorCategory.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n VendorCategoryId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Vendors\r\n | \r\n\r\n Vendor.Created \r\n \r\n Vendor.Updated\r\n \r\n Vendor.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n VendorId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Vendor Transactions\r\n | \r\n\r\n Vendor.Transaction.Created \r\n \r\n Vendor.Transaction.Updated\r\n \r\n Vendor.Transaction.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n TransactionId: [integer]\r\n TransactionType: [string]\r\n VendorId: [integer]\r\n \r\n }\r\n \r\n | \r\n
\r\n Work Orders\r\n | \r\n\r\n WorkOrder.Created\r\n \r\n WorkOrder.Updated\r\n \r\n WorkOrder.Deleted\r\n | \r\n \r\n \r\n {\r\n EventName: [string],\r\n EventDateTime: [datetime], \r\n AccountId: [integer],\r\n WorkOrderId: [integer]\r\n \r\n }\r\n \r\n | \r\n