Odyssey Apps

FetchMLS

The MLS data your work runs on, delivered before you have to go looking for it.

FetchMLS is designed to bring you your own MLS listings and their changes daily, through the Spark API under your own data plan. Buyer matching across the wider market is next, pending a separate MLS approval. Never through your Flexmls login. It's not live yet.

FetchMLS: your listingsTue 7:04 AM
Buyer matching · pending MLS approvalK. Whitmore · 3bd · to $500k · TillamookR. & T. Deleon · to $540k · BayoceanM. Aldous · acreage · Trask River
Your listingList priceStatus
812 Alder Ct, Tillamook$486,000Active
1240 Bayocean Rd$529,900Under contract CHANGED
47 Netarts Hwy$415,000 ▾ 12kPrice reduced CHANGED
88 Trask River Rd$597,500Listed today CHANGED
615 Stillwell Ave$449,000Closed
Licensed through your MLS ·  Spark API  ·  no scraping, no mirror
Concept panel: the interface is in development.

The same morning search, every morning

I log into my MLS and see if there's any new properties on the market
A working agent, from the interview record this module is built on.

That daily check is necessary work, but it's also repetitive work that a machine can do faster and more consistently than a person toggling between browser tabs at 7 a.m. Once you connect your own data plan, FetchMLS tracks your listings and their changes daily. Matching against the criteria you've set for each buyer is the next step, pending a separate MLS approval. You still decide what to send and who to call.

Built on the Spark API, licensed by your MLS

FetchMLS is designed to connect through the published Spark API from FBS (the company behind Flexmls), the same platform your MLS already uses. No scraping. No screen recording. No borrowed logins.

Your data stays yours

Licensed by the MLS, never your login

Each agent connects FetchMLS to their own MLS data by entering a Spark access token from their own data plan, approved by their MLS. Agents never give FetchMLS their Flexmls username or password.

What each agent sees is set by what their MLS approved for that token, and nothing beyond it. Today, each token covers the agent's own listings. Matching across the wider market needs a separate MLS approval not yet granted.

Where the data goes

Listing data travels from Spark to the FetchMLS application, server-side, for the MLS member's own work. Each agent's access token is sealed on the server after entry. Only the last four characters are ever shown back; the full token is never sent back to your browser.

Stored data is held for no longer than 24 hours unless the MLS permits longer retention. It is not sold, redistributed, or shared outside the application that requested it.

Who it's for

FetchMLS is designed for MLS members who hold an approved data plan, for as long as they stay members. An Odyssey Apps account doesn't open MLS data on its own.

What gets displayed, and why

FetchMLS selects and displays listings on objective criteria only: location, price, property type. Any listing the tool displays honors the source MLS's own compliance rules delivered through the API, including required fields, disclaimer text, and source-MLS logo and tracking.

Before FetchMLS asks anyone to use it, our Privacy Policy will say exactly what it reads, what it keeps, and for how long.

Built for agents who work alone

FetchMLS is being built by Odyssey Apps. It's not live yet, and it doesn't connect to any MLS yet. What you've read on this page is a description of what the tool is designed to do, built against the Spark API's published documentation and a working agent's actual daily routine.

Join the FetchMLS Beta