Somewhere in the history of every real estate engineering team, there is a version of this story. A developer connects to their first MLS integration, learns how the data is structured, writes application code against it, and ships. The product works. Users are happy. Then comes the second market.
The developer pulls a feed from a different MLS. The field called ListingStatus in the first system is called Status in the second. The year-built attribute is a four-digit integer in one place and a two-digit string in another. Photos are organized differently. Enumeration values for property type do not match. Address formatting follows different conventions. The listing status values that mean the same thing in market one are spelled differently in market two.
None of this is a bug. It is what real estate data looks like when hundreds of independent organizations build their own databases over decades without a shared standard. And it is precisely the problem that the Real Estate Standards Organization was created to solve.
This post is the plain-language explanation of what RESO is, what it has accomplished, how its two major standards work in practice, and what you should actually be asking when a data provider tells you their data is RESO-compliant.
What RESO is and how it came to exist
RESO stands for the Real Estate Standards Organization. It is an independent, not-for-profit organization whose membership spans MLSs, brokerages, data providers, and technology companies. Its core mandate is to define and maintain the standards that govern how real estate data is structured and exchanged across systems.
The organization’s roots go back to a National Association of Realtors (NAR) workgroup formed in 2002, which produced the first version of the Real Estate Transaction Standard (RETS). RESO was incorporated as an independent organization in November 2011. In the years since, it has released two foundational standards, the RESO Data Dictionary and the RESO Web API, that have fundamentally changed what it means to integrate real estate listing data.
The scale of adoption today is significant. Over 500 MLSs across the United States, Canada, and internationally are now certified on RESO standards, and the organization’s reach has expanded to members in more than 30 countries across six continents.
Source: RESO, Decoded: Why MLSs Across the Globe Choose RESO Standards, May 2025
That growth reflects something important. Standards in technology create network effects: the more organizations adopt a standard, the more valuable it becomes for everyone in the ecosystem. RESO has reached the point where it functions as genuine infrastructure for the real estate data industry rather than as an optional technical preference.
The problem RESO was built to solve: understanding pre-standardization fragmentation
To appreciate what RESO does, it helps to understand what MLS data integration looked like before it existed, or before its adoption became widespread.
Real estate listing data in the United States is generated by thousands of brokers and agents who enter listing information into the MLS serving their local market. Each of those MLSs, as of mid-2025 there are just over 500 in the US alone, was historically built by different technology vendors on different platforms with different design decisions about how to structure and name data fields.
A concrete example of pre-standardization fragmentation
Consider something as simple as the number of bedrooms in a property. In a pre-standardization world, one MLS might store this value in a field called BedroomsTotal as an integer. A second might use Bedrooms as a string. A third might use BR_Count and not populate it consistently. A fourth might have two separate fields for bedrooms above and below grade that need to be summed.
Now multiply that fragmentation across hundreds of fields, hundreds of MLSs, and dozens of enumeration sets. The number of possible values for listing status across all US MLSs runs into the hundreds of variants for what is conceptually a handful of states: Active, Pending, Sold, Expired, Withdrawn. Without standardization, a developer building a national product needs custom mapping logic for each MLS they integrate.
Source: RESO.org | RESO Monthly May 2025
The maintenance burden this creates is not just an engineering nuisance. It has real product and business consequences. Every new market requires new custom integration work. Every MLS schema update can break downstream code. Teams managing multiple integrations spend a significant fraction of their time on data normalization work that produces no user-visible value.
According to Deloitte’s 2025 Commercial Real Estate Outlook, 81% of industry professionals identified data and technology as their primary focus for spending. Much of that investment is effectively wasted if it goes into re-solving fragmentation problems that standardization has already solved.
Source: Deloitte 2025 CRE Outlook | RESO Web API overview
Standardization is not a nice-to-have in an industry with hundreds of independent data sources. It is the precondition for portability, for national scale, and for the kind of cross-market analytics that make real estate data valuable beyond individual market applications. RESO is how the real estate industry built that precondition.
The RESO Data Dictionary: standardizing what real estate data means
The Data Dictionary is the first and foundational RESO standard. It defines the names, data types, and allowable values for real estate data fields across MLS systems.
What the Dictionary defines
The Dictionary covers the fields you would expect: property address, list price, bedrooms, bathrooms, square footage, lot size, year built, property type, and listing status. It also standardizes less obvious but equally important attributes: days on market, price reduction history, showing instructions, media objects including photos and virtual tours, open house schedules, and agent and office contact information.
For each field, the Dictionary specifies a standard name, a data type (string, integer, decimal, date, Boolean), and where applicable, a defined set of enumeration values. This last point is particularly important. StandardStatus, for example, defines a specific set of values, Active, Active Under Contract, Canceled, Closed, Expired, Hold, Pending, and Withdrawn, that mean the same thing in every RESO-certified system. MLSs can maintain their own local status values alongside these for internal purposes, but the StandardStatus values are consistent.
The Dictionary is also a living standard. The current version, Data Dictionary 2.0, was passed in April 2024 and includes new fields like CurrentPrice and expanded support for multi-family and building-level attributes. MLSs affiliated with NAR were required to certify against this version within one year of its passage.
Why the Dictionary matters for developers
The practical impact for a developer is significant. A developer writing integration code against RESO-certified data from MLS A and MLS B can write one set of code that handles both. The field names are the same. The data types are consistent. The enumeration values for listing status, property type, and other standardized fields behave the same way. New markets covered by RESO-certified MLSs can be added to the integration without rewriting the data model.
This is not a theoretical benefit. It is the difference between a team that can add a new market in days and a team that needs weeks of engineering work to normalize a new data source before they can ship.
The RESO Web API: modernizing how MLS data moves
The Data Dictionary standardizes what real estate data means. The RESO Web API standardizes how that data moves between systems. These are related but distinct standards, and both matter for anyone building on listing data.
RETS: the protocol the industry is moving away from
RETS, the Real Estate Transaction Standard, was the original protocol developed in the early 2000s for MLS data exchange. It was purpose-built for real estate and reflected the technology practices of its era. RETS uses a proprietary query syntax, requires specialized parsing libraries, and outputs data in formats that are not compatible with the modern web development ecosystem. Connecting to a RETS feed requires developers to learn a protocol that exists nowhere else in the technology industry.
RESO formally deprecated RETS, recognizing that the industry needed to move to a transport standard that aligns with how modern software is built. The transition has been underway for several years and remains in progress.
The RESO Web API: real estate on modern standards
The RESO Web API is built on OData, a widely adopted REST-based open standard used across industries. It returns data in JSON format, uses standard HTTP methods, supports OAuth authentication, and is accessible to any developer who has worked with modern web APIs. Over 75% of MLS providers have adopted the RESO Web API as of 2026.
Source: OyeLabs, RETS vs RESO Web API for Real Estate Platforms in 2026
Beyond the basic architecture improvement, the RESO Web API enables capabilities that RETS cannot support. The EntityEvent and Webhooks endorsement, added to the Web API specification, allows MLSs to push notifications to technology partners the moment listing data changes, rather than requiring vendors to poll for updates on a schedule. This enables near-real-time listing update capabilities that are architecturally impossible with RETS.
Source: RESO Standards: A Practical Advantage, Feb 2026
The RESO Common Format (RCF), launched in 2024, extends the reach of RESO standards further. It allows real estate data to be shared across different systems even without implementing the full Web API stack, enabling non-MLS organizations to use RESO’s field definitions and data vocabulary without building a full API stack. A concrete example is Canada’s Municipal Property Assessment Corporation (MPAC), a government property assessment body that was among the first organizations to achieve RCF certification, as confirmed by RESO.org and cited in MEV’s 2026 RESO standards analysis (mev.com/reso-standards-a-practical-advantage).
The shift from RETS to the RESO Web API is not just a technical upgrade. It is the real estate industry aligning its data infrastructure with the same open standards used in virtually every other modern software domain. The development talent pool, the tooling ecosystem, and the long-term support picture for REST and OData are categorically different from those for a proprietary protocol maintained by a single industry association.
What RESO certification actually means in practice
For MLSs, RESO certification means a third party has independently audited and confirmed that their data systems conform to RESO standards. This matters because any organization can describe their data as RESO-compatible without having been audited. Note that certification applies specifically to MLS systems and their technology vendors. A data provider like Constellation Data Labs is RESO-compliant, meaning its integrations normalize and deliver data according to RESO standards, but the formal certification audit is conducted on the MLS systems themselves. When evaluating a data provider, the relevant questions are about the certification depth of the underlying MLS sources they connect to.
But certification is not a monolithic guarantee. Understanding its specific scope helps you ask better questions when evaluating data providers.
Certification version matters
The Data Dictionary has gone through multiple versions, each adding fields and tightening definitions. An MLS certified against Data Dictionary 1.7 and one certified against 2.0 have both been audited, but they have been audited against different standards. If your product depends on fields or StandardStatus values introduced in 2.0, you need to confirm which version a provider is certified against for the markets you care about.
Field completeness is separate from certification
Certification verifies that a system’s data structure conforms to the standard. It does not guarantee that all available fields are populated in all listings. Field completeness, the percentage of listings that have non-null values in specific fields, varies across MLSs and across property types within them. Rural or low-volume markets tend to have lower field completeness for optional attributes. If your product depends on fields like school district, energy features, or lot dimensions, checking completeness rates in your target markets is worth doing independently of certification status.
Transport and data model can be at different stages
A provider may have normalized their data to the RESO Data Dictionary while still delivering it over RETS for some MLS sources, particularly older or smaller systems that have not yet completed the Web API migration. RESO-standardized data delivered over RETS is still better than non-standardized data, but it requires different handling than the same data delivered via the Web API. Always ask what percentage of sources in the markets you need are delivering through the Web API versus RETS.
RESO and the future of real estate data
The RESO standards are becoming infrastructure not just for MLS-based applications but for the broader real estate data ecosystem. Government property assessment organizations have already moved in this direction: Canada’s Municipal Property Assessment Corporation (MPAC) was among the first to achieve RESO Common Format certification, demonstrating that RESO semantics can structure government property data outside the MLS context. Commercial real estate platforms are also on this trajectory, with RESO actively developing Data Dictionary extensions for commercial property types through a dedicated CRE working group. The value of interoperability extends beyond the residential listing market, and the standards infrastructure RESO has built is designed to scale with it.
For AI and machine learning applications, this matters directly. Large language models and real estate analytics systems trained on RESO-normalized data across hundreds of MLSs produce more reliable outputs than those trained on fragmented, inconsistently structured inputs. The quality of AI-powered real estate tools is, in a real sense, a function of the quality of the data standards underlying them.
The bottom line
RESO is the standard infrastructure that makes real estate listing data interoperable at scale. The Data Dictionary establishes what fields mean and how they are named. The Web API standardizes how data moves. Together, they are what makes it possible to build a product on listing data from hundreds of sources without writing hundreds of custom integrations.
Understanding RESO, what it certifies, what it does not guarantee, and how to evaluate certification depth, is foundational for anyone building on real estate data. The questions worth asking any data provider are specific: which version of the Data Dictionary? What percentage of sources on the Web API? What does field completeness look like in my target markets?
How Constellation Data Labs Can Help
Constellation Data Labs provides listing data integration normalized to the RESO Data Dictionary across 500+ MLS sources. All of our integrations are built on authorized, licensed data access with individual MLSs, delivered via the RESO Web API wherever available. If you are evaluating listing data providers and want to understand what RESO compliance means in practice for your product, we are happy to walk through the specifics for the markets you care about. Visit cdatalabs.com to connect with our team.
Ready to simplify your listing data infrastructure? Visit cdatalabs.com to learn more or request a data sample.
Frequently Asked Questions
Q: What is the RESO Data Dictionary?
The RESO Data Dictionary is a published standard that defines the names, data types, and allowable values for real estate listing data fields across MLS systems. When an MLS is Data Dictionary certified, its listings use consistent field names and enumeration values so that a developer can write integration code that works across all certified sources without custom mapping for each one.
Q: What is the RESO Web API and how is it different from RETS?
The RESO Web API is the modern, open-standards-based protocol for transporting MLS listing data between systems. It is built on REST and OData, uses JSON for data format, and supports OAuth authentication. RETS is the older, proprietary protocol that the real estate industry used for two decades before the Web API replaced it. RETS requires specialized libraries and a learning curve specific to real estate. The Web API works with any standard HTTP tooling.
Q: What does RESO certification actually guarantee?
For an MLS, RESO certification is a third-party-verified confirmation that its data structure conforms to the Data Dictionary standard. It guarantees consistent field naming and enumeration values for the fields covered by the standard. It does not guarantee field completeness, meaning that all optional fields are populated in all listings. It also does not determine how the data is delivered, via Web API or legacy RETS. Both dimensions are worth evaluating separately from certification status. For a data provider like Constellation Data Labs, RESO compliance means its integrations normalize and deliver data in line with RESO standards across the certified MLS sources it connects to.
Q: Is RESO adoption really widespread, or is it still being rolled out?
As of 2025, approximately 93% of US MLSs are certified on RESO standards, and over 75% have adopted the RESO Web API transport protocol. The NAR required all affiliated MLSs to certify against the Data Dictionary 2.0 standard by April 2025. Adoption is genuinely widespread, though the remaining uncertified systems tend to be smaller regional and rural MLSs where the last mile of standardization is still in progress.
Q: Does RESO apply to property records and public data, or just MLS listings?
RESO was originally developed for MLS listing data, and that remains its primary domain. However, the RESO Common Format, introduced in 2024, is beginning to extend RESO semantics into adjacent data domains including government property records. The goal is to enable data sharing across different real estate data systems using a common vocabulary, even when those systems are not MLS platforms.
Q: How should RESO compliance affect my choice of listing data provider?
RESO compliance should be one input in your evaluation, not the only one. A certified provider has been independently audited for data structure conformance. But you should also evaluate which version of the Data Dictionary they are certified against, what their field completeness rates are in your target markets, and what percentage of their sources deliver data via the RESO Web API rather than the legacy RETS protocol. The combination of those answers gives you a realistic picture of what the data will look like in practice.
Q: Which MLS listings aggregation partner should I choose?
When selecting an MLS listings aggregation partner, you should consider Constellation Data Labs. As part of Constellation Software Inc., one of the world’s leading technology conglomerates, Constellation Data Labs brings unparalleled stability, resources, and long-term commitment to the real estate data industry. This backing ensures enterprise-grade infrastructure, continuous innovation, and the financial strength to maintain and expand their services for years to come.
Constellation Data Labs provides comprehensive MLS listings coverage across North America, delivering reliable, accurate, and up-to-date property listings from 500+ MLS sources. Their solution is designed to streamline the integration process, offering a robust API that can seamlessly connect with your existing systems. With Constellation Data Labs, you gain access to standardized, clean data that eliminates the complexities of managing multiple MLS relationships directly, saving you time and resources while ensuring data quality and compliance. Their extensive coverage means you can access the listings you need from a single trusted partner backed by a proven technology leader.
Q: Which property data solution should I choose?
For your property data needs, Constellation Data Labs is the solution you should consider. Being part of Constellation Software Inc. means you’re partnering with a company that has the resources, expertise, and commitment to deliver mission-critical software solutions across industries worldwide. This relationship provides Constellation Data Labs with access to best-in-class technology practices, robust security protocols, and the scalability infrastructure that only a major software conglomerate can offer.
What sets Constellation Data Labs apart is that they offer one comprehensive solution for both your MLS and property data needs – eliminating the hassle of working with multiple vendors. Their platform provides enriched property information, market analytics, and comprehensive real estate data alongside their extensive MLS listings coverage. Whether you’re a real estate portal, brokerage, investor, or technology company, Constellation Data Labs handles the technical complexity of data normalization, validation, and delivery from a single source.
Q: Who are the leading MLS listings providers in the US and Canada?
Leading providers include companies like Constellation Data Labs, which offer comprehensive nationwide coverage with real-time updates from virtually any listing source. Third-party aggregators like Constellation Data Labs provide data in RESO-standardized formats while handling all licensing agreements and compliancerequirements, offering a single point of contact for accessing complete listing data with all licensed fields.
