RESO Web API

What is the RESO Web API?

The RESO Web API is the modern way to transfer data in the real estate industry. It is built on well-known, open technology standards so that any organization can use it to deliver or receive data quickly and efficiently.

 

Using the RESO Web API for data transfer allows for more interoperability: systems and apps can interact with each other in a more efficient manner. Real estate professionals and consumers have access to more seamless technology experiences when all industry participants adopt the Web API in their exchanges of data.

Michaal Wurzer, RESO Vice Chair and CEO of FBS, explains the need for the industry to move forward with the transition to the RESO Web API:

The RESO Web API moves the industry forward to widely-adopted RESTful design in use by most industries today. The Web API promotes greater access to real estate information directly from the web, mobile, social and other HTTP-based applications.

RESO uses open standards and off-the-shelf tools that are supported across industries. By ensuring standards and protocols like OData and OAuth are at the core of the Web API’s functionality, industry incumbents and newcomers can be assured that they’re building technology that will be well-supported in the future. 

See RESO Web API Commonly-Used Term and Definitions

Common Questions About the Web API:

Can I get data from RESO through the Web API?

RESO does not provide MLS real estate data. RESO creates the standard for the data, and other organizations build technology based upon it. 

Brokers and technology companies should go directly to MLSs to request data via the Web API. MLSs owned and operated by REALTOR® associations are required by the National Association of REALTORS® to have production-level access available to their data via Web API.

How do I get credentials to use the Web API?

Access to data from the Web API will come from local MLSs. After agreeing to an MLS’s data use and licensing policies, data recipients will work directly with that MLS’s software provider or technical staff to receive credentials and instructions on how to access that MLS’s data.

Why Web API Instead of RETS?

RETS is an older standard that is proprietary to the real estate industry. It has been deprecated (it’s no longer being supported or improved at RESO) because the industry needs to move to a more well-known technology standard. While RETS still works for many applications, all technology evolves. RETS created great value for 20 years, and the conversion to Web API is underway.

Do You Have Other Questions?

Please email us at info@reso.org. | VISIT OUR DEVELOPER FAQ PAGE

RESO Web API Downloads

Real Estate Standards Organization
End User License Agreement

This End User License Agreement (the "EULA") is entered into by and between the Real Estate Standards Organization ("RESO") and the person or entity ("End User") that is downloading or otherwise obtaining the product associated with this EULA ("RESO Product"). This EULA governs End Users use of the RESO Product and End User agrees to the terms of this EULA by downloading or otherwise obtaining or using the RESO Product.

BACKGROUND

  1. RESO's mission is to develop and publish data standards, and software to certify compliance with those standards, for the real estate information industry that facilitate software innovation, ensure portability, eliminate redundancies, and obtain maximum efficiencies for all parties in a real estate data transaction.
  2. This EULA has been created and adopted by RESO so End Users understand their rights regarding use of RESO Products.

DEFINITIONS

  1. Definitions: For purposes of this EULA, the following terms shall have the meanings set forth below.
    1. "Intellectual Property" shall mean any and all rights under patent law, trademark law, service mark law, copyright law, trade secret law, unfair competition law, and any and all other similar proprietary rights whether under common law or federal law.
    2. "Member" means any organization or person that is a member of RESO.

All other defined terms are defined at their first use.

