FMLS delivers its data through Bridge Interactive. We sync it into your WordPress, Laravel or custom site and keep it current every 2 to 3 hours.
server token per applicationGET /{dataset}/Property/replication$filter=BridgeModificationTimestamp gt {last}FMLS_{fieldname}Media ordered by OrderFMLS reviews each product before it goes live, so a half working plugin is not enough. Brokers often get quoted a full rebuild at this point. Usually only the sync needs building. We have synced this board's feed before, on a multi MLS platform we built and ran from 2018 to 2025.
FMLS, First Multiple Listing Service, is the Atlanta MLS. It says approved products are shown to approximately 60,000 FMLS members through its Marketplace.
FMLS chose Bridge Interactive for data access in 2019. It offers three ways in through Bridge: the native Bridge API, the RESO Web API and vRETS, a RETS emulator. FMLS describes its system as natively RESO Platinum certified.
In 2025 FMLS, Bright MLS and MIAMI REALTORS announced that their subscribers could search listings across all three. Website feeds are still licensed by FMLS.
The board decides which platform carries its feed. Each route has its own login, paging and limits, and its own page here.
FMLS runs access through its Marketplace and Bridge. Each product is reviewed before it goes live.
Start in the FMLS Marketplace. It holds your products and their review status.
Request FMLS data access on Bridge. Without a Bridge account, FMLS sends an invitation.
Third party vendors pay $250. Member brokerages building for their own brokerage do not.
Once development is done, create a Product in the Marketplace and set Product Incomplete to No.
FMLS reviews the product, typically within 2 business days, then the site goes live.
Through Bridge the feed follows the RESO Data Dictionary, with FMLS fields added under a prefix.
01Property, Member, Office and OpenHouse through the RESO Web API, where your access includes them.
02Fields not yet in the Data Dictionary are named FMLS_{fieldname}.
03Media on the listing record, stored on Bridge's CDN, which Bridge lets you link to.
04Small pages for on demand queries. Full loads go through Bridge's replication endpoint where granted.
05BridgeModificationTimestamp, which also catches changes made on Bridge's side.
06A 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.
FMLS marks fields that are not yet in the RESO Data Dictionary with an FMLS_ prefix. They get their own filter class on top of the shared parser.
Once built, the product is registered in the FMLS Marketplace and submitted for review. FMLS says review typically takes 2 business days.
FMLS charges vendors a monthly data access fee based on how many active FMLS members subscribe. Brokerages building their own product skip the application fee.
FMLS publishes its IDX display rules. The disclaimer is shown with the last updated time, and IDX opt out flags are honoured.
The Bridge server token stays in server config, never in theme JavaScript. Photos can point at Bridge's CDN, so the media library stays clean. A server cron job runs the sync, and the site is ready for FMLS product review before it goes live.
Queued jobs pull changes on BridgeModificationTimestamp and run full re-syncs through replication. FMLS gets a filter class that maps its FMLS_ fields. Rate limit headers are read on every response.
If your site still runs old RETS code, vRETS can keep it alive while the sync moves to the Web API. Either way the sync writes one listing schema, and your pages read that.
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 FMLS access, your Bridge application 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.
All three FMLS routes run on Bridge and carry the same listings. The RESO Web API follows the Data Dictionary, so it reuses the most mapping. The Bridge API is Bridge's own format. vRETS mimics RETS for older code.
For new work we use the RESO Web API. vRETS makes sense only to keep an old site running while the new sync is built. The fees are the same FMLS fees whichever route you pick.
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.