Select Page

RESO FAQ

RETS 1x

RESO’s first standard products used the term RETS (Real Estate Transaction Standards) as a prefix to its version number (i.e. RETS version 1.5 through 1.9) All of these versions all collectively known as RETS 1x. RESO will continue to use “RETS” as a prefix for its original standard product but will not do so for products such as Data Dictionary. RETS provided an open specification for how to describe, transfer, and update real estate data, and many vendors are still using it today.

DLU March 6th, 2019
Category: RETS 1x

The RETS Workgroup has been sunset as of April 2017, RESO will no longer be providing future versions of the RETS standard and the RETS v1.9 standard will be the last version of the RETS Standard released. RESO will also be discontinuing RETS Certification Services and issuing of RETS Certifications for Server and Clients as of July 1st, 2018. The real estate industry will continue to utilize the RETS Standard. RESO has released the RESO Web API standard as the latest standard for distributing real estate data. It is encouraged for MLSs, Brokers and Technology Partners to consider migrating over to the RESO Web API for the features and functions it provides above and beyond the RETS Standard, including supporting a mobile environment, a lightweight based JSON output, authentication through the OpenID Connect and OAuth2 global technology standards and OData for accessing and distributing data that is also a global technology standard for the transmittal of data.

DLU June 8th, 2018
Category: RETS 1x

RETS did not contain any specifications for a specific schema. Rather, it was designed to work dynamically given the Vendor’s metadata. Therefore, each RETS 1.x server instance (e.g. an MLS) can generate a number of RESO-compliant schemas based on its own needs via a Get Payload command.

DLU March 6th, 2019
Category: RETS 1x

RETS 1x security is handled at three levels: user, client, and data. User authentication, though not strictly mandatory in the specification, is handled through a login transaction which establishes a RETS 1x session for subsequent data interchange. Client application program authentication is also specified and is based on various industry standards. Data security, though not strictly part of the RETS 1x standard, is recommended through the use of appropriate transport protocols to ensure data content encryption & authentication (i.e. HTTPS/SSL).

DLU February 11th, 2018
Category: RETS 1x

RETS Specifications

DLU February 11th, 2018
Category: RETS 1x

Load More

DLU June 28th, 2018