Stellar offers two API routes for IDX: MLS Grid and Bridge. We sync either one into your WordPress, Laravel or custom site and keep it current every 2 to 3 hours.
Authorization: Bearer {token}replication full set@odata.nextLink$filter=ModificationTimestamp gt {last}Media ordered by OrderStellar dropped RETS for APIs, and a lot of Florida broker sites were built on RETS era plugins. The fix offered is often a new site. It does not have to be. We have synced this board's feed before, on a multi MLS platform we built and ran from 2018 to 2025.
Stellar MLS is a Florida MLS covering Florida and Puerto Rico. It says it supports more than 80,000 professionals, through 19 local REALTOR organizations.
Stellar chose APIs over RETS. It offers two API routes for IDX, MLS Grid and the Bridge API, both following the RESO Data Dictionary, and runs a Data Services team for feed requests.
Beyond IDX it licenses back office, broker data release, VOW and vendor product feeds, each with its own agreement and fee. Listing distribution to portals runs through Matrix and ListHub, and is up to the broker.
The board decides which platform carries its feed. Each route has its own login, paging and limits, and its own page here.
Stellar's Data Services team handles requests. Vendors and in-house developers each have their own questionnaire.
Vendors complete Stellar's online questionnaire. Brokers building in house use the separate in-house development questionnaire.
Choose MLS Grid or the Bridge API for IDX. Back office, VOW and vendor products are separate licences.
MLS Grid offers a demo feed without approval. The sync is built and tested there.
MLS Grid access needs a three party agreement between broker, vendor and Stellar, and a working product.
Once approved, the token is issued and the sync moves from demo data to the live feed.
Both routes follow the RESO Data Dictionary. What differs is paging, photos and how removals show up.
01Property records shaped by the RESO Data Dictionary, filtered by your licence type.
02Member, Office and OpenHouse resources on both routes, where the licence includes them.
03Media is expanded on the listing. The URLs expire, so every photo is downloaded and stored.
04Media sits on the listing record and can be linked from Bridge's CDN.
05ModificationTimestamp on MLS Grid. BridgeModificationTimestamp on Bridge.
06MLS Grid flips MlgCanView to false. On Bridge, a daily purge compares listing keys with a minimum count check.
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.
For MLS Grid, Stellar asks you to show a fully working application before it approves the feed. A demo feed is open without approval, so the sync is built on it first.
Stellar's MLS Grid route needs an agreement between the broker, the vendor or in-house developer, and Stellar. Back office and VOW feeds need one per broker.
On MLS Grid photos must be downloaded and kept. On Bridge they can be linked from its CDN. The sync handles both, so the route can be picked on cost.
Stellar's back office and VOW data must sit behind a login and be closed to the public. Those fields never reach a public page.
On MLS Grid, Stellar photos go to object storage behind a CDN, not the media library. On Bridge they can be linked. Either way a server cron job runs the sync into its own tables, and the theme reads those.
One sync engine, two drivers. The MLS Grid driver runs on a rate limited queue and downloads photos straight away. The Bridge driver reads its rate limit headers. Both write the same listing schema, so switching route is a config change.
Your pages read your own database, which MLS Grid requires anyway. Map search and filters run on the local copy. Stellar back office or VOW data stays behind a login in its own tables.
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 Stellar access, the route you are on 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 script is removed.
Both routes carry the same Stellar listings on the same RESO standard. MLS Grid uses one standard licence and wants every photo stored. Bridge lets you link photos and has smaller pages.
If you are covering several MLS Grid boards, MLS Grid keeps it to one licence. For Stellar alone, Bridge can cost less in storage. The audit compares the two 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.