OWNERSHIP, LICENSE, MODIFICATION OF RESO PRODUCTS

  1. RESO owns RESO Products. Except for any Intellectual Property licensed by Members to RESO, RESO owns all Intellectual Property in RESO Products. Intellectual Property licensed by Members to RESO is owned by Members and licensed to End User subject to this EULA.
  2. Modification of RESO Products. RESO in its sole discretion may at any time modify a RESO Product for any reason or no reason.
  3. License. RESO grants End User a worldwide, royalty-free, non-exclusive license to reproduce, distribute, make derivative works of, display and otherwise exploit RESO Product solely for incorporation into End Users products or services directed toward the real estate information industry. Except as expressly provided in this EULA, End User may not reproduce, distribute, or display the RESO Product. End User may not use RESO Product to create a derivative work as a technical standard. This EULA is a non-exclusive license, and not a sale, assignment, or exclusive license. RESO retains all rights not expressly granted herein. RESO in its sole discretion shall have the power to revoke this license if End User: (1) uses any RESO trademarks without permission or outside of the scope of a trademark license granted by RESO in a separate EULA, (2) engages in illegal activities, (3) engages in, induces, or contributes to any intellectual property infringement, (4) attempts to sell or does sell the unaltered RESO Product as a standalone product or a derivative work as a technical standard, or (4) violates this EULA.
  4. No trademark license. "RESO" is a trade name of the Real Estate Standards Organization. This EULA does not provide any trademark license to End User. End User must not use RESO trademarks unless it has executed a separate trademark license with RESO.
  5. Required notices. End User shall display the RESO copyright notice on any copy, derivative work, or any other display of the RESO Product. The copyright notice must take one of the four following forms: (a) "Copyright 20XX RESO", (b) "© 20XX RESO", (c) "Copyright 20XX [End User Name]" or (d) "© 20XX [End User Name]", but options (c) and (d) may only be used if End User has created a derivative work. End User shall replace "20XX" with the current year as of January 1 of each year if a new or updated RESO Product is incorporated or End User modifies its derivative work. Additionally, End User shall display the entire text of this EULA and the following notice: "This document includes works developed by RESO, subject to the RESO End User License Agreement published at www.reso.org." Any software application developed by End User based upon the RESO Products shall include the following notice in its end user documentation and in its codes: "This software product includes software or other works developed by RESO, subject to the RESO End User License published at www.reso.org."

END USER OBLIGATIONS

  1. No claims. End User agrees that it will not bring any infringement claims based on RESO Product against Members or other End Users for any Intellectual Property End User claims to own that may be included in the RESO Product.
  2. Indemnification. If End User creates a derivative work or implements the RESO product in such a way that it becomes allegedly infringing, End User agrees to indemnify and hold RESO and Members harmless with respect to any, actions, liability, laws, expenses or legal fees arising from such alleged infringement. RESO or Member shall have the right to participate in the defense and settlement of any action under this section using its own counsel and at its own cost.
  3. Sole Recourse. End User agrees that End Users sole recourse in the event of any claim, loss, injury, damages, fees, cost, expense, complaint or liability concerning the Stated Subject Matter is to and against only RESO and not to or against any Covered Person nor to or against any other company or person. The "Stated Subject Matter" means any RESO Product, this Agreement and any subject matter of, or any acts or omissions under or arising from, this Agreement. "Covered Person" means any member, licensor, service provider, supplier or contractor of RESO (whether retained by RESO or otherwise involved in the design, development, assembly, offering, marketing, sale, promotion, provision, delivery, support, accessibility, use, quality, performance or availability of any of the Stated Subject Matter). End User agrees to in no event threaten or assert any claim or action against any Covered Person regarding any of the Stated Subject Matter. End User also agrees that each Covered Person shall be entitled to the benefit and protection of any provision of this Agreement that disclaims, excludes, qualifies or limits express or implied warranties, representations, guarantees, promises, remedies, liability or other responsibility to End User or others. End User further agrees that each Covered Person has the right to directly enforce such provisions, and this paragraph, although RESO reserves the right (as between End User and RESO) to also enforce such provisions on behalf of any Covered Person. End User agrees to indemnify RESO and each Covered Person from all claims, losses, injuries, damages, fees, costs, expenses, complaints and liabilities incurred or required as a result of a breach by End User of any of the terms of this paragraph. Each reference in this paragraph to a Covered Person or any other company or person shall be construed broadly and shall include also any affiliate of any of them and any director, officer, equity owner, employee or representative of any of them or of any such affiliate. THIS PARAGRAPH APPLIES NOTWITHSTANDING ANY OTHER PROVISION OF THIS AGREEMENT.

DISCLAIMERS; LIMITATIONS OF LIABILITY

  1. Disclaimer of warranties; limitation of liability. IN NO EVENT SHALL RESO BE LIABLE TO END USER FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER ARISING FROM ANY BREACH OF THIS EULA, EVEN IF RESO HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. RESO PRODUCTS ARE PROVIDED "AS IS." RESO AND MEMBERS MAKE NO REPRESENTATIONS OR WARRANTIES EXPRESS OR IMPLIED. RESO AND MEMBERS DISCLAIM ALL REPRESENTATIONS AND WARRANTIES INCLUDING BUT NOT LIMITED TO THOSE OF MERCHANTABILITY, TITLE, AVAILABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT, EXCEPT THOSE EXPRESSLY SET FORTH IN THIS AGREEMENT. THIS PARAGRAPH SETS OUT END USERS EXCLUSIVE REMEDIES, AND UNDER NO CIRCUMSTANCES SHALL MEMBER OR END USER BE ENTITLED TO EQUITABLE REMEDIES.

