Query MLS listing data through a RESO certified Web API: properties with price, status, beds, baths, area and days on market, agents and brokerages, open houses and rooms, plus the lookup vocabulary, the MLS attribution text you must display, location autocomplete and boundaries.
This Actor's pricing details are outlined in the table below. Visit our pricing page to compare plans and see how much you can save.
Pricing
Listing returned
Charged once for each MLS listing returned, in the RESO standard field vocabulary: listing key and MLS listing ID, the status in both the normalised RESO spelling and the originating MLS's own, property type and sub type, list price, original list price and close price, the full unparsed address broken into street, city, state, ZIP, county and subdivision, bedrooms and bathrooms, living area, building area and lot size, year built, days on market, listing and close dates, coordinates, the listing agent and office with their MLS identifiers, public remarks, and every other field the feed publishes. Both the MLS modification timestamp and the distributor's own travel on the row. Filters that match nothing are not charged.
$8.00
/ 1,000
Agent or office returned
Charged once for each agent or brokerage returned: the member or office key and MLS identifier, full name, status, email and preferred phone for an agent, office name, status and phone for a brokerage, the originating MLS, and every other roster field the feed publishes, along with both modification timestamps. Note that contact fields are published only where the originating MLS permits it. Searches that match nothing are not charged.
$8.00
/ 1,000
Open house returned
Charged once for each scheduled open house: its key, the listing it belongs to, the date, the start and end times, and whatever else the originating MLS publishes about it. Listings with no scheduled open house are not charged.
$5.00
/ 1,000
Room returned
Charged once for each room level record: the room key, the room type and its dimensions alongside the listing it belongs to. Room detail depends on MLS policy and is not published by every feed, and listings without it are not charged.
$4.00
/ 1,000
Field or lookup value returned
Charged once for each field definition or lookup value returned by the metadata resources: the field key and name for a field, and the lookup key, lookup name, lookup value and its standard RESO equivalent for a lookup. This is how you find out which fields your particular feed publishes and which values each one accepts before writing a filter against them. Queries that match nothing are not charged.
$4.00
/ 1,000
MLS disclaimer returned
Charged once for each MLS attribution record: the originating system name, the disclaimer text and the attribution logo that most MLS agreements require to be displayed alongside any listing shown to the public. Feeds that publish no attribution metadata are not charged.
$5.00
/ 1,000
Location suggestion returned
Charged once for each autocomplete suggestion: the value and the field it matched on, from among state, county, city, subdivision, MLS area, postal code, street name and unparsed address, plus how many suggestions that field held. Prefixes that match nothing in your permitted feeds are not charged.
$3.00
/ 1,000
Agent statistics returned
Charged once for each closed listing summary: the average closed price and the closed listing count for one agent or office over the requested window, defaulting to the last twelve months. Filters the provider cannot compute are not charged.
$12.00
/ 1,000
Boundary returned
Charged once for each neighbourhood, ZIP code or school district boundary: its name and geographic identifier, the state FIPS code, the land and water area, the interior point coordinates, the lowest and highest grade and school year for a district, the boundary vintage, and the polygon itself when geometry was requested. Names, ZIP codes and points the provider holds no boundary for are not charged.
$6.00
/ 1,000
Additional costs
Platform usageIncluded
Platform usage costs are tied to the Actor's performance in terms of the underlying platform resources it consumes. Learn more