Every real estate brokerage, team, and investor site eventually hits the same wall: the listings on the website don’t match the MLS, photos are missing, status updates lag by a day, or the “IDX plugin” the last developer installed quietly stopped syncing six months ago and nobody noticed. If you’ve ever asked “why does my site still show a house that sold three weeks ago,” you’ve run into an MLS/IDX integration problem — and it’s almost always fixable once you understand what’s actually happening behind the scenes.
This isn’t a theoretical IT topic. For brokerages, investor platforms, and off-market deal sites, listing data is the product. If it’s stale, mismapped, or non-compliant, it costs leads and it can cost MLS access entirely. Here’s how the pipe from the MLS to your website actually works, where it breaks, and what a properly built integration looks like.
RETS vs. RESO Web API: What’s Actually Different
For close to two decades, MLS data moved through RETS (Real Estate Transaction Standard) — a now-aging protocol for pulling listing data in bulk. Most MLSs have either shut RETS off already or have a hard retirement date on the calendar. The replacement is the RESO Web API, built on standard REST and OData conventions, which is faster to query, easier to filter, and far less painful to debug than RETS ever was.
The practical difference matters for anyone still running an older IDX setup: a RETS-based integration built five or six years ago is running on borrowed time. If your MLS has announced a RETS shutdown date, or your IDX vendor has gone quiet about a transition plan, that’s not a “someday” problem — it’s a “the listings on your site stop updating on a specific date” problem. The fix is a RESO Web API migration, not a patch.
RESO Web API also standardizes field names across participating MLSs through the Data Dictionary — in theory. In practice, every MLS still customizes enough fields, lookup values, and photo delivery quirks that “standardized” is a starting point, not a guarantee. More on that below.
The Three Ways Listings Actually Get Onto a Site
Almost every real estate website uses one of three approaches, and the right one depends on budget, how much control you need over search and design, and how the data will be reused:
- A plug-in-and-go IDX widget. Services like IDX Broker or similar vendors embed a search widget or iframe on your site. Fast to set up, low maintenance, but limited: you’re stuck with their search UI, their page speed, and often their branding bleeding through. Fine for a solo agent who just needs a search box. Rarely enough for a brokerage, investor platform, or anyone doing custom filtering (off-market flags, cap rate estimates, zoning overlays).
- A custom RESO Web API integration. You pull listing data directly via the MLS’s RESO Web API, store it in your own database, and build search, map, and listing pages exactly how you want them. This is more development work up front, but it’s the only path if you need custom data logic — commercial property filters, investor-specific tagging, integration with a CRM or buyer database, or combining MLS data with public records and GIS layers.
- A hybrid. Use a vendor’s widget for basic IDX compliance and lead capture, while running a separate custom pipeline for the data you actually want to do something with (deal analysis, owner research, off-market outreach). This is common for investor-focused sites that need IDX-compliant listing display alongside a much more aggressive internal data layer that was never meant to be public-facing.
The mistake we see most often: a brokerage outgrows the plug-in widget two or three years in, but keeps paying for it and bolting workarounds onto it instead of migrating to a real integration, because nobody budgeted for the switch. If your current IDX setup can’t do the one thing your business actually needs — custom search logic, investor-specific data, CRM sync — it’s worth pricing out what a direct integration costs versus what the workaround is costing you in lost functionality.
The Part Nobody Talks About: Data Normalization
This is where most IDX projects quietly go over budget. Pulling data from the MLS is the easy part. Making it usable is not.
Every MLS — even on RESO Web API — has its own quirks: different lookup values for property subtype, different status code behavior (does “Pending” mean under contract or just an accepted offer awaiting inspection?), inconsistent photo ordering and resolution, and fields that exist in one MLS’s data dictionary and simply don’t exist in another’s. If you operate across more than one MLS (common for brokerages near a county or state line, and almost universal for investor platforms doing off-market outreach across a region), you’re not integrating with “the MLS” — you’re integrating with several MLSs that each describe the same real-world thing slightly differently.
A real integration needs a normalization layer: a mapping table that translates each MLS’s field names, status codes, and property types into one consistent internal schema before anything touches your website’s database. Skip this step and you end up with bugs like commercial listings showing up in a residential search, or a property showing as “Active” on your site for a day after it went under contract because the status-code mapping was wrong, not because the sync job failed.
We build this mapping explicitly, test it against real listing data from each source MLS, and re-validate it whenever an MLS pushes a data dictionary update — because they do, usually without much warning.
IDX Compliance Isn’t Optional
Every MLS that grants IDX access attaches a rulebook, and most brokers never read the actual document — their IDX vendor just handles it. If you’re running a custom integration, you own that responsibility directly, and getting it wrong can mean losing data access entirely, not just a warning email. The rules that come up most often:
- Broker attribution. Listing broker and agent name typically has to display with every listing, in a specific format and size defined by the MLS rules — not buried in fine print.
- Listing office/courtesy of. Reciprocity agreements between MLSs often require showing which office actually has the listing, even on a competitor’s site.
- Update frequency. Most MLS agreements specify a maximum staleness window (commonly 24 hours, sometimes less) for sold/pending status. A sync job that silently fails for a week is a compliance violation, not just a bad user experience.
- What you can and can’t do with the data. Some MLSs restrict scraping sold-price history into public-facing valuation tools, restrict display of certain fields (like showing instructions or private remarks), or limit how long you can retain data after a listing is removed.
We build monitoring into every MLS integration specifically so a silent sync failure gets caught in hours, not weeks — because “the feed broke and nobody noticed” is the single most common way agencies end up in a compliance conversation with their MLS.
What We Actually Build
When Vandulo takes on an MLS/IDX project, the build typically includes: a direct RESO Web API connection to the relevant MLS (or MLSs, for multi-market operations), a normalization layer that maps every source MLS into one clean internal schema, a caching and refresh strategy that respects the MLS’s update-frequency rules without hammering their API, custom search and map pages built to match the site rather than a vendor’s generic template, and monitoring that flags a broken sync before it becomes a compliance issue.
For investor and off-market focused clients, we also layer in the pieces a standard IDX setup was never built for: tagging listings against buyer-box criteria, cross-referencing MLS data with public records and owner information, and feeding qualified listings into a CRM or buyer database automatically instead of through manual export-and-import.
If your current IDX setup is held together with a vendor widget and hope, or you’re facing an MLS’s RETS shutdown deadline with no migration plan, that’s exactly the kind of project we handle. Take a look at Vandulo’s IDX for Real Estate service page for more on how we approach these builds, or reach out through the contact form or the chat widget on vandulo.com and we’ll walk through what your specific MLS setup actually needs.