MLS integration and listing feeds

Your homes for sale, on your site, straight from the MLS.

A page for every home you have listed, with the price, the status and the photos kept in step with your MLS. RealTracs, MLS Grid, Trestle, Bridge, Spark, or your MLS’s own RESO Web API. Built into the site, not bolted on.

Short answer

A builder website can pull its listings directly from the MLS. Your broker signs the data license, the MLS approves it, and we connect the feed over the RESO Web API. From then on every home you list gets its own page on your site, a quick move in list and a home search update themselves, and a sold home drops off without anyone touching the site. We connect RealTracs and the other MLSs on MLS Grid, plus Trestle, Bridge Interactive, Spark and the large MLSs that run their own API.

How a listing feed gets built.

  1. Your broker signs the data license. The MLS licenses its data to a vendor for your site. We send the paperwork, your broker signs it, the MLS approves it on its own schedule. This is the one step we cannot speed up, so it is the first thing we start.
  2. We connect the feed. One connection to the MLS’s RESO Web API, filtered to your listing office or builder name, replicated to the site on a schedule inside the MLS’s rate limits.
  3. Every home gets a page. Address, price, beds, baths, square footage, community, plan, photos and status, mapped from the RESO Data Dictionary to your design. A quick move in list and a search by community, price and size come with it.
  4. Launch does not wait for approval. Until the license is granted the site runs on a copy of your current listings, refreshed when you send changes. The day it is approved the live import switches on.
  5. It keeps itself current. New listing, new page. Price change, updated. Sold, gone. The same data can also be published out to Zillow New Construction and BDX so your portals match your site.

The feeds we connect.

Nearly every MLS in the country now delivers data the same way, over the RESO Web API, through one of a handful of platforms. Here is each one and what it means for your build.

MLS Grid

One RESO Web API and one data license agreement for about 35 MLSswww.mlsgrid.com

The route we use for RealTracs, the MLS for Middle Tennessee, and for every other MLS on the Grid: Stellar MLS in Florida, Canopy MLS in the Carolinas, ACTRIS in Austin, MRED in Chicago, NorthstarMLS in Minnesota, Northwest MLS in Washington, REcolorado, Heartland MLS in Kansas City, MARIS in St. Louis, MIBOR in Indianapolis, OneKey MLS in New York, Indiana Regional MLS, MLSOK, and the regional boards around them.

One standard license for all of them, approved by your MLS, and one OData API on RESO Data Dictionary fields. The feed refreshes on a schedule inside the Grid’s rate limits, and a builder’s own listings are filtered by office or builder name.

Trestle

Cotality, formerly CoreLogic. Vendor data licensing for many MLSstrestle.corelogic.com

Trestle is the licensing and delivery platform a large share of MLSs use to hand data to vendors. RESO Web API on Data Dictionary fields, contract and billing handled on the platform, the MLS still approves.

If your MLS is on Trestle, the connection on our side is the same shape as the Grid: a replicated copy of your listings, refreshed on a schedule, with every home getting its own page.

Bridge Interactive

Zillow Group. Data distribution for MLSs and associationsbridgedataoutput.com

Bridge is Zillow’s data platform, used by MLSs to license their data to vendors and by Zillow for syndication. Listings arrive normalized to RESO standards over the Web API.

Access starts with the MLS, which is who to ask about licensing. Once approved, our import treats it the same way as any other RESO source.

Spark API

FBS, the company behind Flexmlswww.sparkplatform.com

Spark is the API for every MLS that runs on Flexmls. It offers a proprietary API and a read only RESO Web API inside it, with one key for both.

For a single MLS on Flexmls we use the Spark API directly. For a builder in several markets we use the RESO side so the fields line up across them.

MLSs with their own RESO Web API

Bright MLS, CRMLS and other large regional MLSswww.reso.org

Some of the largest MLSs run their own vendor programs and their own RESO certified Web API rather than a middle platform. The license comes from the MLS, the endpoint is theirs, the fields follow the same Data Dictionary.

RETS, the older transport, is being retired industry wide and RESO no longer updates it. If a feed you already have is RETS, we move it to the Web API as part of the build.

Sending your inventory out

Zillow New Construction, BDX for NewHomeSource and realtor.comwww.thebdx.com

The other direction. A builder’s communities, plans, specs and lots can be published from the site as a feed that Zillow’s New Construction program and BDX accept, so the homes on your site and the homes on those portals are the same list, updated from one place.

We build the feed from the same data that drives your inventory pages. You enter a spec home once.

Questions builders ask about MLS feeds.

Can a home builder show MLS listings on their own website?

Yes. Your broker, or the brokerage that lists your homes, holds the MLS membership, and the MLS licenses the data to a vendor for display on your site under its IDX or VOW rules. We are the vendor. The site shows the homes you have for sale, straight from the listing feed, with price, status and photos kept in step with the MLS.

Which MLS systems can you integrate with?

Any MLS that delivers data over the RESO Web API, which is now nearly all of them. That includes RealTracs in Tennessee and the roughly 35 MLSs on MLS Grid, the MLSs licensed through Trestle and Bridge Interactive, Flexmls systems through the Spark API, and large MLSs with their own API such as Bright MLS and CRMLS. If your MLS still runs RETS, we convert the feed to the Web API as part of the build.

How long does MLS approval take?

The MLS decides, and it is usually days to a few weeks after your broker signs the data license. It does not hold up the launch. Until the feed is approved the site runs on a copy of your current listings, refreshed when you send changes, and the live import is switched on the day the license is granted.

What does an MLS feed cost?

Two parts. The MLS and the data platform set their own license fees, paid by you directly, and we get you that quote before your broker signs. Our work to connect the feed, map the fields, build the home pages and the search, and keep it refreshing is a line in your fixed written scope.

Can the site show only our homes, not the whole MLS?

Yes, and that is how most builders want it. The import is filtered to your listing office or builder name, so the site shows your inventory and nothing else. A builder who also wants a full market search for buyers can have that too, under the same license, on its own page.

What if our homes are not in an MLS?

Then the inventory is built from your own data, in a simple sheet or an admin page your team keeps current, and every home still gets its own page. We can also publish that inventory outward to Zillow New Construction and to BDX, which feeds NewHomeSource and realtor.com, so you enter a home once.

Let’s build yours.

Tell us what you build and where. We read every one of these ourselves and reply with honest next steps, including a written scope with a fixed price.

Prefer to talk it through? Call (615) 915-7899 or email ryan@siteworkdigital.ai