Your MLS sets the display rules. MLSimport is built to follow them. The account, and the obligations that come with it, are yours.
This page explains how the plugin behaves and where the responsibility sits. It is not legal advice, and it does not replace your MLS’s IDX policy. When the two disagree, your MLS wins.
Who is responsible for what
| Party | Responsible for |
|---|---|
| Your MLS | Setting the IDX rules, issuing your credentials, deciding which listings and fields your feed is allowed to carry, and telling you when any of that changes. |
| You | Holding valid MLS membership and an IDX agreement, keeping credentials current, displaying the attribution and disclaimers your board requires, and configuring the plugin to match your board’s rules. |
| MLSimport | Connecting over the RESO Web API with the credentials you supply, importing only what the feed authorises, honouring the internet display flags in that feed, and removing listings when they leave the MLS. |
What the plugin does
- Internet display rules are respected. Every import task honours the internet display flags carried in your feed. Listings the feed marks as not displayable are not imported.
- Only what your feed authorises. MLSimport requests data using your credentials. It cannot show you listings or fields your board has not granted, and it does not aggregate data across customers.
- Stale listings are removed. Daily reconciliation takes down listings that have left the MLS, so sold, withdrawn and expired properties do not linger on your site. You choose which statuses are protected from removal.
- Attribution fields are available. Listing agent, listing office and the other attribution fields your board requires are in the RESO field set and can be mapped, labelled and displayed.
- Per-field visibility. You can import a field and still keep it private, which is how you satisfy boards that permit storage but restrict display.
- Photos stay at source. Images are served from the MLS or its CDN as remote references rather than copied onto your server.
- Everything is logged. The activity log records every add, update and delete with the ListingKey and the task responsible, which is what you will want if your board audits you.
What you should do
- Read your board’s current IDX policy. They differ, and they change.
- Configure your import tasks to match it: statuses, fields, and any market or office restrictions.
- Display the attribution, disclaimer and last-updated text your board requires. Map the fields you need for it.
- Keep your credentials and your IDX agreement current. An expired agreement is your problem, not a plugin bug.
- Re-check after any board policy change, and after you change an import task.
If your MLS asks for a change
Send it to us. If a board requires behaviour the plugin does not currently support, we want to know, and we would rather fix it than have you switched off. Open a ticket from your dashboard or contact us.
Related: what IDX actually is, terms and conditions, and DMCA.