Data Feeds & MLS Configuration

Active Feeds

ABOR (Austin Board of Realtors)

  • Region: Austin / Central Texas
  • Protocol: RESO Web API via Bridge (Trestle)
  • Status: Primary feed, fully operational
  • Data: 15+ years of historical data synced
  • Key fields: All standard RESO fields including FlexibleListingYN, BuyerAgencyCompensation, BuyerAgencyCompensationType, CumulativeDaysOnMarket

NTREIS (North Texas Real Estate Information Systems)

  • Region: Waco / North Texas
  • Protocol: RESO Web API + RETS (supplemental)
  • Status: Fully operational after migration from legacy RETS
  • Data: 1M+ properties synced (Trestle does not support a Waco-only filter, so all NTREIS properties are synced)
  • RETS usage: ClosePrice is not exposed via the RESO API. Synced separately via RETS. Some historical properties do not exist in RETS and will not have ClosePrice.
  • Default counties: McLennan, Hill, Limestone, Bosque, Falls, Bell

Florida / Sarasota

  • Region: Sarasota, Florida
  • Protocol: RESO Web API
  • Status: Active with ongoing UI configuration refinements
  • Feed-specific UI: Admin-configurable fields and filters for this market

Sync Behavior

Properties are synced continuously from all active feeds. Key details:

  • Statistics are generated on the 6th of each month via cron job.
  • New fields are added via migration scripts to MongoDB.
  • When a feed migration occurs (e.g., NTREIS RETS to RESO), all fields are reviewed and mapped for compatibility.
  • The ListPrice > 25000 condition for property sync has been removed for ABOR and Waco. For Sarasota, the API does not support a ListPrice filter; full resync is required for price-range changes.
  • Subtypes are now deselected by default. All available subtypes for ABOR and Waco are included. Sarasota subtypes were curated to address data quality issues.

Fields Synced

Standard property details, status fields (Active, Pending, Sold, Expired, Withdrawn, Hold, Coming Soon), dates (list, sold, listing contract, price drop), financial (sold price, close price, buyer agency compensation), features (sewer, accessibility, community features), school data, access codes, and lease-specific fields.

Known gap: Elementary school data may not populate for all Waco/NTREIS properties. Residential income properties do not include bed/bath counts in the main data (exists in a separate "Unit Information" section not currently synced).

Feed-Specific UI Configuration

Admins can configure per feed:

  • Which search fields are displayed per property type
  • Property detail display fields
  • Tour view configuration
  • Select options (view type, roof type, etc.)

This configuration is managed via the admin panel. A comprehensive field audit (mapping which fields to show/hide per feed per property type) is a manual process that will be completed over time.

Property Deletion Auditing

A reusable script audits properties that exist in the SP but have been deleted from the MLS. When found, these properties can be removed from the database. This script should be run periodically to maintain data quality.

Reference: Property Data Clean-Up Script for Deleted Properties

Bridge RESO API Changes

The system tracks RESO Web API changes from Bridge/Trestle. When API changes are announced, sync logic is reviewed and updated.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.