Integration scope and one‑line answer

Yes — Summit integrates with Yardi and Buildium in Canada (CSV/webhooks). Solutions are available nationwide except Quebec. This page explains supported connection patterns, prerequisites, and step‑by‑step setup for each platform.

• Audience: Canadian property managers, asset managers, and realty operators using Buildium or Yardi alongside Summit for insurance workflows (e.g., certificates of insurance, vendor compliance, student tenant insurance).

• Data residency: Summit stores personal information exclusively in Canada; see our Privacy Policy.

What “integration” means with each platform

Summit supports two secure exchange patterns that align with how each platform exposes data:

• Buildium: near real‑time eventing via webhooks plus REST API pulls; bulk exports for backfill.

• Yardi: scheduled CSV/XML exports and imports via Voyager ETL; optional API access when your organization participates in Yardi’s Interface Partnership (Voyager).

The table below summarizes at a glance.

Notes (source‑backed): Buildium provides an Open API and first‑party Webhooks; Yardi’s Standard Interface Partnership exposes Voyager APIs and sandboxes; Voyager ETL supports CSV/XML import/export using format templates. See References.

Buildium setup (webhooks + API)

Follow these steps if you’re a Buildium Premium subscriber.

1) Confirm API entitlement

• Ensure your Buildium plan includes the Open API.

• In Buildium, navigate to Settings → Developer Tools to locate API credentials and Webhooks.

2) Create API credentials

• Generate a client ID and client secret for server‑to‑server authentication. Store securely.

• Summit will provision a dedicated secure endpoint; request details via our Contact page.

3) Register webhook subscriptions

• In Developer Tools → Webhooks, add subscriptions for entities relevant to insurance workflows (examples: Tenant. Created, Tenant. Updated, Lease. Created, Rental. Updated).

• Use HTTPS and validate signatures. Configure retry handling on your side if you operate middleware.

4) Authorize Summit to pull full records (optional but recommended)

• Share your API client ID/secret through your established secure channel. Summit uses read‑only GETs to hydrate full records referenced by webhook event IDs.

5) Backfill and ongoing checks

• Use Buildium’s data export features (e.g., Rentals, Tenants) for historical backfill.

• Summit maps your exported fields to our ingestion schema and reconciles against webhook‑driven deltas.

Security tips

• Use unique credentials per environment (sandbox vs. production). Rotate keys periodically.

• Limit events to only the entities you need to reduce noise and exposure.

Yardi setup (Voyager ETL CSV/XML; optional API)

Recommended when you run Yardi Voyager. If you use Breeze, see the Breeze note below.

A) Voyager ETL export (CSV/XML) — fastest path

1) Enable ETL access

• Verify your security group/menu includes Admin/Toolbox Import/Export and ETL modules.

2) Choose export objects and templates

• Common objects for insurance workflows: Tenants/Residents, Leases, Units/Properties, Vendors, Payables (bills), Certificates/Attachments if applicable.

• Use Yardi’s default CSV/XML format templates (FMT) or ETL templates; customize as needed for your fields.

3) Configure Foreign Database (ETL profile)

• Define import/export locations (CSV/XML), mapping, and scheduling preferences.

• Associate ETL Groups and ensure the correct user group permissions.

4) Schedule recurring exports

• Use Task Manager to automate nightly exports (or desired cadence).

• Output to SFTP. Summit will provide a dedicated Canadian SFTP target; request details via Contact.

5) Validate and monitor

• On first runs, compare record counts and spot‑check required fields.

• Keep an error log; export Yardi ETL error reports for quick remediation.

B) Voyager API via Yardi Interface Partnership (optional)

• If your organization already licenses a Standard Interface (e.g., Common Data, Commercial API) and works with an approved interface vendor, Summit can consume your API payloads at our secure endpoint instead of (or in addition to) CSV/XML.

• Interface programs involve licensing and vendor setup on the Yardi side. Coordinate with your Yardi account team.

Breeze note

• Yardi Breeze deployments typically rely on report/data exports rather than open API. Summit supports CSV‑based exchanges for Breeze where export features are available.

Field mapping and minimum data

To automate certificates and tenant insurance validations, include at minimum:

• Tenants/Residents: tenant_id, first/last name, email, phone, lease_id, property_id, unit, lease start/end, occupants.

• Leases: lease_id, property_id, unit, start/end, status, responsible party, rent.

• Properties/Units: property_id, property name/address, unit code, manager contact, province.

• Vendors/COIs: vendor_id, legal name, service category, insurance expiry, limits (if tracked), attachments reference.

• Payables (optional for benefit): bill_id, vendor_id, invoice no., date, amount, GL, property_id.

Summit will provide a canonical schema and perform one‑time mapping; subsequent deltas flow via webhook (Buildium) or scheduled export (Yardi).

Security, privacy, and data location

• Transport: HTTPS for API/webhooks; SFTP with strong ciphers for batch files.

• Storage: Summit stores personal information exclusively in Canada. See Privacy Policy.

• Access control: Principle of least privilege; rotate credentials and restrict IPs where possible.

• Audit: Maintain export job logs and webhook delivery logs for traceability.

Supported provinces/territories

Summit supports integrations across Canada except Quebec.

Frequently asked questions

• Can Summit push status back into my systems? Yes. For Buildium, Summit can call the Open API to update allowed fields your admin enables. For Yardi, we typically return status files for ETL import; if your Voyager Interface license permits, we can post updates via your interface vendor.

• What if we don’t have a developer? Buildium’s webhooks are configuration‑driven; no custom code is required on your side. For Yardi, your administrator can configure ETL exports and Task Manager schedules without writing code.

• How fast is “near real‑time”? Buildium webhooks generally deliver in seconds to minutes; Summit immediately pulls full records via API when needed. Yardi ETL exports run on your schedule (e.g., nightly).

• Do you integrate student tenant insurance with property systems? Yes. We routinely map student tenant data and proof‑of‑insurance artifacts from property platforms into Summit workflows. See our Property Management Insurance page for coverage context.

• How often should we rotate credentials? At least quarterly, or immediately upon personnel changes.

References (public documentation)

• Buildium Open API and Webhooks documentation (accessed December 2025).

• Yardi Interface Partnership (Standard Interface options and program details) for Voyager (accessed December 2025).

• Yardi Voyager ETL/Import‑Export documentation on CSV/XML formats and templates (accessed December 2025).

• Buildium data export instructions for Rentals/Tenants used by third‑party integrations (accessed December 2025).

Last reviewed: December 4, 2025.