Two transport APIs enable solutions to connect, request, and consume data feeds. The mechanisms are:
➢ The WebAPI, a RESTful API based on the Real Estate Standards Organization’s (RESO) WebAPI
1.0.2 specification and OData 4.0
➢ The RESO Real Estate Transaction Standard (RETS) API, an older API based on the RESO RETS 1.8
Both transport mechanisms return data based upon RESO Data Dictionary 1.5 schema specification at the
time of this publication. Support for 1.6 and future versions will be included as the standards evolve, and
new versions are ratified by RESO.
Rather than provide extensive documentation for these standards directly herein, Technology Providers
are encouraged to review the documentation directly on the RESO site; a great deal of time and care has
gone into the creation of these standards, and the support information regarding their purpose and use is
best viewed at the source.
➢ WebAPI v. 1.0.2 documentation: https://www.reso.org/reso-web-api/
➢ RETS 1.8 documentation: https://www.reso.org/specifications/
➢ RESO Data Dictionary documentation: https://www.reso.org/data-dictionary/
Both transport mechanisms require client software to connect, authenticate, and query the underlying
Trestle data sources. There are multiple clients available for download for free or for a license fee; further,
reference implementations and documentation can be found on reso.org if you choose to develop your
own client. CoreLogic recommends RETS Connector (http://retsconnector.com) for use with the RETS API.
If you are a new vendor and require a RETS connector tool, please go to http://www.retsconnector.com/ to download the CoreLogic RETS connector tool. The server link will not work without a connector tool.
If you are a new vendor and require an API tool, please go to https://www.getpostman.com/apps to download the Postman API tool. The server link will not work without an API tool. Additional instructions on how to access your API feed can be found at https://docs-trestle.corelogic.com/GettingStarted/WebAPI.