BU Portals · Data Brokers

One API for every Real Estate Listing.

Portals + brokerages publish active and sold listing data. Third parties pull comps, leads, valuations, and market analytics from the same canonical contract. Listing Data is the connective tissue.

Pick your side

Two products. One contract.

Supply

For Portals + Publishers

MLSs, brokerage feeds, and any platform that wants its active listings reaching the broader Broker Union network + every data-broker contract. Push once, distribute everywhere.

Demand

For Data Brokers

Lead-gen, valuation models, AVMs, comp engines, market analytics. Buy active listings (from portals) and sold-property data (from brokers via Broker Union) — one schema, one API.

How it fits together

Producers. Schema. Consumers.

  1. 01

    Producers publish

    Portals push active listings; real estate brokers (via Broker Union) push closed transactions. Both write into the same canonical fields.

  2. 02

    One schema

    Every record carries publisher slug, source MLS (when applicable), and a stable updatedAt. Provenance is built in; no black-box aggregation.

  3. 03

    Consumers pull

    Data brokers, BU's own brokerage tenants, and the public search indexes all query the same JSON.

Tell us what you're building — we'll route accordingly.

Publishing or consuming, drop a note with your use case. We'll come back with the right next step — mapping plan if you publish, sample payload if you consume.

Data — Broker Union