MLS access (overview)

This page explains how MLS data usually works so you know what to ask your board or broker — RealtyPad does not connect MLS feeds in v1.

How agents typically get MLS data

1. Membership — You join a local REALTOR® association / MLS.
2. Data license — The MLS or a vendor (Bridge Interactive, MLS Grid, Spark, Trestle, etc.) grants API or IDX access under strict rules.
3. Credentials — You receive client IDs, secrets, or OAuth flows — not your login password for the MLS website.
4. RESO Web API — Many vendors expose a RESO-standard OData API for listings, photos, and metadata.

IDX vs API

Approach	Typical use	Notes
IDX website	Public search on your site	Display rules; not a full agent back-office feed
RETS / RESO Web API	Apps, CRMs, custom tools	Requires approval; rate limits; audit

RealtyPad’s future MLS integration will likely store vendor credentials per tenant and sync into deals — not scrape the MLS login UI.

Compliance

• Follow your MLS rules of use (display, retention, sharing with AI tools).
• Do not paste MLS exports into public chats or unapproved third parties without checking policy.
• Your operator should document which fields are stored and retention.

What to ask your MLS or broker today

1. “Do we have RESO Web API or MLS Grid access for third-party tools?”
2. “What is the process to approve a private application for deal analysis?”
3. “Are AI / automation uses allowed with API data under our agreement?”

Roadmap (not shipped yet)

• Secure credential storage per workspace
• Scheduled sync from RESO-style APIs into deals
• Clear field mapping (list price, status, photos, remarks)

Until then, use listing data today paths and manual/API leads.