CoreLogic Trestle is the platform many MLSs use to distribute their RESO certified feed. It issues two values, a Client ID and a Client Secret, and MLSImport exchanges that pair for an access token on every request.
Trestle feeds are usually requested by the broker rather than the agent, and the client secret expires on a schedule. Both facts cause more support tickets than the setup itself.
Before you start
- Confirm your MLS distributes through Trestle. Check the Web API Server line on your MLS entry at the RESO certification directory.
- Check who may request it. Several MLSs, CRMLS among them, accept feed requests from brokers only. An agent request on those boards goes nowhere.
- Have a data licensing agreement in place. Most MLSs require the broker to sign one before Trestle will process a subscription.
Requesting the feed
- Complete the data licensing agreement with your MLS. This covers permitted use and compliance with their rules.
- Open the Trestle Subscription Wizard and choose the option matching your role, in most cases Broker.
- Describe how the data will be used. MLSs commonly require this and reject blank or vague answers.
- Choose Web API as the delivery method where the wizard offers a choice.
- Submit and wait for the connection to be approved by your MLS.
Expected result: the subscription shows delivery as Web API and status as approved, and your Trestle account lists a client ID and a client secret.
Feed allowances are set per MLS, not by Trestle. Some boards include a number of feeds for their brokers and charge a monthly service fee beyond that, and some charge per website URL served. Ask your MLS what your account includes before you request a second feed.
Entering the credentials
- In WordPress, open MLS Import Settings and select your MLS in the Your MLS search.
- Paste the client ID into Your Trestle Client ID – provided by your MLS.
- Paste the client secret into Your Trestle Client Secret – provided by your MLS.
- Save, then run the connection test.
The token field used by Bridge and Spark markets stays hidden for a Trestle MLS. If you see it instead of the two Trestle fields, the MLS you selected is not the Trestle one.
When a working connection suddenly fails
This is the most frequent Trestle ticket. Imports ran for months, then stopped, and the MLS connection is no longer green. Nothing changed in WordPress.
Trestle rotates client secrets periodically and emails a notice before the old one expires. When it lapses, the connection test fails with the message about checking the authentication token and the data access application. The fix is on the Trestle side.
- Sign in to Trestle and copy the current client secret. Trestle support can reissue it if you cannot find it.
- Paste the new secret into Your Trestle Client Secret – provided by your MLS in MLS Import Settings and save.
- Run the connection test again. Saving clears the previous result, so a re-test is always required.
The client ID normally survives a rotation. It is the secret that expires. If someone tells you they have “the ID and the token”, confirm they have both values and that the second one is the freshly issued secret, not the one from the original approval email.
Two things worth knowing about Trestle feeds
Some MLSs publish through both Trestle and another platform, and the feeds are not identical. Miami through Trestle does not carry latitude and longitude, while Miami through Bridge does. If map search matters to your site, ask which fields your feed includes before choosing the platform.
Realcomp is a separate server that reuses the same two fields in the plugin. If your MLS is Realcomp, entering the credentials in the Trestle labelled boxes is correct.
Frequently asked questions
Can an agent request a Trestle feed?
It depends on the MLS. Some route agents to a different platform and reserve Trestle for brokerages, so the answer comes from your MLS rather than from Trestle. Ask them which platform your role applies through before starting a subscription.
Does MLSImport sign as my vendor in Trestle?
No. The data relationship is between the broker and the MLS through CoreLogic. We do not sign as a vendor, do not request the feed, and do not manage your MLS data. We connect to the feed you already have.
Trestle asks for a description of intended use. What do I write?
Describe the site plainly: a public real estate website displaying listings under your brokerage, built on WordPress, pulling listings through the Web API. Applications that leave this blank or vague are frequently sent back.
How long does Trestle approval take?
The Trestle steps themselves are quick. The wait comes from your MLS reviewing and approving the connection, which is manual and varies by board. If it has been more than a week with no movement, ask your MLS what is outstanding.
Related
- What RESO Web API access is and why you need it
- Rapattoni, Paragon, ConnectMLS and Realcomp
- MLS approval processes that take time
- Verifying your MLS connection
If your Trestle subscription is approved and the connection test still fails, send us the MLS name and we will check the response from the server.