RETS has been a solid technology standard for 15 years, and many vendors are resistant to make the change to API. But as the needs of mobile shift the industry, a new “interstate” is necessary. Jeremy Crawford, CEO of RESO, discussed the details of this controversial pivot with Greg Robertson for his “Listing Bits” podcast.
RESO is responsible for the creation, promotion and adoption of standards in the real estate industry, seeking to fuel innovation and help streamline the real estate transaction. Crawford has been involved with RESO since 2010, serving on its Board of Directors and co-leading the Education and Outreach Workgroup. He has a unique combination of talent and experience, with an extensive background in information technology and corporate management.
Crawford explains the need for a pivot away from RETS to API, the benefits of saved search portability and the progress of the transition to date. Listen to the full interview to understand the steps being taken to improve the permissioning process and who might play a role in further advances.
What’s discussed:
The controversial pivot to API
– Resistance from traditional vendors
– Interstate analogy (on and off ramps)
– Shifting needs require API
– Parallel uses of both RETS and API likely
The progress of the move to API
– Distribution piece complete
– Updates component under development
The vendors who are taking advantage of API capabilities
The benefits of switching to API for established vendors
– API built to access data on the fly
– Can still replicate data, but have option not to
– Saved search portability
Progress with regard to the challenges of permissioning
– Standardized data licensing agreements
– NAR turnaround time policy for IDX access
– Access to developmental data feeds to facilitate product development
Who is responsible for permissioning process
– RESO R&D Workgroup drafting best practices
– Brokers must help shepherd process along
