Trestle
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.
*Please be advised that CoreLogic is switching the Trestle™ API URL to a new URL
Old: https://api-prod.corelogic.com
New: https://api-trestle.corelogic.com
The Old URL will continue to work until February 6th 2024.
https://api-trestle.corelogic.com
We
are happy to announce the release of Data Dictionary 2.0. With this release
Trestle systems will be RESO 2.0 certified, which means that you will have a
dramatic improvement in standardization coverage. Trestle offers a single
schema, delivering consistency to our users across every MLS. As such, you will
see as this change rolled out to all customers at the same time. There are a
few new features that you can take advantage of with this update, but in
general, your biggest concern should be making sure that your fully replicated
datasets are up to date.
When: Monday, Sept
30th 6AM EST - 12PM EST
What
to expect
- On
Release, you will see the new enumeration values in the metadata.
- A data
refresh will occur in reverse order, correcting newer records first.
- We
will only touch ModificationTimestamp
for On-Market Listings.
- All rows
going forward include the new values.
- The entire
dataset will be updated over the next two weeks.
Reference
“What to Do” below for details.
What to Do
Review Changes:
- If you
consume these fields as is, you may not need to make a change.
- If you are
using enumeration values in your code or have complex mapping, you will
need to review.
- Most users
do not search on these fields.
Be prepared to update a lot of rows:
- We expect
over 200m row updates across all resources.
- Most of
our users are conditioned to the fast pace of our updates and will have no
issues consuming data at the rate that we provide it.
- If you
need additional quota, please reach out or upgrade to our Premium Quotas
for a permanent boost.
- We will
only touch ModificationTimestamp for On-Market Listings.
- You should
repull off market data in a few weeks. We will send a reminder when all
accounts have been refreshed.
Metadata changes:
- Check for
changes in namespace.
- Check for
changes in your internal references (are you mapping an enum to another enum?).
- Consider
moving to Lookup/Field resource.
Major Changes
CoreLogic's CLIP is now available:
- CLIP
(CoreLogic Integrated Property) is a Machine Learning driven record
identifier based on CoreLogic assets. Use it to uniquely identify a
property across vast datasets.
- Interested
in additional datasets that you can use with CLIP? Ask us about our
collection.
UPI is now available:
- UPI is a
Universal Parcel Identifier for each listing based on the concatenation
for other values. Lean more about UPI at
City / County lookups:
- Data type
is being changed from a String to a Lookup
- You will
see case changes but should not see any value changes at this time.
- You can
find references to the available Lookup values in the lookup resource.
- Over time,
we will continue to standardize these values.
CustomFields json blob:
- This field
is being converted into a stringified JSON.
- If you
rely on this field (the blob), please let us know as we are considering
deprecation in favor of a more standard approach.
Data Type Changes:
- Some
strings were made enumerations and vice versa.
- See our
field change documentation.
New Field & Lookup Resources:
- You can use
these resources for determining available lookup values.
- You can
filter this for a specific MLS.
Metadata is much larger:
- RESO
certification requires that Enumerated fields must have all values in the
metadata.
- If large
Metadata files are a concern, use the Lookup Resource.
New field type of Lookup:
- Fields
like PostalCity, CountyOrParish
will be exposed as a string, with a reference to the Lookup Resource.
- You can
use the Lookup resource to find available values for Lookup fields and
enumerations.
Massive enumeration value changes
- RESO 2.0
testing enforces parity between a payload and the enumeration/lookup.
- The most
common fields:
- ListAOR
- ListAgentAOR
- ListOfficeAOR
- BuyerAgentAOR
- BuyerOfficeAOR
- BuyerFinancing
- Possession
- LeaseTerm
- MediaType
- See our
field change documentation.
Review Field & Lookup Change Document
Recent Changes
Content Patch
Sep 30, 2024
Content Patch #177
Content Patch #177 adds 26 new fields and 56 new lookup values and removed 9 lookup values and 4 fields, with 21 field changes and 1068 lookup replacements across multiple resources.
Content Patch
Aug 21, 2024
Content Patch #176
Content Patch #176 adds 15 new fields and 74 new lookup values.
Content Patch
June 17, 2024
Content Patch #174
Content Patch #174 adds 1 new resource, 46 new fields, and 129 new lookup values.
Content Patch
May 13, 2024
Content Patch #173
Content Patch #173 adds 1 new field, 7 field changes, 2 removed fields, and 72 new lookup values.
Content Patch
April 11, 2024
Content Patch #172
Content Patch #172 adds 27 new lookup values and 0 new fields.
Content Patch
March 11, 2024
Content Patch #171
Content Patch #171 adds 16 new lookup values and 0 new fields.
Content Patch
February 20, 2024
Content Patch #170
Content Patch #170 This content patch added 3 new resources, 251 new fields and 510 newlookup values and removed 14 lookup values and 5 fields across multiple resources.
Content Patch
August 30, 2023
Content Patch #169
Content Patch #169 adds 29 new lookup values and 0 new fields.
Content Patch
August 2, 2023
Content Patch #168
Content Patch #168 adds 5 new lookup values and 16 new fields.
Content Patch
June 26, 2023
Content Patch #167
Content Patch #167 adds 5 new lookup values and 0 new fields.
Content Patch
May 18, 2023
Content Patch #166
Content Patch #166 adds 17 new lookup values and 0 new fields.
Content Patch
April 6, 2023
Content Patch #165
Content Patch #165 adds 27 new and removes 2 lookup values.
Content Patch
February 13, 2023
Content Patch #164
Content Patch #164 adds 5 new and removes 2 test lookup values.
Content Patch
June 28, 2022
Content Patch #159
Content Patch #159 adds 12 new lookup values and 0 new fields.
Content Patch
May 19, 2022
Content Patch #158
Content Patch #158 adds 27 new lookup values and 0 new fields.
Content Patch
March 24, 2022
Content Patch #157
Content Patch #157 adds 30 new lookup values and 0 new fields..
Content Patch
February 24, 2022
Content Patch #156
Content Patch #156 adds 121 new lookup values and 6 new fields.
Content Patch
November 18, 2021
Content Patch #155
Content Patch #155 adds 144 new lookup values and 17 new fields. Lookups will be live November 24.
Content Patch
October 28, 2021
Content Patch #154
Content Patch #154 adds 23 new lookup values and 4 new fields.
Content Patch
September 29, 2021
Content Patch #153
Content Patch #153 adds 75 new lookup values and 0 new fields.
Content Patch
September 1, 2021
Content Patch #152
Content Patch #152 adds 99 new lookup values and two new fields to the Property resource.
Content Patch
July 14, 2021
Content Patch #151
Content Patch #151 adds 25 new lookup values. There are no new fields with this patch.
Release
June 22, 2021
Trestle 5.20
Trestle Version 5.20 adds single sign-on and "contractless" connections to broker accounts.
Content Patch
June 3, 2021
Content Patch #150
Content Patch #150 adds 31 new lookup values. There are no new fields with this patch.
Previous Changes
Notice
May 2021
Data Maintenance Notice
Notice: Trestle will be undergoing aggressive data maintenance over the next few weeks
Content Patch
May 4, 2021
Content Patch #149
Content Patch #149 adds 32 new lookup values. There are no new fields with this patch.
Content Patch
April 22, 2021
Content Patch #148
Content Patch #148 adds 36 new lookup values and two new fields.
Release
April 6, 2021
Trestle 5.18
Trestle Version 5.18 adds a session timeout alert to the dashboard as well as some bugfixes.
Content Patch
February 18-19, 2021
Content Patch #146
Content Patch #146 adds several new lookup values, and a new field to pass through the MLS’s original Security Class on the Member resource.
Content Patch
February 4-8, 2021
Content Patch #145
Content Patch #145 adds several new lookup values, and new fields to the Property resource for additional branded and unbranded virtual tour URLs.
Release
February 3, 2021
Trestle 5.12
Trestle Version 5.12 adds the new Connections and Contracts Report. It enables you to query for connections by inception data and contracts by execution date.
Release
January 20, 2021
Trestle 5.11
Trestle Version 5.11 adds a new flag field HumanModifiedYN
to all 10 MLS data resources to indicate if the record was changed by an actual live person.
Content Patch
January 13-20, 2021
Content Patch #144
Content Patch #144 adds several enumerations, and one new field to all resources: HumanModifiedYN
.
Content Patch
December 16, 2020
Content Patch #143
Content Patch #143 adds one field to Member. It adds and updates a number of list values (you’ll see a Remove and a New for the renames).
Release
December 9, 2020
Trestle 5.9
Trestle Version 5.9 adds support for nested OData string functions in $filter
s.
Release
November 17-18, 2020
Trestle 5.8
Trestle Version 5.8 improves the user experience for MLOs and TPs on the dashboard. It provides OData-compliant error messages and more $expand
options for WebAPI.
Content Patch
November 11, 2020
Content Patch #142
Content Patch #142 adds the Teams and TeamMembers resources. Two new Teams-related lookups are included: TeamStatus
and TeamImpersonationLevel
. As with any new resource, population will start low and increase as mappings are updated. This patch also adds a number of new lookup values.
Content Patch
October 14, 2020
Content Patch #141
Content Patch #141 adds 316 new lookup values across 61 lookups. It also adds the UpstreamYN
field to the Member resource.
Release
August 27, 2020
Trestle 5.4
Trestle Version 5.4 primarily addresses two issues with WebAPI. Specifying a $top greater than 300,000 now for an "InKeyIndex" query now correctly returns an error and PrettyEnums=true now works across $expand.
Content Patch
August 27, 2020
Content Patch #140
Content Patch #140 adds new lookup values only. There are no field changes.
Content Patch
August 7, 2020
Content Patch #139
Content Patch #139 completes the Public Record data set by adding Building, Site, and TaxAssessment resources.
Content Patch
July 17, 2020
Content Patch #138
Content Patch #138 adds 11 fields to the PropertyUnitTypes resource and adds 52 new lookup values.