Appearance
Buildium
undefined
| Detail | Value |
|---|---|
| Category | Real Estate |
| Base URL | https://api.buildium.com/v1 |
| Authentication | API Key |
| Endpoints | 7 |
| Connector key | buildium |
Using Buildium in a workflow
- Go to Connections and click New Connection.
- Pick Buildium from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Rentals |
GET | Units |
GET | Leases |
GET | Tenants |
GET | Work Orders |
GET | Transactions |
GET | Vendors |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Rentals
| Detail | Value |
|---|---|
| Operation ID | rentals_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Buildium connection from the Connection dropdown.
- In the Operation dropdown, select
rentals_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Buildium API reference.
GET
Units
| Detail | Value |
|---|---|
| Operation ID | units_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Buildium connection from the Connection dropdown.
- In the Operation dropdown, select
units_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Buildium API reference.
GET
Leases
| Detail | Value |
|---|---|
| Operation ID | leases_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Buildium connection from the Connection dropdown.
- In the Operation dropdown, select
leases_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Buildium API reference.
GET
Tenants
| Detail | Value |
|---|---|
| Operation ID | tenants_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Buildium connection from the Connection dropdown.
- In the Operation dropdown, select
tenants_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Buildium API reference.
GET
Work Orders
| Detail | Value |
|---|---|
| Operation ID | work_orders_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Buildium connection from the Connection dropdown.
- In the Operation dropdown, select
work_orders_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Buildium API reference.
GET
Transactions
| Detail | Value |
|---|---|
| Operation ID | transactions_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Buildium connection from the Connection dropdown.
- In the Operation dropdown, select
transactions_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Buildium API reference.
GET
Vendors
| Detail | Value |
|---|---|
| Operation ID | vendors_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Buildium connection from the Connection dropdown.
- In the Operation dropdown, select
vendors_6. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Buildium API reference.