Linking Buildium as a source
This source is currently in beta. It works end to end, but you may still hit rough edges. Let us know if you do.
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
The Buildium (RealPage) connector syncs your property management data – rental properties, units, leases, tenants, owners, vendors, bills, general ledger accounts, work orders, and applicants – into PostHog, so you can analyze your property operations alongside your product data.
Prerequisites
- A Buildium Premium subscription (required for API access).
- Open API enabled in your Buildium account.
- An API key created under Settings > Developer Tools in Buildium.
- View access granted for the data you want to sync.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Buildium, you'll need:
- Client ID – the client ID from your Buildium API key.
- Client secret – the client secret from your Buildium API key.
You can create API keys in Buildium under Settings > Developer Tools. See the Buildium API documentation for more details.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Only the leases and applicants tables support incremental syncing (using the LastUpdatedDateTime field). All other tables use full refresh because the Buildium API does not return update timestamps for those resources.
Configuration
| Option | Type | Required |
|---|---|---|
Client ID | text | Yes |
Client secret | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
rental_properties | Properties managed as rentals in Buildium. | Full refresh | — | — |
rental_units | Individual units within rental properties. | Full refresh | — | — |
leases | Rental agreements for property units. | Incremental, Full refresh | LastUpdatedDateTime | — |
tenants | Tenants associated with rental leases. | Full refresh | — | — |
rental_owners | Owners of managed rental properties. | Full refresh | — | — |
vendors | Vendors that provide services for managed properties. | Full refresh | — | — |
bills | Bills recorded in Buildium accounting. | Full refresh | — | — |
general_ledger_accounts | Accounts that classify accounting transactions. | Full refresh | — | — |
work_orders | Work orders for property maintenance. | Full refresh | — | — |
applicants | Applicants for rental properties and units. | Incremental, Full refresh | LastUpdatedDateTime | — |
bank_accounts | Bank accounts that hold property, company, and association funds. | Full refresh | — | — |
general_ledger_transactions | Financial transactions recorded in the general ledger, with their journal lines. | Incremental, Full refresh | LastUpdatedDateTime | — |
lease_transactions | Charges, payments, credits, and other transactions on each lease ledger. | Full refresh | — | — |
lease_outstanding_balances | Leases that have an outstanding balance, split by how long the amount has been due. | Full refresh | — | — |
inventory_assets | Inventory items and assets tracked for properties, units, and the company. | Full refresh | — | — |
inventory_storages | Storage locations that hold inventory assets. | Full refresh | — | — |
asset_categories | Categories used to group inventory assets. | Full refresh | — | — |
custom_field_definitions | Custom fields defined for each Buildium entity type, such as rentals, leases, and vendors. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your client ID or client secret is invalid. Create a new API key in Buildium under Settings > Developer Tools, then reconnect.
- If you see a permissions error, your API key does not have the required access. Make sure Open API is enabled and your key has View access for the tables you want to sync.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.