Build your PMS integration once
One API that normalizes AppFolio, Yardi, RealPage, Entrata, and the rest of our supported list into consistent resident, lease, unit, and payment models.
What does the Unified API actually normalize?
The Unified API is the fully normalized product. One endpoint returns consistent resident, lease, unit, charge, and payment models across AppFolio, Yardi, RealPage, Entrata, and the rest of the supported list. Connect is a different product: it extracts and loads raw data across the catalog. This page is the one that unifies the schema.
That split matters because most "unified integration" pages collapse the two jobs. A warehouse feed and a normalized application API are not the same thing. If you want source-native tables in Snowflake, BigQuery, or Databricks, that is Connect. If you want one resident object no matter which PMS the property runs, that is the Unified API. The API docs are the live contract.
What do you get from one normalized PMS API?
Build once, connect everywhere.
Normalized Data Models
Consistent schemas for residents, leases, units, charges, and payments, regardless of the source PMS.
Webhooks
Get notified when data changes. Subscribe to granular events across any connected PMS.
99.9% Uptime SLA
Enterprise-grade reliability backed by redundant infrastructure and 24/7 monitoring.
Which property systems does the Unified API cover?
Every property management system and rental CRM the Unified API supports. One normalized schema across all of them.
Property Management Software
Rental CRMs
What does a normalized resident look like?
Every PMS returns the same normalized format. No per-vendor logic needed.
GET /v1/residents?property_id=prop_12345{ "data": [{ "id": "res_98765", "first_name": "Jane", "last_name": "Cooper", "unit": "204B", "lease_status": "active" }], "pagination": { "total": 342, "page": 1 } }
Frequently asked questions
What is a unified property management API?
A unified property management API is one endpoint that returns the same resident, lease, unit, charge, and payment models no matter which PMS the property runs. The Unified API is that product: you build against one schema, and it covers Yardi, RealPage, Entrata, MRI Software, ResMan, Rent Manager, AppFolio, Buildium, Propertyware, and Rentvine. You do not write per-vendor mapping for those objects.
Does the Unified API normalize Yardi, RealPage, and Entrata data?
Yes. This is the product that normalizes. Yardi, RealPage, Entrata, AppFolio, and the rest of the supported PMS list come back as consistent resident, lease, unit, charge, and payment objects. Connect is a different product: it extracts and loads raw data across a much wider catalog, and does not normalize every source.
How is the Unified API different from Connect?
Connect is the managed extract-and-load path: pre-built connectors that land source-native tables in a warehouse you own. The Unified API is the fully normalized product for supported PMS platforms and rental CRMs. Use Connect when you want the warehouse feed. Use the Unified API when you are building an application that should not care which PMS sits behind a given property.
Which PMS platforms and CRMs does the Unified API support?
Property management systems: Yardi, RealPage, Entrata, MRI Software, ResMan, Rent Manager, AppFolio, Buildium, Propertyware, and Rentvine. Rental CRMs: Funnel, Knock, RentCafe, and EliseAI. The same normalized schema covers the objects those systems expose for residents, leases, units, charges, and payments. The full catalog of Connect source connectors is wider than this list, and those extra sources are raw extract-and-load, not Unified API.
How can operators connect every property management system together?
They do not connect the PMS systems to each other. For application builders, the Unified API is the join: one schema across the supported PMS list, so a resident in Yardi and a resident in Entrata share a model. For warehouse work, Connect lands each system in its own shape and the modelling is downstream. Most operators who want both use both.