Trestle provides real estate data delivered via WebAPI and RETS. We aim to help you write your first WebAPI client, configure a RETS library to work with Trestle, or scale your solution to meet the demands of aggregating multiple MLSs. If there are questions left unanswered, you may reach out to us via email or phone (844) 530-8855. You can also request to join our support slack if you are not already on there.
May 7, 2020
Content Patch #136 adds three new Public Records resources: Prior Sale, Ownership,and Ownership Transfer. We are also adding one field to CustomProperty (MembershipFeeFrequency, and its new lookup called FeeFrequency), and updating values in many lookups. We are deleting one lookup value (BuyerFinancing.LeasePurchase, seen as a duplicate of “Lease” in that lookup list).
April 20, 2020
CoreLogic is excited to announce the release of Trestle Version 5.0! This marks the next step of Trestle’s evolution toward being the industry’s leading distribution platform for all kinds of Real Estate and Property related data.
In partnership with CoreLogic’s Smart Data Platform team, Trestle now offers two internal CoreLogic products: CLIP™ and Public Record Data. In addition, our new developer’s API documentation website brings a whole new level of support to Trestle’s data consumer customers.
Content Patch #135 updates the metadata and content payloads in sync with the release of Trestle 5.0, which contains the first piece Trestle’s new Public Record Data offering. Public Records will be announced more fully in the next several days, as part of the upcoming Trestle 5.0 release.
Access to Public Record Data will be managed, contracted, and billed through our sales organization—more detail about that will be in the 5.0 release announcement.
This patch includes the resources PropertySearch and LastMarketSale. No changes are made to any existing resources. The remaining Public Records resources will be coming over the next several content patches.
The Public Record resources are in a separate OData schema from the MLS data. They will not at this time be exposed for RETS access, nor be visible in the RETS metadata. Also notice that the field name capitalization conventions are different from those used in the MLS dataset (camelCase versus PascalCase).