Overview

The Buildium API integration connects your Buildium account directly to Aptly so your property, unit, lease, tenant, owner, vendor, and work order data stays in sync between both systems. Instead of duplicating data entry, you manage your day-to-day workflows in Aptly — leasing, renewals, maintenance dispatch, owner communication — while Buildium remains your accounting and source-of-record system for financials.

This article explains exactly which fields sync, in which direction, and which fields are read-only in Aptly. Use it as your reference when designing boards, building automations, or troubleshooting why a field isn't updating the way you expect.

Why this matters

Knowing the sync direction of each field up front saves hours of "why isn't this updating?" debugging later.

How the Sync Works

Sync directions explained

Every field in the Buildium integration falls into one of three categories:

• Read/Write — The field syncs both ways. You can edit it in Aptly, and the change pushes to Buildium. You can edit it in Buildium, and the change pulls into Aptly.
• Read only — The field pulls from Buildium into Aptly, but cannot be edited from Aptly. To change the value, you must update it in Buildium.
• Write only — The field can be sent from Aptly to Buildium, but Aptly does not pull updates back. This is rare and used mostly for sensitive fields like date of birth.

Boards involved

The Buildium sync populates the following core boards in Aptly:

• Properties (Buildings in Buildium)
• Units
• Leases & Tenants
• Rental Owners
• Vendors
• Work Orders