RESO Web API

The RESO Web API is how property listing data is supposed to move in American residential real estate. It is an OData 4.0 interface over the RESO Data Dictionary, replacing the bespoke XML of RETS. Core 2.0.0 ratified in January 2021, 2.1.0 in December 2023.

• OData-based - It builds on OData rather than inventing a query idiom, so conventional tooling works and $metadata describes the model.
• Certified - RESO runs a public conformance directory. Certificates are verifiable without an account.
• Genuinely mandated - National Association of REALTORS Policy Statement 7.90 requires association-owned multiple listing services to certify within a year of each ratification. Every other mandate in the API Evangelist sector series came from a state; this one an industry imposed on itself.
• Free to read - The specifications are anonymous downloads on GitHub and reso.org.
• OAuth-secured by the spec - Bearer or client-credentials over TLS 1.2+, with credentials issued by each MLS’s software provider rather than by RESO.

What the mandate actually bought

This is the standard’s most useful lesson, and it is not the one a conformance programme is designed to teach. The State of US Real Estate APIs scored forty-five organizations and found RESO-certified organizations average 38.0 against 36.0 for everyone else — roughly two points, for the only self-imposed machine-readable mandate in the API economy.

The reason is that certification and reachability are independent variables, and RESO certifies only the first. All three certified parties in that study are data resellers rather than portals or MLSs, and every one of their OData $metadata documents — the actual machine-readable contract — returns 401 to a caller without an executed MLS licence. The documentation is public and good. The contract is not reachable. A developer can read the standard, study the schema, and call nothing.

The corroborating detail is starker still: across all forty-five organizations, not one publishes a specification for mls, idx, media, openhouse or member — the Data Dictionary’s own core resources.

Why it matters beyond real estate

Three companion markets in the same study isolate the variable. Britain has no MLS, no data dictionary, no certification and no mandate, and out-publishes the mandated American market 42.8 to 31.2 with double the agent-readiness. Australia mandated the transaction rail instead of the schema and produced a production API carrying national property settlements. Canada’s cooperative adopted a RESO-shaped Web API voluntarily, with nobody compelling it.

The transferable finding for anyone designing a standards programme: the schema is the easy half. RESO did the hard part of vocabulary agreement genuinely well — that is the part most industries never manage. What it did not do, and was never chartered to do, was decide who may call the endpoint and how they get a credential. Finish a standard without designing the access model and you will have built an excellent description of something nobody can reach.

For the agentic turn this stops being philosophical. An agent can parse an OData contract and follow a discovery document. It cannot sign an IDX agreement, obtain broker sponsorship, or negotiate a per-MLS licence. Every access tier above self-serve in this sector is a human legal process.