SDMLS moved from RETS to the MLS Router API, a RESO Web API 2.0 feed. We sync it into your WordPress, Laravel or custom site and keep it current every 2 to 3 hours.
POST /token client_credentialsGET /$metadataGET /Property@odata.nextLink$filter=ModificationTimestamp gt {last}SDMLS asked RETS users to move by June 30, 2025. San Diego broker sites built on a RETS download need a new sync, and the quote that comes back is usually a new site. We have synced this board's feed before, on a multi MLS platform we built and ran from 2018 to 2025.
SDMLS, the San Diego MLS, serves brokers and agents in San Diego. It offers IDX, VOW and broker back office feeds.
SDMLS moved its data delivery to the MLS Router API, a RESO Web API 2.0 and Data Dictionary 2.0 feed. It lists certification on Data Dictionary 2.0, Web API Server Core 2.0.0 and Web API Add/Edit 1.0.0.
Pricing is published: monthly feed and access fees, per client fees and per request fees, all billed through MLS Router. SDMLS asked RETS users to move before June 30, 2025.
The board decides which platform carries its feed. Each route has its own login, paging and limits, and its own page here.
Two agreements meet in the middle: the vendor's with SDMLS, and yours.
SDMLS requires brokers and agents to work with an IDX provider it has approved.
The vendor submits the Vendor Data Access Agreement. Once SDMLS approves, it creates an MLS Router account and subscribes to the SDMLS package.
You submit the Participant Data License Agreement. VOW and back office feeds also need a Broker Data Access Agreement.
SDMLS says it processes requests within 2 business days.
The provider connects to the MLS Router API, sets up the display and checks the IDX rules before your pages switch.
SDMLS serves a standard RESO feed. These are the parts that shape the sync.
01IDX for public sites, VOW for registered visitors, and broker back office for internal tools and analytics.
02RESO Web API 2.0 with Data Dictionary 2.0 fields, so a San Diego feed lands in the same schema as other RESO feeds.
03SDMLS says the API does not need to be replicated. We keep a local copy anyway, so per request fees stay low and search stays fast.
04A filter on ModificationTimestamp pulls only what changed, and @odata.nextLink pages through large results.
05A daily purge removes what left the feed, and skips the run with an alert if the feed returns too few listings.
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.
SDMLS charges vendors per request on top of the monthly fees, billed through MLS Router. A sync that pulls only changes keeps that bill down.
SDMLS says brokers and agents must work with an IDX provider it has approved before they apply.
SDMLS has a tiered access programme for vendors serving 1 or 2 clients who do not need the fastest data. It is not open to vendors serving many clients.
SDMLS recommended moving off RETS before June 30, 2025. RETS code on a site is replaced by a Web API sync, not patched.
Calling the API on each page view would add per request fees, so the sync runs from a server cron job and fills local tables. The theme reads those. Credentials stay in server config. A RETS plugin from before 2025 is replaced, not updated.
An SDMLS config entry and filter class sit on a shared parser. Scheduled jobs pull changes, run the weekly re-sync and the daily purge. Request counts are logged per run, so the MLS Router bill can be checked against them.
Any stack that can fetch an OAuth token and run a schedule will do. Since the feed follows Data Dictionary 2.0, adding a second California MLS later reuses most of the mapping.
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 SDMLS agreement, your platform 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 old plugin or RETS script is removed.
SDMLS has one delivery route, the MLS Router API, so there is no Trestle or Bridge to compare. The fees are public, which makes the sums easy.
A broker using a provider that already pays the vendor access fee pays the per client fee. A provider building one site pays the vendor fee too, or applies for the small vendor tier. The audit works out which applies to you.
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.