Frequently Asked Questions
What Is Trestle
What is Trestle™ by CoreLogic®?
Trestle is a real estate data distribution platform. It aggregates and normalizes data from disparate sources, automates the data licensing process, and provides fast and standardized programmatic data interfaces.
What sort of data is available?
Trestle is a central marketplace from which you can license and access a broad range of real estate data.
Today, Trestle has listing and membership data from over 90 multiple listing organizations (MLOs) across North America. Trestle also offers CoreLogic’s own public record and tax data. We plan to add more CoreLogic, third-party, and multiple listing data sets in the future.
Trestle standardizes listing data per the Real Estate Standards Organization (RESO) Data Dictionary specification. Trestle transforms data from each MLO into a consistent data structure, saving you the effort of understanding and translating each MLO’s data individually. Trestle is Platinum Certified by RESO for Data Dictionary 1.7.
How do I access the data?
Trestle supports two methods of data access:
Web API – a modern, OData-based RESTful interface created by RESO. Web API is appropriate for both real-time data access (responding to live user activity) and for data replication processes where some or all the data is downloaded to your application. Trestle is RESO Platinum Certified for Web API 1.0.3.
RETS – a legacy query and response framework created by RESO more than 20 years ago. Existing data applications might already use RETS, in which case ingesting Trestle data via RETS could make the most sense. RETS is designed for data replication and is not suitable for real-time access.
How does data licensing work?
Trestle automates the data licensing process between data consumers and copyright holders. In the case of multiple listing data, the MLO is the copyright holder and data licensor. Trestle only facilitates the license agreement between you and the MLO; CoreLogic is not a party to the agreement.
When a Trestle data consumer requests a new data connection with an MLO, the Trestle dashboard walks them through setting up an e-signing contract to collect signatures from all parties and authorize the billing of the MLO’s license fee.
IMPORTANT NOTE: Generally, MLOs license data to technology providers that provide value to their membership. As a result, MLOs typically require a real estate broker or agent to ratify the contract or require the technology provider to submit a periodic report that shows which members are using its service. MLOs typically disallow certain uses of their data, such as marketing to their members. It is very unlikely that an MLO will license data to a company that does not intend to use it to provide a value-added service back to its members.
What does it cost?
For MLO data feeds, there are usually two separate charges for each connection:
- A Trestle platform fee of $85/month
- An MLO license fee, which varies greatly by market and may be charged monthly, quarterly, or annually
You can view the fees associated with a particular data connection before activating it. These two types of fees are automatically charged to the credit card you put on file when you opened your Trestle account.
Other data assets—such as CoreLogic’s public record data—are charged a custom rate depending on the areas you license and your intended usage. Please contact email@example.com to learn more about these additional data assets.
How can I get help?
CoreLogic offers technical support by phone, email, and Slack. Contact TrestleSupport@corelogic.com to request your own Slack channel—this gives you real-time access to Trestle developers and data engineers who can help with most issues.
How do I get started?
Register for an account at https://trestle.corelogic.com. Follow the steps to create a Technology Provider account (or Broker account if appropriate). Then click “ADD MLO CONNECTION” to begin the data request workflow.
Working With Trestle
How can I increase my quota?
If you are running into
429 Quota Exceeded messages, there are a couple of things to check. First, make sure you are following our best practices for quota management. Second, look at the response content for a value
Hour-Quota-Available. If that value is NOT zero, then you are hitting the per-minute quota. You may need to adjust your rate limiting to accommodate your per-minute quota.
If you have followed the above steps and are still running into quota issues, please reach out to Dan Ray, the principal product manager for Trestle.
How long does it take for data to update in Trestle?
We strive to keep the data as fresh as possible in Trestle. For us, that means that listing data, agent data, etc. should be updated within 5 minutes of it being changed in the source MLS, and that images should be updated within 15 minutes.
Why is there a delay in listings and/or media showing up?
Trestle aggregates and standardizes listing and media data from over 100 MLSs. As part of that process, we can run into delays if we have a massive update from one or more larger MLSs that consumes a disproportionate amount of our processing capacity.
Why do I keep getting a 504 error when trying to pull data?
A 504 Gateway Timeout error means that your request took too long. When you encounter this issue, the best thing you can do is to first try the request again. If you are consistently getting 504 errors, then please report the issue to Trestle Support, including the full request you're making.
Why is there a discrepancy in counts between the MLS/Matrix and Trestle?
There are a couple of different reasons why you might see a discrepansy between the counts in the MLS/Matrix and Trestle. The first possibility is that the MLS/Matrix source is a regional MLS comprising multiple MLSs, e.g. SWFL includes data from Ft. Myers, Roayl Palms, Naples, and Bonita, but your connection in Trestle might only be for one or two of the MLSs. The second possibility is there might be differences in which statuses and which listings in those statuses you can access. For example, if you have an IDX feed, you will not have access to sold listings, whereas if you have an IDX Plus feed, you will have access to some of them.
Should I use ListingId or ListingKey, as an identifier?
ListingId is the value that agents will be familiar with, so it is the recommended value for displaying. However, it is not guaranteed to be unique across MLSs, so for identifying the record in a database or across Trestle, we recommend using ListingKey.
How can I have the data display with spaces?
Our enumerations follow OData standards, which means they are displayed without spaces. We do provide an extension PrettyEnums=true that will provide the enumerations with spaces in them.
Can I use the same credentials for all of my feeds?
Your credentials are tied to a specific product/feed type. So if your product Joe's Pretty Good IDX has an IDX feed and and IDX Plus feed, they will require two separate credentials. However, if you have multiple IDX feeds set up for multiple MLSs, then all of that data will come with one set of credentials.
How can I get another feed type added for an MLS that I already work with?
In order to create another feed type or replace an existing feed type, you will need to set up a new connection with the MLS through the Trestle Dashboard. Because Trestle feeds are associated with contracts and because those contracts specify the feed type, we cannot simply switch your feed type.
What is CLIP and how does it relate to RESO's UPID?
Technically speaking, CLIP is a 10-digit numeric value that uniquely identifies real properties. It is complimentry to RESO's UPID and Trestle supports both. Within Trestle, CLIP allows you to join MLS records to public records and other data from CoreLogic.