Many companies offer certified RESO web API services, including MLS software provider MLS software. We asked Joseph Szurgyi (CEO at MLS Grid) and Turan Tekin (Senior Director, MLS, Industry Relations at Zillow Group, and Co-Founder and CEO of Bridge Interactive) to discuss how they are adapting their API vendors to meet the demand for holistic data feeds to brokers from MLSs.
The discussion revolved around the possibility for data producers to provide one data feed that covers all of a data consumers’ needs. This includes information about how the data will be used. WATCH VIDEO (28:03):
MLSs must provide a single data feed to participants in accordance with participant’s authorized licensed uses.
MLS must provide a single data feed to a participant at the request of the participant. This data feed can be used for the participant’s licensed uses. The single data feed may be used by the designee only to facilitate the participant’s licensed uses.
Tekin says that the policy had a tight turnaround and vendors needed to move quickly. Bridge first created a focus group consisting of representatives from the MLS, brokerage, and vendor communities. MLS Grid immediately reached out to policy decision makers to clarify expectations.
Szurgyi and Tekin agreed that when a policy has a technical integration or implementation tied to it, different trade organizations, organizations, and stakeholders should be present at the table. In an effort to increase transparency, MLS providers, downstream vendors, and NAR engagement/MLS staff have held more frequent updates over the past year.
Collaboration and communication are key to success.
The business community has responded positively to Web API services being the main way customers can access data. Not only at Bridge and MLS Grid but throughout the industry, engagement is on the rise.
Tekin stated, “Things are going really really, really well at API land.”
The Web API was not adopted quickly at first, as it was difficult to convince data providers and consumers that Real Estate Transaction Standard (RETS), was no longer viable as an API. It was necessary to coach MLSs that this data transport protocol would work better for the entire industry.
Concerns about the single feed also needed to be addressed. MLSs wanted to see how other MLSs would implement it. They wanted to be certain that their rules would still be followed in a one-feed scenario.
MLS vendors were able to guide MLS staff through this new method. These groups collaborated to reduce operational and technical costs by sharing clear plans and communicating.
A data resource was needed that included information about the display and rights for individual fields. These fields and their uses are now defined in a digital or paper license agreement.
If an MLS feed contains the BathroomsFull area, it must be noted that it can be used for both private and public display. PrivateRemarks fields are not allowed to be displayed in MLSs. These fields must be designated as private and only available to the brokerage.
These business cases can be supported by the RESO Transport Workgroup’s continued improvements to the Data Dictionary Lookup and Field Resource models.
RESO’s mission focuses on the need for a solution that is efficient for all parties involved in real estate transactions. Technical professionals will want to participate in the ongoing technical discussion on defining multiple uses within a single payload (RESO member-only content).
Data providers and consumers need to continue to engage in MLS data policy directly with Rodney Gansho (Director of Engagement) and Jason Sanchez (Director of MLS Engagement at NAR), who meet regularly with technology vendor groups.
More than 50 data consumers had already migrated to Bridge’s single feed at the time of the panel discussion. The majority of data consumers migrate to Bridge from brokers. MoxiWorks was among the first to adopt MLS Grid and they were up and running in no time with nine of MLS Grid’s MLS clients. Redfin, Compass and Compass followed shortly.
Education and documentation are essential to quality collaboration that produces results. RESO’s Web API specifications and standards are available for feedback at transport.reso.org. We are open to your participation in the development.
We get asked the most common question at RESO about Web API: “How do you get started?” Many industry professionals requested a vendor-agnostic guide in order to move customers forward. We delivered with a Web API Transformation Guide.
For technical questions, we offer support via dev@reso.org and support@reso.org.
RESO members continue finding workgroups and conferences to be the most valuable venues to unite around solutions that will benefit all. Szurgyi stated that RESO must be the voice for those in this industry. We need to be heard, and RESO should be that voice.