GENERAL TERMS

  1. Survival. Sections 7 through 18 shall survive termination of this EULA.
  2. Dispute resolution. The laws of the State of Illinois shall govern this EULA and its interpretation. Any action to enforce or interpret this EULA shall have venue in Cook County, Illinois, and the parties hereby submit to personal jurisdiction in that venue.
  3. Severability. Each provision of this EULA is severable from the whole, and if one provision is declared invalid, the other provisions shall remain in full force and effect. In the event a court having jurisdiction over the parties holds any provision of this EULA invalid or unenforceable, the parties shall negotiate in good faith to replace the invalid or unenforceable provision, if possible, with a valid provision that most closely approximates the intent and economic effect of the invalid provision. If any provision of the limitation of liability or exclusion of warranty is held invalid or unenforceable, this EULA shall immediately terminate unless the parties agree to the contrary.
  4. Entire EULA. This EULA contains the full and complete understanding of the parties regarding the subject matter of this EULA and supersedes all prior representations and understandings, whether oral or written, relating to the same subject matter.
  5. No third party beneficiaries. There are no third party beneficiaries of this EULA.
  6. Relationship of the Parties. The relationship of RESO to End User is that of independent contractor. No party shall be deemed to be the agent, partner, joint venturer, franchisor or franchisee, or employee of RESO or have any authority to make any agreements or representations on the behalf of RESO.
  7. E-notices. All notices, disclosures, and other communications made between RESO and End User electronically satisfy any legal requirement that such communications be in writing.
  8. No waiver. Failure of RESO to enforce any provision of this EULA shall not be deemed a waiver of future enforcement of that or any other provision.

Contact for notices and operations matters:

Name: Sam DeBord
Address: RESO
PO Box 10824
Raleigh, NC 27605
Phone: 919.504.9898
Email: sam@reso.org

With a copy to:

Name: Mitch Skinner
Address: Larson Skinner PLLC
2701 University Ave. SE #201
Minneapolis, MN 55414
Phone: 612.424.6775
Email: mskinner@larsonskinner.com

Previous Versions

RESO Web API Version 1.0.1
RESO Web API Version 1.0.2

Commonly-Used RESO Web API Terms:

API is short for Application Programming Interface. In a nontechnical sense, you can think of it as the panel on the back of a TV with ports and jacks to input and output media. It’s a set of standardized ways for technology systems to interact with each other. An API is an interface for access and delivery of data.

Authorization identifies what kinds of data a user is allowed to access. To access data through an API, a data requestor supplies an authorization code – an API key or API token – and the user’s allowed level of data access is delivered through the API.

Authentication identifies who is requesting data. An API needs to authenticate who is requesting data and identify which data they’re authorized to access.

Endpoint is a web address where data can be accessed. An API service may have one or many endpoints where different kinds of data can be accessed.

HTTP is Hypertext Transfer Protocol. It is the set of rules for transferring data between systems on the World Wide Web or within a network.

JSON is a way to represent data that is simple for humans and machines to interpret. RESO’s Web API can return data to requestors in this format for ease of use.

OAuth is an open standard that allows for authentication and authorization in one step. It allows previously-identified users of systems (think Facebook and Google accounts) to log in to other APIs and get access to services quickly.

OData is a protocol, or system of rules, for building an API and for transferring data through an API. RESO uses the OData V4 standard specification.

Metadata is “data about the data.” It is a user guide to explain what data is available and how it is organized. Metadata can be analyzed so that data requestors understand exactly what the data they access from an API will look like.

Payload is a set of data which has a predetermined structure. An “IDX Payload” would include all of the fields needed for display on a real estate IDX website in a structured format that can be understood and easily consumed by the data recipient.

Protocol is a defined system, process or set of rules.

Query is a request a user makes to an API explaining what kind of data is needed. The RESO Web API can handle “live queries” that allow for immediate results in web applications.

Replication is the copying of a database. Replicators initially pull an entire data set, and then continually request the most recent data changes to update their copy and keep it in sync with the primary database.

REST is REpresentational State Transfer. It is a design for creating an API to efficiently communicate between systems. REST APIs, like the RESO Web API, use RESTful HTTP (web-based) requests to input, update, delete or get data through the API.

DLU January 21st, 2020