What Is RETS? Why It Was Retired and What Replaced It (RESO Web API)


Eddieweir.comBuilt Three Apps Without Coding
CB&A RealtorsBuilt an AI Operating System
HAR.comAdded Real Time Data Delivery
Unlock MLSLaunched AI-Ready Infrastructure
Joes.HomesJoes.Homes went from vibe-coding to generating leads
MARISIntroduced On-Demand Data Access
Buy.caBuy.ca Launched Cutting-Edge Features Faster
PinePine (Formerly Properly) Cut Costs
WahiWahi Built a National Product in Record Time
MaveMave Saved Months Of Development Time
For nearly two decades, if you wanted MLS data, you used RETS. The Real Estate Transaction Standard was the way listing data moved from Multiple Listing Services to the websites and tools that displayed it. If you are maintaining an older real estate integration, you have probably met RETS. And if you are building something new, you need to know that RETS is now a retired standard, and what took its place.
This guide explains what RETS is, why it was retired, and what replaced it. The short answer: RETS has been superseded by the RESO Web API, and new development should target the modern standard. For a direct comparison, see MLS API vs RETS Feed: What Developers Should Use.
RETS, the Real Estate Transaction Standard, is a protocol that defined how MLS systems and applications exchanged listing data. It was developed to standardize what had been a chaotic landscape of custom integrations, and for years it did exactly that. Technically, RETS is XML-based and built around bulk replication: you pull large datasets on a schedule and reconcile changes in your own system.
For its era, RETS was a genuine improvement, a common way to move data where none had existed. But it was designed before modern web standards, and over time its age became a limitation.
The industry moved on, deliberately. RESO, the Real Estate Standards Organization, developed a modern replacement and began phasing RETS out.
| Milestone | What happened |
|---|---|
| 2018 | RESO stopped certifying new RETS implementations |
| Transition years | MLSs adopted the RESO Web API |
| December 31, 2024 | Legacy RETS support officially ended |
The reasons were practical. RETS relied on bulk replication and polling rather than real-time queries, its XML format was heavier to work with than modern JSON, and it did not fit cleanly into contemporary web and mobile development. The RESO Web API addressed all of this, so the industry committed to it.
The RESO Web API is the modern standard that replaced RETS. It is built on REST, OData, and JSON, so instead of replicating bulk datasets, you make real-time queries and get structured responses that fit naturally into modern applications. It also standardizes field names through the RESO Data Dictionary, which brings consistency RETS lacked. See The RESO Data Dictionary Explained.
More than 500 MLSs now offer the RESO Web API, and it is the foundation the entire industry runs on. For how it works in practice, see What Is an MLS API and How Does It Work?.
You can build on the modern standard without a sales call. Get an API key, build against sample data, and move to production when ready.
If you are still on RETS, migration is both necessary and an opportunity. The direct route is to re-integrate against the RESO Web API for each MLS you use. The simpler route is to adopt a unified real estate data API built on the modern standard. Repliers consolidates hundreds of MLS systems across the US and Canada behind one real-time connection, so instead of migrating each RETS integration separately, you replace them all with a single modern one. For the build-or-buy decision, see Build vs Buy: Should You Aggregate MLS Data Yourself?.
RETS (Real Estate Transaction Standard) is a legacy protocol for transferring MLS listing data between Multiple Listing Services and applications. It is XML-based and built around bulk replication. It served the industry for years but has been retired in favor of the modern RESO Web API.
Some older systems still run on RETS, but it is a retired standard. RESO stopped certifying new RETS implementations in 2018, and legacy RETS support officially ended on December 31, 2024. New development should use the RESO Web API instead.
The RESO Web API replaced RETS. It is built on REST, OData, and JSON for real-time queries and uses the RESO Data Dictionary for standardized fields. It is now offered by more than 500 MLSs and is the current industry standard for MLS data access.
RETS was the standard that made MLS data accessible for a generation, but it is now retired: no new certifications since 2018 and legacy support ended at the close of 2024. The RESO Web API replaced it with real-time, JSON-based, standardized access, and a unified API built on that standard is the simplest way to move off RETS entirely. Repliers provides exactly that. To build on the modern standard, visit www.repliers.com to get an API key or schedule a demo.
Get an API key and start testing within minutes — no credit card required.