CRMLS sends its RESO feed through Trestle. We sync it into your WordPress, Laravel or custom site, follow the CRMLS IDX rules, and keep it current every 2 to 3 hours.
POST /oidc/connect/token client_credentialsGET /Property?replication=true@odata.nextLink$filter=ModificationTimestamp gt {last}Media ordered by OrderMost CRMLS brokers start with a framed link or a plugin, then get quoted a full rebuild to move past it. The feed itself is not the hard part. The sync, the solds, the listing credit rules and the photos are. We have synced this board's feed before, on a multi MLS platform we built and ran from 2018 to 2025.
CRMLS, the California Regional Multiple Listing Service, is a subscriber based MLS covering much of California. It says it serves more than 93,000 real estate professionals from 39 associations, boards and MLS organizations.
Its subscribers work in CRMLS Matrix, Paragon and Flexmls, and log in through the REcore dashboard. For data, CRMLS offers framed IDX links, licensed IDX vendors, and raw RESO feeds through Trestle.
For a broker who wants listings inside their own site, the Trestle feed is the one that matters. It hands over the data. Getting it onto your pages, with the CRMLS display rules, is the work.
The board decides which platform carries its feed. Each route has its own login, paging and limits, and its own page here.
CRMLS lists three IDX options. The raw feed goes through Trestle, and the request starts with you or your developer.
CRMLS offers IDX Standard and IDX Plus framed links, licensed IDX vendors, and a RESO certified feed through Trestle. A feed into your own site is the third.
CRMLS asks for your Matrix ID and Office ID, plus its IDX Request Form when you work with a licensed vendor.
You or your developer sign up for Trestle and request a connection to CRMLS in the Subscription Wizard, describing how the data will be used.
CRMLS treats a request from a developer or a new IDX vendor as a general IDX vendor request, and the Trestle and per URL fees fall to the developer.
Once the connection is approved, Trestle issues the client ID and secret. The sync is checked against the feed before your pages switch.
Through Trestle the feed follows the RESO Data Dictionary. CRMLS decides which statuses and fields your licence includes.
01Property records for Active, Active Under Contract and Pending listings, as CRMLS describes its IDX data.
02CRMLS includes Sold listings from 2012 onward in IDX data. They sync on their own schedule.
03Member, Office and OpenHouse resources through Trestle, where your licence includes them.
04A Media resource with a URL per photo, tracked on PhotosChangeTimestamp so photos only move when they change.
05ModificationTimestamp for regular pulls, and Trestle's replication endpoint for full loads.
06Changes do not show what left the feed. A daily purge compares listing keys, with a minimum count check that blocks a bad purge.
Taken from the board's own published rules and data pages, listed under Sources above. The audit confirms the current version before anything is built.
CRMLS says its IDX data covers Active, Active Under Contract and Pending listings, plus Sold listings from 2012 on. Each status gets its own rules in the sync.
CRMLS keeps agent remarks and showing instructions out of IDX. The sync never stores them for public pages.
CRMLS publishes IDX Standards of Practice and listing credit guidance. The disclaimer and listing credit are set per board, with the last updated time shown.
CRMLS lists a Trestle fee for each IDX feed and a small monthly fee per website URL after the first two. The audit checks which ones your setup triggers.
Many CRMLS brokers start on a framed link or IDX plugin. The Trestle sync runs from a server cron job and fills its own tables, so listings render in your theme instead of a frame. Disclaimers and listing credit sit in one template part.
Queued jobs on the scheduler pull changes, photos and solds from Trestle. CRMLS gets its own small filter class for local fields and statuses. The token sits in the cache with its expiry, and models read the listing tables.
Any stack that can call HTTPS and run a schedule will do. A market this size suits a search index for map search, so pages never query Trestle on a page view. The sync writes one listing schema your pages read.
Your listings never go blank. The new sync runs beside whatever feeds the site today, and we only switch when the two match.
We check your CRMLS access, your Trestle connection and what the site needs to show.
It fills its own tables while your current listings stay up.
Counts, statuses, photos and rosters checked against the feed.
Pages read from the new sync. The framed search, plugin or old script is removed.
CRMLS lists framed IDX links at no added cost, licensed IDX vendors who charge their own fees, and a raw RESO feed through Trestle. The Trestle feed is the one that puts the raw listings in your own database, under your own design.
Brokers get two Trestle feeds at no charge, per CRMLS. A developer building for you pays the Trestle IDX fee and the per URL fee. The audit sets out which costs apply before anything is built.
Your site's address, what it runs on, and which MLS or feed you have access to.
Access, fields, photos, rosters, and how your platform stores listings.
What syncs, how often, what shows where, and a fixed price for the build.
If you go ahead, the $499 comes off the integration.
We are an independent developer. We are not affiliated with, or certified by, any MLS or data provider named on this page.
Send the site's address and the feed you have access to. The audit gives you a written plan and a fixed quote.