Skip to main content
Multifamily endpoints cover apartment properties. Each property is one profile that gathers its facts, buildings, unit mix, rents, loans, owners, tax accounts and parcels. These endpoints need a Multifamily API key; create one in the portal under API keys. Property records keys do not work here.

Find a property

Search by address or property name:
Or by owner, operator or contact name with by=owner. A name matches when it contains every word you type. When the words narrow to five names or fewer, the search also follows each name’s mailing addresses one step, to properties whose owner record uses the same address. Each result’s connection says why it is listed.
Results are the best matches, ranked, in data.items. Set limit up to 100 for address searches and up to 500 for owner searches, so one owner search can list a whole portfolio. Search is not paged: if you get exactly limit results there may be more, so narrow the query or add state. Read full profiles one property at a time.

Read the profile

Pass a result’s property_id:
data is the property:

Things to know

  • Null means no value is held. A field can be null or absent; treat both as not reported, never as zero.
  • Inferred values are marked. An owner or operator that was inferred, rather than stated by a source, ends with ” (inferred)”. Check with value.endsWith(" (inferred)").
  • Personal data is for business use. Owner and contact names, mailing addresses and phone numbers come from public records. Use them only for business purposes, follow telemarketing and do-not-call rules, and don’t use them for consumer marketing.
  • Fields are only added. Within v4, multifamily fields may be added but are never renamed or removed.
  • Billing. Searches with matches and profile reads are billable. Empty searches, unknown ids and errors are free.