-
What is the RESO Web API?The RESO Web API is a standardized data access method for the real estate industry that provides a common language for software systems to exchange data. It was created to replace the older RETS standard and to modernize the way real estate data is accessed and shared. More Info on RESO Web API
-
What is the RESO Web API Core specification?
The RESO Web API Core specification outlines requirements for implementing a standardized Web API in the real estate industry to facilitate data exchange.
More Info on Web API Core
-
What technology standards does the RESO Web API use?
The RESO Web API uses RESTful principles, JSON data format and OAuth for security.
More Info on Web API Core
-
How are authentication and authorization handled in the Web API?
OAuth is used to provide secure authentication and authorization for accessing a RESO Web API service.
More Info on Web API Core
-
Where can I get test environment access to a Web API to develop my product and show its capabilities to potential partner MLSs?
The RESO Web API Developer Reference Server allows developers to access real estate listing data for testing and development purposes. The Austin Board of REALTORS® and RESO collaborate with Zillow’s Bridge Interactive API service to make this possible. Developers can access the previous year’s listing data from Austin’s Unlock MLS. It provides quick and affordable access to accurate data for developing and testing new products.
More Info on Web API Developer Reference Server
-
What is the the RESO Web API Transition Leaderboard?
The RESO Web API Transition Leaderboard tracks the progress of MLSs transitioning their customers’ data feeds from RETS to the RESO Web API. RETS (Real Estate Transaction Standard) is a deprecated, unsupported data transport protocol created over 20 years ago. The transition to the RESO Web API is essential, because it represents the industry’s shift towards a more modern and efficient data standard. MLSs not listed should contact RESO to be included in the leaderboard and refer to the Web API Transition Guide for advice.
More Info on Web API Transition Leaderboard
-
What is the purpose of the Web API Transition Guide?
The RESO Web API Transition Guide is a roadmap for transitioning MLSs from the unsupported Real Estate Transaction Standard (RETS) to a certified RESO Web API service. This transition requires significant planning and communication, and the guide provides a path forward with advice from RESO and MLS organizations that have already converted their customers to Web API It is a best practices guide that covers preparation, communication, scheduling and execution based upon the experiences of MLS industry leaders.
More info on the Web API Transition Guide
-
What technology vendors provide Web API services?
A list of vendors can be found in the appendix of the Web API Transition Guide near the end of the document.
More Info on Web API Vendors
-
Can the RESO Web API be used internationally?The RESO Web API is designed to be flexible and adaptable to different markets, including international markets with different languages. More Info on RESO Web API
-
What is the RESO Web API Add/Edit specification?The RESO Web API Add/Edit specification standardizes the methods for adding and editing real estate data through the RESO Web API. The primary goal is to ensure consistency and interoperability when adding or updating data in different real estate systems. It provides a standardized framework for data operations, reducing errors and improving the efficiency of data management processes. More Info on Web API Add/Edit
-
How are data validation rules applied in the Add/Edit proposal?
Validation rules are enforced to ensure data integrity and compliance with standardized definitions before data is accepted or updated.
More Info on Web API Add/Edit
-
What is the purpose of the Entity Events proposal?
The Entity Events specification standardizes the way events related to data entities are handled. An entity event refers to any change or occurrence that affects an entity. Standardizing entity events ensures consistent handling, tracking, and communication of changes across different systems and platforms.
More Info on EntityEvent Resource and Replication
-
What is the purpose of the Webhooks Push specification?
The Webhooks Push proposal aims to standardize how webhooks are used to push data notifications from servers to clients. A webhook is an HTTP callback that allows one system to send real-time data to another system when a specific event occurs.
More Info on Push Replication with EntityEvent and Webhooks
-
What is the purpose of the Autofill Service proposal?
The Autofill Service is designed to provide a standard method for automatically filling in forms with data stored in a user’s profile or other data sources. The Autofill Service can handle various types of data, including text, dates and structured data like addresses and payment information. By automatically filling in forms, the Autofill Service reduces the need for manual data entry, saving time and reducing errors.
More Info on Autofill Service
-
What is the Single Feed proposal?
The Single Feed proposal is about supporting single feeds for data consumers, allowing them to ingest only one feed while still accessing all necessary records and fields. It addresses the challenge of data consumers having to manage multiple feeds, such as IDX and BBO, by providing a way to consolidate these into a single data feed. The single feed must include enough information to use all relevant records and fields within the varied licenses assigned to them.
More Info on Supporting Single Feeds
-
How does RESO test the data within the property records delivered via Web API?
The Payloads 2.0 specification standardizes rules for the structure and format of the property records delivered via Web API services.
More Info on Payloads
-
What are the Model and Field resources?
The RESO Model and Field resources make server metadata easier to work with and more Data Dictionary friendly.
More Info on Model and Field Resources
-
How does RESO make integration of unique local fields with standard fields predictable and consistent?
The RESO LocalData field addresses the need for predictability and flexibility when handling local MLS data fields.
More Info on Local Fields and Predictability
-
How do RESO standards describe data and metadata in the Web API across different locales, countries and languages?
The proposal for Multiple Metadata Locales accommodates internationalization and localization needs in real estate data standards. They allow real estate systems to handle metadata in various languages and regional formats.
More Info on Metadata Internationalization and Locale
Select Page
- Home
- Knowledge Base
- Web API
- RESO Web API FAQ
