RESO Transport Specifications

Modular specifications and change proposals that define how real estate data is exchanged across the industry.

9
Ratified Standards
12
In Progress
OData 4.01
Protocol
RESO Endorsements are modular specifications associated with the RESO Web API transport protocol. Each endorsement starts as a RESO Change Proposal (RCP), progresses through community review and implementation, and is eventually ratified as a standard. Specifications use semantic versioning.
How Specifications Are Made
1

Proposal

A change proposal is submitted via GitHub Discussions with a business case and requirements.

2

Draft & Review

The Transport Workgroup reviews the draft specification and testing rules. At least two vendor implementations are required.

3

Approval

Once implementations are verified, the proposal is approved by Transport and Certification. Testing tools are built.

4

Ratification

The specification is ratified by the RESO Board of Directors and becomes a standard with certification requirements.

Ratified Standards

Adopted Standards

Ratified
Web API Core
Core OData 4.01 query capabilities — $filter, $select, $orderby, $expand, pagination, and metadata.
RCP-37 · v2.1.0 · Dec 2023
Read spec →
Data Dictionary
Standard field names, types, and enumerations for real estate data. Defines Property, Member, Office, Media, and more.
RCP-36/40 · v2.0 · Nov 2023
Read spec →
Web API Add/Edit
Create, update, and delete operations for RESO resources via OData POST, PATCH, and DELETE.
RCP-10 · v2.0.0 · Dec 2023
Read spec →
EntityEvent Resource and Replication
Change tracking and incremental replication using the EntityEvent resource. Enables efficient data synchronization.
RCP-27 · v2.0.2 · Dec 2023
Read spec →
Push Replication with Webhooks
Server-push replication using webhooks and the EntityEvent resource for real-time data delivery.
RCP-28 · v1.0.1 · Dec 2023
Read spec →
Validation Expressions
Machine-readable validation rules for field-level constraints, cross-field dependencies, and business logic.
RCP-19 · v1.0.0 · Dec 2023
Read spec →
RESO Common Format
Standard JSON payload format for exchanging RESO data outside of the OData protocol.
RCP-25 · v1.7 · Nov 2023
Read spec →
In Progress Proposals

Active Change Proposals

In Review
Autofill Service
RCP-22 · v1.0.0
View →
Supporting Single Feeds
RCP-35 · v1.0.0
View →
Model and Field Resources
RCP-42 · v1.0.0
View →
Local Fields and Predictability
RCP-43 · v1.0.0
View →
Metadata Internationalization and Locale
RCP-44 · v1.0.0
View →
Legacy and Deprecated Data Elements
RCP-45 · v1.0.0
View →
RelatedLookup Resource
RCP-47 · v1.0.0
View →
Add/Edit with Media
RCP-48 · v1.0.0
View →
EntityEvent Subscriptions and Filtering
RCP-49 · v1.0.0
View →
Data Provenance
RCP-50 · v1.0.0
View →
DOM Increment
RCP-51 · v1.0.0
View →
Listing Advertisement
RCP-52 · v1.0.0
View →
Resources

RCP Process

How to submit and advance a RESO Change Proposal

Versioning Policy

How RESO uses semantic versioning in specifications

Discussion Forum

Propose ideas and discuss specifications with the community

Certification & RESO Analytics

How specifications are tested and certified

Data Dictionary Wiki

Browse all standard fields, resources, and enumerations

RESO Tools

Open-source testing and reference implementation tools